God I love seeing a codeberg link. I swear their no AI policy is going to do dividends in the future.
post
Nice idea.
If you're taking constructive suggestions; I'm heavily into Hugo, which is excellent for all the usual reasons. But one thing that really irritates is breaking features. Keywords being deprecated from hugo.yaml in particular. I don't constantly update my sites, so remembering where everything is can take some time.
If you were to actively resist feature bloat (as suggested by your premis) then that also lends itself to not having breaking changes. If scaff were to feature "always backwards compatible" - handling any later changes silently internally - it might wins some friends? Low maintenance, easy to learn, low effort SSG. Leave the singing and dancing to the mature frameworks.
Anyway - good luck, whether you take my thoughts on board or not!
I've used Hugo before, but I've always got too full whenever I used it, and I felt like it was just big and slow. Other SSGs exist and are faster but I found that the process for making an SSG that meets my demands sounded like an extremely simple, quick and efficient concept to implement. The breaking features issue sounds plenty annoying, and rest assured, I will make sure that things are backwards compatible and will completely reconsider features to maintain it.
Thank you!
all 5 comments