Open DEGoodmanWilson opened 4 years ago
Numbered the list, to make it easier to branch out into multiple discussion.
1. First off, I vote to roll our own theme. It will likely take less time then understanding someone elses css. 😅
2 & 3. This is likely pretty much the same for all static site generators.
4. Agreed. We must make sure that the hassle of publishing isn't the reason why content isn't created.
https://stackshare.io/stackups/11ty-vs-gatsbyjs https://twitter.com/jensimmons/status/1107377359546736641?lang=en 11ty/eleventy#745 https://brycewray.com/posts/2019/09/why-left-hugo-eleventy/
For what it's worth re the last one, I actually returned to Hugo (not just the brief time in 2019) — not because there was anything wrong with Eleventy, for which I remain a huge fanboy, but because I wanted a simpler dev experience not tied to npm dependencies and all that. I explain that a little bit in the “epilogue” part of https://brycewray.com/posts/2020/09/ignition-sequence-start.
It turns out I unfortunately lack time to contribute. Sorry for being a blocker.
Hugo is a little bit of a pain for me and the other board members; it's hard for us to find templates we need to modify sometimes (and template organization has gone to shit as a result), and cumbersome to add new content (you have to remember not only the magic Hugo command, but run it from the right path). Maybe we're asking too much from a static site generator, I don't know.
Anyway, I've heard interesting things about 11ty, and I am curious to understand if it is going to help make site maintenance easier. The scope of this issue is to understand whether 11ty can help us with these problems: