icaraps
commented
6 months ago @benjamind If another technology stack is envisioned to get rid of Gatsby, I'd rather recommend moving to https://aem.live especially since some pages are already built with it.
Here's an example of a tech doc site built with it https://docs.prismacloud.io/en where the content is Asciidoc-based.
❔ Question
Gatsby was recently put into 'maintenance mode' by the new owners at Netlify, with all the features of Gatsby being rolled up into the Netlify stack. The team has all been fired back in August 2023, and there is nobody maintaining it, see links in this thread: https://fediverse.zachleat.com/@zachleat/110927844356705881
Gatsby is also pretty heavy when it comes to static site generation, unnecessarily complex, and slow to generate pages. Would the team consider a move to eleventy instead?
🔦 Context
Site generation is slow, and the produced output of Gatsby generated sites is also slow (being very JS heavy and 'React-first'). This impacts user experience for any sites we create for external customers, as well as impacts developer velocity when generation times are increasingly a bottleneck.
Additionally with Gatsby no longer having support, this will quickly become a security vulnerability for us as the packages it depends on will not be updated.
🧢 Your Company/Team
Photoshop