Headless CMS blog platform for RUMAG
For RUMAG, we built a blog platform on a Strapi headless CMS, where the editorial team publishes daily on their own, without needing a developer.
Deliverables
- UI/UX design
- Web development
- Hosting
Tech stack
- Strapi (headless CMS)
- Figma
RUMAG publishes every day. The editorial team had to ask a developer for too many changes, and the existing setup stalled when lots of visitors arrived at once. Your Tech Club rebuilt the blog platform.
What needed to improve?
Two things at once. The site stalled under high traffic, and the content team depended on a developer for changes. For a newsroom that publishes daily, that slows down the whole operation.
One cause, two problems
The site stalling under load and the editors waiting on a developer had the same cause: content and presentation were tied together. Separating them lets the editors publish in the CMS without a technical step, and lets the front end be set up separately for busy moments.
What did we build?
A blog platform on a headless CMS, where content is separate from presentation. The editors publish themselves, without a technical step, and the surrounding setup uses caching and hosting optimisation to handle busy moments.
Which integrations are included?
Advertising tools that tie in with the content, plus analytics that measure clicks and interactions. That data feeds the content strategy.
What can the editors do now?
Articles, sections and pages go live when the editors have them ready. Because the content structure is separate from presentation, the same articles can later be used on another channel too.
Get in touch with us directly. We'll get back to you as soon as we can
Your message goes straight to our team in Amsterdam.Who built the RUMAG blog platform?
Your Tech Club. We did the UI/UX design, built the blog platform on a headless CMS and provided the hosting that handles busy publishing days.
What did Your Tech Club build for RUMAG?
A blog platform where the editors publish independently, with advertising tools and analytics built in, and a hosting setup that absorbs traffic peaks.
What technology does the RUMAG blog run on?
Strapi as the headless CMS, with the design developed in Figma. Content is separate from presentation, so the same articles can also be used on another channel.
What is a headless CMS?
A CMS that only manages content and makes it available through an API, without rendering the page itself. The editors work in the CMS; visitors see a separate front end.
How do you stop a blog from stalling under peak traffic?
With caching, hosting optimisation and limiting heavy queries on the busiest pages. The difference often isn't the CMS, but how the setup around it is built.
Can the editors change pages themselves?
Yes, that was the whole point. The content team publishes and makes changes without a developer.