[rpastuszak]

This looks lovely! I've been recently working on sth similar: building a custom pipeline from my Obsidian notes into a website (untested.sonnet.io).

I ended up using 11ty because I wanted to stick as close to the web platform as possible, but a part of me wishes I had tried Astro as well. Mainly because I feel that it strikes the right balance when it comes to flexibility and boilerplate. 11ty is lovely, but there was soooo much stuff I had to write from scratch. I feel like it paid off, but it took me much longer than I had hoped.

One surprising side effect: I noticed that the site worked faster online than served from localhost. 5 minutes of digging after I remembered that it's served via HTTP2 w. multiplexing. I'm not even interested in adding a bundler/minify step, just plain CSS/HTML and asset optimisation w. 11ty-image is enough.

[azangru]

Plus one for eleventy. Love its minimalism and flexibility, although it means that there isn't a clear guidance on assets management. It's a shame that the web still doesn't have a standard way of authoring components, and different frameworks and static-site generators, including eleventy, have to invent their own.

[rpastuszak]

OK, so 11ty webc is pretty good and feels relatively low on abstraction. The only issue I've had with it was the developer UX (e.g. some components getting "stuck" during livereload, so I needed to manually restart 11ty to see the changes). Webc also supports bundles.

What 11ty lacks (assuming I don't add vite, keep things minimal), are components/composition, i.e. actually being able to compose templates without seeing them as templates but as DOM.

I recommend checking out some videos about .webc and progressive enhancement, there's a small paradigm shift from both React-like components map to a tree that maps to pixels and a more traditional old timey PHP-like string interpolation in templates. (I'm expressing this poorly as I'm in a rush, sorry!)