Your static site gen is slow. Well, it does a lot of stuff you don‘t need, so you switch to a lighter one. You choose eleventy. You build assets yourself. This is tedious and boring. You include asset building into eleventy. You then (after some time) decouple asset building from your SSG entirely, because it‘s a bit complicated. To do this, you install node packages which do these jobs outside of your SSG to replace bash scripts.
Now you need a live server to work with your output in production. No problem, you can do this via node. 11ty includes a dev server.
You want hot reloading, because manually restarting the server sucks. You also need cash busting because your stupid browser gets in the way with its nice ideas about caching.
Man your output is large. You want to minify it. No problem, there‘s a node package for this after all!
You begin to work with images and svgs a lot. Damn, importing via strings sucks. Isn‘t there a better solution for this? Sure enough, get another package or switch templating systems.
You need JavaScript for interactivity. No problem, you can just write vanilla JS. Damn, this only works in Chrome? Better get Babel or something. Uh oh, my JS is getting large and unwieldy. TypeScript it is!
Now embedding your JS file for file kind of sucks... Can‘t we just combine these into one?
Man, all these steps to take for your application to build. Configuration files are everywhere. Assets are large and begin to be unmanageable. You begin to pull your system together. It can do all these things at once.
This feels nice! Maybe you should open source it!
Need a name... Let‘s see... Your application-slash-buildsystem prepares assets, scripts and bundles them and packs them for the web.
„Packweb“ it is.
—-
Remember, new and shiny buildsystems/SSG‘s/software in general can be fast because they can afford to be. They do one thing, or a very limited range of things. Then users come along, and with them feature requests and the like. Suddenly, <new thing> can do a whole lot, but it‘s not fast anymore! Well gee, of course not, blog posts and influencers say alike. Have you heard about <newest thing> however? It may only have a small numbers of features, but it‘s fast.
I like Hugo right now as it's super fast + has just enough built-in (Sass, image resizing) that you don't need anything else for simple sites. I'm actively avoiding static site generators that turn your website into a SPA because it just feels like adding a heap of complexity for little gain.
I am able to build out my site either by leveraging a number of 'smart ways' to do it that all static site generators do ... templates, markdown to html... but I can also be lazy and custom write html/style per page, per directory, to get some art-directed type page out fast.
I feel like there was a tiny learning curve with the docs to get from 0 to 10 ... but from 10 to whatever is really great fun.
I am in the process of building multiple sites with 11ty, one new, and a few are redesigns of older sites. I am in love with every part of 11ty except the documentation. I've learned most of what I needed to know from GitHub starter projects, GitHub issue responses and some YouTube videos.
I am using Gatsby for my site https://bobbydreamer.com . Sites fast but build times are slowly increasing on the local machine. I wonder how much time does it take Blog with 500 articles with 5 images per page take.
7 comments
[ 0.23 ms ] story [ 34.5 ms ] threadYour static site gen is slow. Well, it does a lot of stuff you don‘t need, so you switch to a lighter one. You choose eleventy. You build assets yourself. This is tedious and boring. You include asset building into eleventy. You then (after some time) decouple asset building from your SSG entirely, because it‘s a bit complicated. To do this, you install node packages which do these jobs outside of your SSG to replace bash scripts. Now you need a live server to work with your output in production. No problem, you can do this via node. 11ty includes a dev server. You want hot reloading, because manually restarting the server sucks. You also need cash busting because your stupid browser gets in the way with its nice ideas about caching. Man your output is large. You want to minify it. No problem, there‘s a node package for this after all! You begin to work with images and svgs a lot. Damn, importing via strings sucks. Isn‘t there a better solution for this? Sure enough, get another package or switch templating systems. You need JavaScript for interactivity. No problem, you can just write vanilla JS. Damn, this only works in Chrome? Better get Babel or something. Uh oh, my JS is getting large and unwieldy. TypeScript it is! Now embedding your JS file for file kind of sucks... Can‘t we just combine these into one?
Man, all these steps to take for your application to build. Configuration files are everywhere. Assets are large and begin to be unmanageable. You begin to pull your system together. It can do all these things at once.
This feels nice! Maybe you should open source it!
Need a name... Let‘s see... Your application-slash-buildsystem prepares assets, scripts and bundles them and packs them for the web.
„Packweb“ it is.
—-
Remember, new and shiny buildsystems/SSG‘s/software in general can be fast because they can afford to be. They do one thing, or a very limited range of things. Then users come along, and with them feature requests and the like. Suddenly, <new thing> can do a whole lot, but it‘s not fast anymore! Well gee, of course not, blog posts and influencers say alike. Have you heard about <newest thing> however? It may only have a small numbers of features, but it‘s fast.
I like Hugo right now as it's super fast + has just enough built-in (Sass, image resizing) that you don't need anything else for simple sites. I'm actively avoiding static site generators that turn your website into a SPA because it just feels like adding a heap of complexity for little gain.
I am able to build out my site either by leveraging a number of 'smart ways' to do it that all static site generators do ... templates, markdown to html... but I can also be lazy and custom write html/style per page, per directory, to get some art-directed type page out fast.
I feel like there was a tiny learning curve with the docs to get from 0 to 10 ... but from 10 to whatever is really great fun.
Interesting. One of the reasons I chose Eleventy over Hugo was because I felt its documentation was much better.