espy commented on issue #9135: URL: https://github.com/apache/pouchdb/issues/9135#issuecomment-3870342588
11ty looks like a pragmatic choice, it’s been around for ages and doesn’t change much, they prioritise making updates easy, it does what we need and doesn’t require a lot of modifications to the site sources. Also, Markdown files plus HTML templates are a fairly portable format, and if we realise we need something more capable further down the road, we can still switch without too much hassle. Currently, the primary goal is to make the site easier to work on. Ruby/Gems/Jekyll have proven to be a constant source of frustration for a number of people trying to work on the site, and since PouchDB is a JS project, having the website be in that same ecosystem just reduces friction and lowers the barrier to entry. It shouldn’t be necessary to wrangle a separate version manager, package manager, language or containerisation system just to write a blog post or fix a typo. So given all this, and that @alxndrsn has already [forged ahead](https://github.com/apache/pouchdb/pull/9146) with this and made good progress, I’d say let’s just roll with it. I’ve looked at the PR last week and continued a bit to see where we stand, and we could basically switch… this week? I have the time and motivation to finish the migration right now, and then we can tackle the more interesting issues more easily. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
