Mar 20, 2020 • ☕️ 1 min read
Static rendering is a strategy that eagerly generates a separate HTML file for each URL ahead of time at build time, needs to be rebuilt and published each time the content changes, promises to be blazing fast with great SEO, and ultimate outputs static websites with no application code.
Generates no application code makes it best for sites with few authors and relatively infrequent content changes, typically personal and simple marketing websites.
Can help your site rank and perform better in search engines. Using this strategy makes your site fast and efficient for search engine crawlers, like Googlebot, to crawl your site and index your pages, blazing fast is a positive ranking factor for Google.
Has very fast response time because nothing needs to be generated on the fly, you can deploy to multiple CDNs to take advantage of edge-caching.
Exchange flexibility for speed makes it good for websites focused on static quality content, often publicly available and doesn’t need to be published frequently.
Has very low maintaining cost, provide high-levels of reliability, require almost no IT administration, and scale to handle enterprise-level traffic with no additional work.
Static rendering is a no no if your site has one of following features:
Ultimately static rendering is best suited for sites containing no more than a few hundred pages with a couple of new posts every week published by several technical authors.
Some noted problems that might hold CSS back and open up new development of preprocessors or CSS-in-JS
At any given time, I have a side project running. It help me to learn new skills, meet new people and provide a different context in which to showcase my strengths
I discuss some HTML topics like living standard, semantic markup, accessibility, and more
Bull is the fastest, most reliable, Redis-based queue for Node. I have been using it for years to handle async jobs and schedule messages