Volodymyr is an experienced front-end developer who can handle projects of various complexity. He is great at implementing colorful and engaging visual elements for custom web applications. He strives to bring positive user-experience, efficiency, speed, and easy to use functionality into every project he's working on. Volodymyr aims to write the kind of the code that can be easily modified and upgraded in the future. His framework of choice is Vue.js. Volodymyr specializes in building SPA websites that load fast and run smoothly.
Vue
Vuejs 2
SPA
Let say we have pages, which are not in the prerender routes list for some reason. For example, pages which are visible only for logged in users or ones that are not needed for crawlers, etc. For those pages, the server will return the prerender file for the home page, which is not good. We need to return the initial HTML file which is generated during the webpack build for such pages.
During developing SPA (Single Page Application) we met with a common SPA problem: although google crawler uses the last Chromium version to run JS and indexing results as HTML pages (it’s not so easy to make it work and there is still the Fix Search-related JavaScript problems list), but for other search systems and sharing in social networks SPA doesn’t work. They will get the default index.html with the default title, description, etc for all pages.
Usually links inside Vue.js app handle by vue-router and router-link component. It makes a transition between routes without reloading page. The smooth and slick user interface is one of the advantages of Single Page Applications. In the case with CMS content, links are inside content and can’t be processing separately but inserting as one HTML part with `v-html` directive. Such links on click will reload page even if they follow the same app page.