WeSearch

When AI can write your code, do you still need a CMS?

David Demaree· ·8 min read · 0 reactions · 0 comments · 32 views
#technology#ai#content management
When AI can write your code, do you still need a CMS?
TL;DR · WeSearch summary

The debate over the necessity of content management systems (CMS) in the age of AI-driven coding continues. While some argue that AI can replace traditional CMS tools, others maintain that CMS features address real underlying problems. Ultimately, the choice between using a CMS or coding directly hinges on the speed at which different parts of a website need to change.

Key facts
How this story was covered

2 outlets in our directory ran this story, first to last over 11 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 1
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 2,866 of its stories.

Original article
Bits&Letters · David Demaree
Read full at Bits&Letters →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherBits&Letters
Canonical URLhttps://www.bitsandletters.com/ideas/do-you-still-need-a-cms-with-ai
Publication timeWed, 20 May 2026 22:05:17 +0000
Retrieval time2026-05-20T22:15:03.058Z
Last seen2026-05-20T22:15:03.058Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Clusterxvb_IOgWtxTv · 2 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Ideas When AI can write your code, do you still need a CMS? It’s less about the tooling and more about who needs to change which parts of your website at which speeds. David Demaree May 20, 2026 Lately there's been a debate about whether, in the era of vibe-coding and agentic AI, anyone still needs a dedicated content management system — or whether you can just keep everything in text files and let Claude or Codex handle the rest.Last fall, Lee Robinson from Cursor wrote about his team's move away from Sanity (our favorite CMS) toward Markdown files, HTML templates, and their own AI agent. Sanity's Knut Melvaer responded with the case that CMS features exist because the underlying problems are real, and that bespoke tooling will accrete complexity until you've reinvented one anyway.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Bits&Letters.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Bits&Letters