"You should never build a CMS"
2 days ago
- #ContentManagement
- #AI
- #CMS
- Lee Robinson migrated cursor.com from Sanity to markdown files, GitHub, and Vercel, citing issues with CMS complexity and AI agent accessibility.
- Sanity acknowledges valid criticisms of headless CMS, including clunky preview workflows, auth fragmentation, and unnecessary complexity.
- Despite moving away from a CMS, Lee's solution still incorporates CMS-like features such as asset management, version control, and content modeling.
- Markdown and git workflows have limitations at scale, including difficulties with content reuse, collaboration, and querying structured data.
- Structured content with a query language is more suitable for AI agents than markdown files, enabling better content management and retrieval.
- Sanity's new MCP server aims to address these issues by providing structured, queryable content accessible to AI agents through APIs.
- The debate should focus on building content infrastructure that supports AI as both author and consumer, rather than choosing between CMS and no CMS.