Super Optimised Static Sites
Super Optimised Static Sites
Super Optimised Static Sites
If you use GitHub pages, there’s a high chance you’re also using Jekyll. The biggest thing Jekyll brings is templating - which is great both for developer speed and for getting consistency in your site.
Today, Jekyll is over 12 years old, and it does show its age in places. I wanted to see what was possible with today’s more modern tooling.
The toolchain makes heavy use react-dom/server and leverages a powerful custom component system that handles the site’s assets. While I’m not the first to do a static site system based on React, the custom component system is what sets it apart, and gives way to,
React-based templating Does not include React on the client (or any JS unless you want it) Effortless compression/minification of images, CSS, and JS Simple long term caching of assets Granular control of how assets are used - including inlining critical CSS and JS The best CSS optimisation available - I’ve not seen anything that comes close here
Putting this all together makes the total page weight for the page you’re currently on less than 100kb - and that’s including a 50kb font.
Firstly, React-based templating. This is basically the same as MDX. You can include HTML and JSX inside your markdown,
Docusaurus
Static Site Generators List
