CMS for a News Website: The 2026 Guide

Running a news site is a different sport from running a blog. You publish many stories a day, multiple writers hit "publish" at once, breaking news has to go live now, and last week's front page becomes this week's archive. The CMS underneath has to handle volume, multiple authors, fast publishing, and a URL structure that survives thousands of articles. Pick the wrong one and your team fights the tool instead of the deadline.

The short answer: a good news site CMS needs multi-author support, fast scheduled and instant publishing, categories/sections for the newsroom, and clean permalinks that scale. UnfoldCMS covers these for a self-hosted news or independent-media site, with role-based access for a real editorial team and an API to power a separate front end if you want one.

What does a news website need from a CMS?

A news CMS needs four things a blog CMS often lacks: multiple authors with roles (writer, editor, admin), instant and scheduled publishing, sections (Politics, Tech, Sports) not just tags, and a permalink structure that stays clean across thousands of articles. Speed and reliability under load matter more than fancy design.

The newsroom workflow is the real test. A writer drafts, an editor reviews and publishes, and the front page updates. Different people need different powers — a junior writer shouldn't be able to delete another author's story. That's role-based access control, and it's non-negotiable for a team site.

How does UnfoldCMS handle a multi-author newsroom?

UnfoldCMS uses Spatie's permission system for role-based access: a Super Admin bypasses all checks, and you create custom roles (writer, editor) through the admin with module- and action-level permissions. Each article has an author relation, so bylines and "articles by this writer" pages work out of the box.

The permission model is granular. Module permissions cover areas like blog.manage and users.manage, and action-level middleware controls things like delete rights. So you can build an editorial hierarchy:

• Writers create and edit their own drafts.
• Editors review, edit, and publish across the newsroom.
• Admins manage users, sections, and settings.

An activity log (Spatie ActivityLog is installed) records who changed what — useful when a correction needs a paper trail. This is the difference between a personal blog tool and something a newsroom can actually run on.

Can it handle breaking news and scheduling together?

Yes — you publish instantly by saving a story live, or schedule ahead by setting a future publish date, and the built-in scheduler flips scheduled stories live on time. It runs every minute and synchronously, so no queue worker is needed, and instant publishing is immediate.

This dual mode fits the news rhythm. Breaking story? Write it, publish now, it's live. Embargoed announcement or a planned feature for tomorrow morning? Schedule it and walk away. Because scheduled publishing runs on a simple cron entry (no background workers), it works on ordinary hosting without a complex infrastructure setup.

Corrections and updates are just edits — save the story again and the change is live. There's an honest limit worth stating: the CMS does not keep a full revision history, so it won't show a diff of every past version of an article. For most independent news sites that's fine; for a site that legally needs versioned audit trails, that's a gap to plan around.

News CMS options compared

The tradeoff: WordPress has the widest plugin ecosystem and built-in revisions but carries its well-known security and bloat baggage. A headless CMS gives you a pure API but no front end. UnfoldCMS sits in between — a modern self-hosted CMS with a clean admin and a real API, minus revisions.

Can you run a news site headless?

Yes. Every published article, section, and search is available over the /api/v1/* REST API, so you can build the reader-facing site in Next.js, Astro, or any framework and use UnfoldCMS purely as the editorial backend. There's no GraphQL — it's REST only — but the endpoints cover posts, categories, search, and menus.

This matters for a news site chasing speed. A statically generated or edge-cached front end pulling from the API loads fast for readers and survives traffic spikes better than a server-rendered page. And outgoing HMAC-signed webhooks let you trigger a rebuild on your host (Vercel, Netlify) the instant an editor publishes — so a breaking story deploys automatically without anyone touching the deploy pipeline.

If you'd rather not run a separate front end, the built-in templates render the news site directly. Either way you own the content and the data.

Is it built for SEO and news discovery?

News lives and dies by discovery — Google, Google News, and increasingly AI search. A news CMS has to emit clean metadata and structured data so a story is eligible for rich results and AI citation the moment it publishes. UnfoldCMS handles the on-page side: per-article seo_title and meta_desc, Article JSON-LD schema via the @jsonld() directive, an auto-generated XML sitemap, and a dynamic robots.txt.

It also ships /llms.txt and /llms-full.txt files that expose your content to AI crawlers like Perplexity and ChatGPT in the format they read — so your reporting can be quoted in AI answers, not just blue links. Slug history plus the redirect module means restructuring your sections later never breaks an inbound link or a story shared on social. One honest note: there's no dedicated Google News sitemap generator built in, so if you're pursuing formal Google News inclusion you'd add that piece yourself, but the standard sitemap, schema, and fast publishing get most news sites indexed quickly.

FAQ

Can I run a news website on UnfoldCMS? Yes. It supports multiple authors with role-based permissions, instant and scheduled publishing, hierarchical sections, clean permalinks, and a REST API. It's built for self-hosting, so you own the content and reader data — suitable for independent news and media sites. The main gap versus WordPress is no built-in article revision history.

How do multiple writers and editors work? Through Spatie role-based access control. You create roles like writer, editor, and admin with module- and action-level permissions, so writers edit their own drafts while editors publish across the newsroom. Each article has an author byline, and an activity log records who changed what.

Can I publish breaking news instantly? Yes. Save a story as published and it's live immediately. You can also schedule stories for a future time, and the built-in scheduler (running every minute, synchronously) makes them live on time. Both modes work on ordinary hosting with a single cron entry — no queue worker needed.

Does it keep a revision history of articles? No. UnfoldCMS doesn't store past versions of an article, so there's no version diff or rollback. Corrections are edits that overwrite the previous body. For most independent news sites this is fine; if you legally need a versioned audit trail, plan for that gap or add external tracking.

Can I build the news front end separately (headless)? Yes. The /api/v1/* REST API serves posts, categories, search, and menus, so you can build the reader site in Next.js, Astro, or any framework. HMAC-signed webhooks can trigger an automatic rebuild on publish. Note it's REST only — there's no GraphQL endpoint.

How does it handle sections like Politics or Sports? With hierarchical categories. Each section is a category (which can have sub-sections), and articles are assigned to one or more. Category pages list every article in a section, and the API exposes per-category article lists for a headless front end. This gives a news site the section structure a flat tag system can't.

The bottom line

A news site needs a CMS built for teams and volume: multiple authors with real roles, instant plus scheduled publishing, sections, and a URL structure that scales. UnfoldCMS delivers those with Spatie RBAC, a modern admin, and a REST API for going headless — self-hosted so you own every story and reader. The one thing to plan around is the lack of article revision history. For an independent news or media site that values ownership and a clean editorial workflow, it's a strong fit.

See the admin and API: live demo · features · docs.

Related: CMS for an online magazine · CMS for a publisher · CMS for a content hub