[Website]: Headless CMS for blog

[ssandino]

Is there an existing request for this feature?

• I have searched the existing issues

Is your feature request related to a problem? Please describe.

We are planning to introduce a blog feature on our website that enables non-dev volunteers to publish articles using a headless CMS. Currently, each new page (even text only pages) requires manual coding, which is inefficient and time-consuming.

Describe the solution/feature

Our goal is to use a easy-to-use visual interface that streamlines the workflow, supports automatic deployment, and facilitates the publishing of multilingual articles.

The proposed blog articles should be published under the subdirectory: socialincome.org/journal/TITLE

Important: The headless CMS should be implemented exclusively for the blog section, and not for any other pages on the website.

Describe alternatives you've considered

No response

Criteria for Completion

No response

Anything else?

Additional considerations and information:

• Our decision to implement a blog was further validated through preliminary testing. We created basic content pages (example) and linked them to Google Search Ads via the Google Nonprofit Program, which resulted in a noticeable increase in traffic.
• We have a free NGO account for storyblok.
• We use Vercel which seems to be working with Storyblok (Demo, Code). The boilerplate design with text and image would be a solution that works for a start.

Code of Conduct

• I've read the Code of Conduct and understand my responsibilities as a member of the Social Income community

[renestalder]

@ssandino Is there any need for «region» translated journal entries? Or are languages sufficient enough?

[ssandino]

Languages are sufficient – don't see a need to show journal entries based on region of a user.

[renestalder]

I have now Storyblok connected on the branch im working on, including the setup for using the visual editor.

I'm now about to integrate the journal story type I've setup in Storyblok.

[renestalder]

Another status update and why the ETA is difficult:

• While the connection to Storyblok works, to make the CMS useful, a simple content preview is necessary, to be able to check on whether content is rendererd correctly.
• As Next.js 14 uses the relatively new and experimental Server Side Components part of React, it assumes to render all content server-side per default.
• It's possible to define client-side only rendered components. For a preview, we need some kind of client-side rendering, so the unpublished content can be retrieved on demand.
• Traditionally, and also previously with Next.js 14, frameworks allow to use the same components for server-side rendering and client-side rendering, allowing to retrieve data on the client too and render it in the same components that previously were rendered on the server.
• As Next.js 14 isn't doing this the way it used to be (for the good and the worse), I'm currently trying to figure out how I can achieve this with dynamic routes/split routes.
• The alternative is to do everything twice; having every component as a server-side one and a client-side one.

It's quite a hazzle, as Next.js 14 is new enough for official documentations not covering it especially. All documentations cover Next.js 13, where this is somewhat «easy» to do as it follows well common known paradigms.

I keep you posted.