Perhaps these frameworks are better employed for designing Single Page Applications (SPA) with reactivity.
So I looked it up and found their themes pages. I took a look at one that closely resembled typical product or service landing pages call Juice.
Pagespeed Score: 99 on the desktop. 99 on mobile. Total requests 14. 178 KB. Wow!
I immediately installed the Zola binary.
These are the things I noticed: No package.json One scss file contained most of the styling normalize.css utility.css just three classes live reload still there A few SVGs HTML templating similar to what I find when using PHP (i.e. similar to Twig)
I mean, talk about a simple framework (If you can call it that). I absorbed the Life-Cycle very intuitively mostly by looking at the code. Their documentation is succinct.
There was just one thing to do for me. Try to recreate the Gatsby Startup Landing Page starter using Zola and test it.
I recreated most of the style of the Gatsby Startup Landing Page and included the Banner and Features sections. I wrote some simple CSS and JS without worrying about IE or much cross-browser support. I donâ€™t think this matters since most landing pages would be targeting mobile devices anyway.
Since I was losing the SPA feature of Client-Side rendering, I made sure I prerendered my main menu pages.
The results. Drumrollâ€¦ 99 on the desktop, 98 on mobile. 1. 0KB Js files. 10KB CSS. Check out the Pagespeed report.
Did I find the perfect landing page? No. Iâ€™ll explain.
What I managed to find is a way to generate landing pages that get very near to a perfect score on Pagespeed Insights.
That may not be enough for everyone. I deal mostly with small businesses, and for my clientele, getting a perfect score on Pagespeed Insights may be more than enough.
Here are three imperfections I thought about:
- Developer Focused CMS: May not scale well with marketing teams
- Messy Code: A Templating engine is good, but Styled Components is way better at keeping code organized.