Skip to main content

Tag · 27 essays

CMS

Writing tagged "CMS".

← All writing

Most CMS migrations fail before the first record moves

CMS migrations fail not because of the new platform but because nobody cleaned up the mess before packing it into boxes. Bad content models get locked in, integrations get reverse-engineered at midnight, legacy logic resurfaces as unexplainable bugs, and composable architecture without discipline becomes distributed chaos. The only thing worse than a painful migration is a successful one that preserved all your worst decisions.

  • Composable architecture
  • CMS
  • Frontend
  • Product strategy

The future of software is bespoke

This article argues that generic SaaS dashboards are a legacy compromise from a time when custom software was expensive and slow to build. With modern APIs, solid SDKs, scaffolding, and AI-assisted development, teams can now create focused, bespoke interfaces in days that match their exact workflows, instead of fighting through one-size-fits-all UIs. The platform should be treated as the engine providing authentication, permissions, content modeling, and governance, while product teams own the experience layer tailored to their people. The piece also examines trade-offs like maintenance burden, skills gaps, and fragility, and explains how good scaffolding, community patterns, and developer education can mitigate these risks and make custom tooling a pragmatic default.

  • Composable architecture
  • CMS
  • API design
  • Frontend

Your legacy patterns are technical debt in modern architecture

Developer teams migrating from legacy to modern architecture often bring old habits that become technical debt. Executive pressure and budget constraints drive rushed migrations without adapting to new paradigms. Success requires stopping to discover how modern systems actually work, designing ideal workflows without legacy constraints, and recognizing that migration is about transforming how you model and manage content, not just moving it between systems.

  • Composable architecture
  • CMS
  • Craft

AI integrations expose platforms without headless DNA

AI exposes which platforms were truly built API first and which ones only marketed it. As brands move into AI native workflows, the only viable path is a system that treats agents, events, and automation as composable building blocks. Contentstack's agentOS shows what happens when you start with API first DNA instead of bolting AI onto a monolithic core. This piece explains why AI native composability is the next logical layer of MACH and why brands should judge vendors by the architecture of their agents, not the slideware that surrounds them.

  • Composable architecture
  • AI engineering
  • CMS
  • API design

The MACH monolith in 2026

The 2022 diagnosis was right. Composable architectures need orchestration or they collapse. But the form factor was wrong. Teams rejected standalone orchestration layers as too heavy, another vendor, contract, and critical path. The 2026 reality is platforms that integrate orchestration directly, staying API-first and modular while providing built-in coordination. The shift isn't about more tools, but smarter platforms that reduce complexity fatigue without losing flexibility.

  • Composable architecture
  • AI engineering
  • CMS
  • API design

It's time to think of LLMs as having abilities, not protocols

TL;DR Don't over-engineer standards around protocols. Instead, treat your large-language-model as a toolbox of abilities (like search, translate, query, generate) that you plug into your system. By thinking of LLMs as modular and composable abilities rather than monolithic protocols, AI becomes accessible, practical and aligned with how engineering and product teams already build.

  • Composable architecture
  • AI engineering
  • CMS
  • API design

SDKs are everywhere. But should you use them?

Explore the significance of Software Development Toolkits (SDKs) in modern development, their advantages, and when you might want to skip them. From enhancing productivity to integrating complex functionalities seamlessly, the right SDK can accelerate your projects. But what about GraphQL-based systems or the flexibility of headless architectures? Dive into the pros and cons to make an informed decision.

  • Composable architecture
  • CMS
  • API design
  • Performance