I love nextjs for static websites (yes, it sounds crazy). But nextjs offers some really cool features. Like OG image generation. Also react is the most used front-end library (not necessarily the best) so as many people as possible can contribute because they are familiar with JSX. Also nextjs is really friendly for SEO.

Also note that the design I did is based on tailwindcss which works very well in the nextjs ecosystem.

PS: I'm open to set up the infrastructure. Make the components ...

@AugustinMauroy I'm only vaguely familiar with nextjs. Is the nextjs getting started page a reflection of what's required to start developing with it?

Some feedback that prompted this move is that installing an entire language, package manager, and dependency tree (Ruby/Gem in the case for Jekyll) was too cumbersome for someone who wanted to write a blog post or make some docs updates. Judging by the getting started page, it doesn't look like that nextjs moves us in the direction needed to make the website easy to contribute to. But I'm opening to hearing more if that's a misjudgement.

(FWIW, I'm a Javascript guy from a long way back - since 1998! - but I think that's not typical amongst folks who use or would contribute to Valkey)

Is the nextjs getting started page a reflection of what's required to start developing with it?

You only need node. after you can extend with package with npm but npm is install whit node.

it doesn't look like that nextjs moves us in the direction needed to make the website easy to contribute to. But I'm opening to hearing more if that's a misjudgement.

in all cases you need something to process the markdown files. with next you just need to do npm run dev.
But we could also provide a devcontainer ???

If you want good example of how nextjs can be used for static website nodejs.org

While I'm a fan of Next.js personally, it does not create the simplest contribution roadmap (imo, and specifically for non-infrastructure commits, which should be more common eventually).

I'm also of the opinion that even though React is all the rage in frontend world, it is likely overkill for a website with almost no "interactivity". We'd essentially just be using the JSX component of it as a templating language, which really is a job for a static site generator.

I do think that using TailwindCSS is almost always a good idea though, and I'd love to use it again. Note that this would almost certainly require an additional build step involving some JS bundling business provided that Zola turns out to be the solution.

After spending this afternoon playing with Zola, I am a fan. It seems to work pretty well.

perfect !