Ergberg's  Jotter
🔍
×

Drop me a note



If you wish, you may send your message anonymously.
However, if you would like me to be able to reach you, please include your e-mail address.
(I do not use social networks.)



    



⟳
As of
Est. 

SSR ​

Server Side Rendering does not stand for server-side web frameworks but specifically refers to pre-rendering JavaScript web applications to static HTML, and finally hydrating it on the client.

Advantages are:

  • Page content is more rapidly visible because it doesn't have to be computed by the JavaScript code first.
  • Content is static and hence easier digestible for search engines which might result in better SEO.

That is, you have a server running that handles all requests from the clients and delivers pre-rendered HTML that looks like a snapshot of what would otherwise displayed if all JavaScript was rendered at the client, only. That server is no static web server serving static files but includes node.js as an environment to execute the JavaScript part at the server. In the end, the JavaScript Code is executed twice, one at the server to timely deliver HTML the browser can directly show to the user, and once at the client in the hydration process that adds the dynamic behavior to the static pages.

Pre-render only once in build step on server side and you've got SSG.

See also: CDN, SSG

You also might want to read about the following topics:

  • Reactive Components with Vue
    What I like about Vue and a quick glance under the hood.
  • Scott me up, Beamy!
    🖖 How to avoid common pitfalls when using Vue's teleport component with VitePress layout.
  • Stray Parts
    Some parts have piled up 🧩 that do not represent a coherent description of the basics, nor of a general functionality that fits under site functions.