ok so I've had it in my mind that I want to make something with eleventy.
I really like the vibes of the project. Extremely competent from a technical standpoint a little bit madcap humor - which is rare - but when you see it, when I see it, it feels inspiring.
Keep it small, keep it fast
I've also had this project in mind for a while: a site to show new browser features that almost, but not quite ready to use. I've written a package that collects the data from the caniuse repo going back to 2016.
Now I'm ready to start the site, and it feels like it wants to be a static site. There's only ~500 distinct features in the caniuse dataset and while there'll surely be more in the future ... it's not that big.
I want it to have:
I want it to look pretty good.
And so I'm going to be working on that.
So right off the bat I'm a litle lost:
things I don't get yet:
how to pick your preferred templating language
how do you get some styles in place?
So much of the docs reads (to me) to presuppose that you have an existing site, with some decisions made already, and 11ty is trying to be flexible enough to just adapt seamlessly.
But if you don't
So I'm probably going to go with:
nunjucks (because handlebars and mustache have some trouble with referring to partials from other files)
I use tailwind a lot, so much so that I'm trying to find another project to try something different. But even thought I want to try something like styled-components, this might not be the one. (Though it looks like it's possible to use styled-components with preact and to use preact with 11ty, so ... maybe another time.
Given that I want to use tailwind, I'll probably follow the first chunks from this CSS tricks post.
.eleventy.js file is really importanthttps://sia.codes/posts/itsiest-bitsiest-eleventy-tutorial/
https://www.tatianamac.com/posts/beginner-eleventy-tutorial-parti/
https://www.zachleat.com/web/eleventy-tutorial-level-1/ https://www.zachleat.com/web/eleventy-tutorial-level-2/