[mojombo]

> As far as I know Redwood has no server-side rendering solution.

SSR is priority number one for v2. In the meantime, a number of users use Next.js as a client that talks GraphQL to the Redwood backend. It works very well!

> there is actual financial backing for Next.js

Today I announced I will be providing $1M of funding for future RedwoodJS framework development this year, so now we have funding too. =)

https://tom.preston-werner.com/2022/04/04/redwood-v1-and-fun...

The truth is, we can both succeed at the same time, there are so many great app ideas waiting to be explored, and different tools will work better for different situations!

[xrd]

I'm the author of Svekyll (https://svekyll.com) a static blog tool which models the simplicity of Jekyll. Svekyll uses SvelteKit under the hood, but rendering to a static site feels like it is a second class experience in SvelteKit (they are more focused on rendering to cloudflare or netlify or vercel serverless platforms). I would love to experiment with using RedwoodJS as the backend if SSR is a priority; how do I get more information on that work?

[dac09]

Hi! Core team member here, right now we have our hands a little full with the launch week, but will be moving onto v2 very soon!

Best way to get more info is to create a post on the forums, or an issue! The discord contributing channel is a great place too. All the links on the main website https://redwoodjs.com

Speak to you over there!

[replygirl]

what happens when you get bored of it?