I've been exploring modern publishing workflows for React applications.
Curious how others solve:
- content management - editors - frontend separation - deployment
What is your current stack?
Ask HN: How do you manage content for React-based websites?
1–6 of 6 posts
Re: Ask HN: How do you manage content for React-based websites?
#2A headless CMS usually but with a strong preference for just hardcoding anything that won't change very often. I'd rather have to deploy the app again than have a dependency on a network service. CMS content is strictly limited to things that need to be updated more quickly than the release pipeline can handle (e.g. marketing content that needs to be updated to react to the response, legal things like T&Cs that need to be live ASAP when there's a change, etc.)
The actual content for the site (descriptions, help content, etc) all comes from a locale-specific JSON file that's exported from a translation app.
Re: Ask HN: How do you manage content for React-based websites?
#3[flagged]
Re: Ask HN: How do you manage content for React-based websites?
#4First, I remove React.
Re: Ask HN: How do you manage content for React-based websites?
#5A headless CMS usually but with a strong preference for just hardcoding anything that won't change very often. I'd rather have to deploy the app again than have a dependency on a network service. CMS content is strictly limited to things that need to be updated more quickly than the release pipeline can handle (e.g. marketing content that needs to be updated to react to the response, legal things like T&Cs that need…
[flagged]
Re: Ask HN: How do you manage content for React-based websites?
#6First, I remove React.
[dead]