Structured content distribution is the decoupling of content from presentation through a headless CMS and Content as a Service (CaaS) architecture. It is a sound strategy for organizations managing complex content distribution networks across multiple channels. 

To be the most successful, this digital transformation requires organizations to change both their publishing workflows and their content ownership structures. Governance complexity affects 41% of CaaS adopters (PDF), workflow mismatches impact a third, and training requirements average 14 to 18 weeks. 

We have implemented these systems for clients in healthcare, financial services, and higher education, and the pattern is consistent: the three failures that kill structured content initiatives are the preview gap, the ownership vacuum, and the training deficit. Here is what we have learned about each one — and what actually works.

The Promise 

The pitch for structured content distribution is compelling: create content once, store it as modular data in a headless CMS, deliver it via API to any channel (web, mobile, kiosks, AI agents) without reformatting. The CaaS market is projected to reach $2.8 billion by 2035, and over 65% of enterprises have adopted headless CMS architectures.

What they do not tell you is that integration challenges affect 46% of adopters using legacy CMS platforms, and that 31% of enterprises encounter deployment delays exceeding six months. The technology works, but the governance requires just as much attention and is often overlooked. We have seen this avoidable pattern repeat across many structured content implementations.

Why Do Structured Content Migrations Stall?

In short, because organizations implement the technology without redesigning how their teams create, review, approve, and own content. That’s the governance problem.

A headless CMS decouples content from presentation. But most editorial teams have spent years, sometimes decades, working in systems where creating content and seeing how it looks are the same activity. WordPress, Drupal, and even SharePoint have a visual editing experience: build a page, see the page, publish the page.

Structured content does not work this way. Authors fill in fields like title, body, metadata, and related entries to publish content objects, not pages. As one analysis of Contentful’s editorial interface notes, “content editors work in structured content entry forms without seeing how content will render in production.” The front-end determines how those objects appear to users.

That architectural distinction is the correct one for consistent omnichannel delivery. It is also the one most likely to break editorial workflow expectations when teams do not deliberately plan for this big shift. In our experience, three governance failures account for the vast majority of structured content stalls.

What Is the Preview Gap, and Why Does It Derail Teams?

The preview gap is the loss of visual context that editorial teams experience when moving from a WYSIWYG (what you see is what you get) environment to a structured content interface, and it is the most immediate friction point in any headless CMS migration.

Authors who previously built pages visually are now filling in form fields and trusting that a front-end will render them correctly. The shift from “building a page” to “managing a content object” takes adjustment, and “once teams adapt, the structured approach tends to produce more consistent, reusable content.” The problem is what happens before they adapt.

What happens is that authors create workarounds. They paste formatted content into rich text fields, breaking the structured model. They submit tickets to developers asking “what will this look like?” multiple times per week. They maintain shadow documents in Google Docs so they can see their work in context. Every workaround is a governance failure — content that exists outside the system, formatting that undermines the content model, and developer time consumed by preview requests instead of feature development.

The planning that pays off includes building live preview environments for as many content sources as possible. This development work typically gets deprioritized because it is not user-facing, but it determines the success of the new system. As one migration guide puts it, headless platforms deliver excellent editorial experiences “when configured correctly — visual editing, live preview, flexible page-building, role-based permissions. But that configuration is work, it doesn’t happen by default.” Budget for it, build it first, and do not launch editorial access without it.

What Is the Ownership Vacuum?

The ownership vacuum is what happens when structured content crosses departmental boundaries without clear governance over who maintains the content model, who approves changes to shared components, and who is accountable when content is reused in a context the original author never intended.

In a traditional CMS, the marketing team owns the marketing pages, the product team owns product pages, etc. Structured content breaks this model deliberately — a product description created once might appear on the website, in a mobile app, in an email campaign, and through a chatbot simultaneously. But governance complexity affects 41% of CaaS adopters, and multi-team collaboration across 6 to 10 departments increases governance overhead by 27%.

Questions seldom asked include: 

We have seen organizations discover these questions six months post-launch, usually during a content audit that reveals inconsistencies no one can trace. In regulated industries — healthcare, financial services, higher education — those inconsistencies are compliance risks.

Knowing these pitfalls ahead of time can lead to the establishment of a content model governance board before migration begins. A small, cross-functional group (typically 3 to 5 people spanning content strategy, development, and compliance) owns the content model as a shared organizational asset. They approve changes to content types, evaluate reuse implications, and maintain a living inventory of where shared content objects appear. This role does not exist in traditional CMS organizations because it’s not needed. But in structured content environments, it is absolutely necessary.

Why Does the Training Deficit Compound Everything?

Because organizations allocate 90% of their transformation budgets to technology and implementation, and only 10% to change management — the part that determines whether anyone actually uses the system they built.

Training requirements for CaaS implementations average 14 to 18 weeks, the elapsed time from initial exposure to genuine editorial fluency. This training creates the confidence for authors to create, structure, and publish content without reverting to old habits or filing developer tickets. Most implementation budgets account for a one-day training session and a knowledge base article. The gap between that and actual fluency is where adoption dies.

The compounding effect of the training deficit makes this particularly damaging. Undertrained authors hit the preview gap and panic. Without clear governance ownership, there is no one to answer their questions authoritatively. They build workarounds. Those workarounds corrupt the content model. The corrupted content model undermines the case for structured content. Stakeholders lose confidence. The transformation stalls.

BCG’s study of 850+ companies found that only 35% of digital transformations meet their value targets globally. The failure rate is a change management problem that looks like a core problem with the technology itself.

To avoid this failure spiral, structure editorial onboarding as a phased engagement, not a one-and-done event. In our implementations, we start with a pilot group of 3 to 5 authors working with the system while the front-end is still being built. They surface friction points the development addresses in real-time. When the broader editorial team is onboarded, the common pain points have been resolved, and the pilot group serves as advocates who can answer questions and support their peers. This approach adds little cost and dramatically improves adoption velocity.

What Should Organizations Do Before Starting a Structured Content Migration?

Treat governance design as a foundation to build a successful digital transformation:

  1. Audit your editorial workflows as they actually operate. Map who creates content, who reviews it, who approves it, and where informal workarounds exist. As one migration planning guide advises, most publishing workflows “are often based on legacy systems, informal approvals, or staff availability. The result? Delays, missed steps, and content that never quite gets finished.” Your structured content governance must account for the real workflow, not the theoretical one.
  2. Define content model ownership before selecting a platform. Determine who will own the content model as an organizational asset, who can request changes, and what the approval process looks like. This governance structure should be platform-agnostic — it is an organizational decision, not a technical one. We have helped clients build this through our roadmapping and strategy engagements, and it consistently reduces mid-project governance confusion.
  3. Budget for editorial experience parity. If your authors currently have WYSIWYG editing, live preview, and visual page building, do not assume they will accept a simpler and more limiting form-based interface. Calculate the development effort required to provide contextual preview in your new architecture and include it in the implementation scope, not as a phase-two enhancement. Phase two rarely arrives before editorial frustration does.

Wrap Up

The CaaS pitch is not wrong. Structured content distribution is the right architecture for organizations publishing across multiple channels, and it is increasingly the right architecture for AI readiness — structured data is what AI systems consume most effectively. But the promise underestimates the organizational effort to make it successful.

Technology is the easy part. Governance, training, and editorial adoption are harder, and that is where implementations succeed or fail.

We have built these systems on Contentful, Drupal, and composable architectures for organizations in regulated industries where getting content wrong has real consequences. The lesson we keep relearning is the same one: start with the team, not the platform.

The Business Context

CarGurus operates one of the largest online automotive marketplaces in the U.S. Its revenue model depends on dealer subscriptions. Dealers pay for access to shopper data, market intelligence, product tools, and business support. When that relationship is mediated by digital, the quality of the digital experience is not a design question. It is a retention question.

By 2019, the infrastructure supporting that relationship had become a strategic liability.

The Problem: Digital Debt at Scale

CarGurus’ dealer-facing web presence had grown organically into a collection of disconnected properties: multiple WordPress sites, a gated resource center, a product microsite, and a dealer dashboard. Each operated independently, with different workflows, separate analytics, and no shared content standards.

The consequences were structural, not merely cosmetic.

For internal teams: The B2B marketing team could not publish or update content without engineering support. Campaign velocity, product launches, and content strategy were bottlenecked by a dependency that had nothing to do with marketing capability. Without centralized reporting, leadership had no way to understand what was working or where dealers were dropping off.

For dealers: Research and interviews surfaced a consistent pattern. There was no obvious place to log in, product information and help content scattered across destinations, and shopper data siloed away from the resources that gave it context. The experience communicated the opposite of CarGurus’ intent. Dealers found fragmentation where they expected authority. Pre-consolidation data made the cost of that fragmentation concrete. The Dealer Resource Center carried a bounce rate of 61.57%, the Insights pages topped 80%, and the bulk of visitors spent fewer than 10 seconds on the site. Nearly 15% of dealers reported struggling to find information, with the disjointed experience cited as the primary reason. 

For compliance: Accessibility gaps across the WordPress properties introduced regulatory risk and excluded users relying on assistive technology, a segment of the dealer population that was simply invisible.

The problem was not any single site. It was the absence of a system.

The Diagnosis

Most agencies, presented with this problem, would have proposed a website redesign. Oomph diagnosed something different. CarGurus did not have a website problem, they had an operating model problem that manifested through websites.

The fragmentation was a symptom of three root causes:

  1. No content governance model. Without shared standards, each property developed its own editorial process, its own taxonomy, its own way of doing things. Content proliferated without coherence.
  2. No editorial independence. The marketing team’s dependency on engineering for routine publishing created a structural bottleneck that compounded over time. Every campaign, every update, every product launch queued behind engineering capacity.
  3. No shared measurement. Without centralized analytics, CarGurus could not connect dealer behavior across properties, could not identify friction points in the engagement journey, and could not make evidence-based decisions about where to invest.

Fixing any one of these without the others would have reproduced the same problem on a new platform.

The Solution: A Dealer Engagement System

Oomph began with structured discovery across sales, support, UX, and marketing using stakeholder interviews, a full content audit,  heatmap analysis, and a card sort exercise to understand how dealers actually navigate and categorize content. The critical finding was that dealers organized information around their workflows and tasks, not around CarGurus’ internal team structures. The existing architecture reflected the org chart. The new one needed to reflect the dealer. Dealer research also surfaced where content investment would matter most. 38.78% of dealers were very interested in digital marketing best practices, and 36.12% in automotive marketing best practices, two content categories that had been scattered or buried across the fragmented properties.

From that research, Oomph designed and built three interconnected capabilities.

A Unified Content Platform

Three separate sites, the Dealer Resource Center, the Dealer Account Request page, and the product microsite at products.cargurus.com, were consolidated into a single governed destination. The Contentful-based content portal consolidated Articles, Events, Products, Authors, and reusable Design Components into a single governed destination, with localization for the Canadian market. The content model was documented and governed, giving the marketing team full editorial control without engineering dependency.

Centralized Measurement

One destination meant one analytics framework. For the first time, CarGurus could track dealer engagement across the entire content ecosystem, not property by property, but as a coherent journey. Internal teams could direct every channel to the same URL, building familiarity and reinforcing the hub over time.

Systematic Accessibility Remediation

Accessibility work ran in two phases, starting with the existing WordPress properties (addressing contrast failures, empty labels, and keyboard navigation gaps), then post-launch across three Contentful-based sites targeting WCAG 2.1 compliance. Remediations included fixing keyboard navigation and adding tab focus rings across dropdown menus, correcting color contrast ratios to meet the WCAG 4.5:1 standard in headers, forms, and FAQ blocks, adding alt text to logos and informational icons, and converting static chart images into accessible HTML formats. This was not a one-time fix but a repeatable compliance process designed to scale with the platform.

What Changed

Operational velocity: The marketing team gained the ability to publish, update, and govern content independently, removing the bottleneck that had constrained their ability to execute for years.

Dealer experience: Three sites became one. Dealers gained a single, consistent destination for products, services, research, and account access. The experience shifted from fragmented and frustrating to coherent and navigable. Where pre-consolidation data showed bounce rates above 61% and the majority of visitors spending fewer than 10 seconds on site, the unified hub gave CarGurus the structural foundation to actually retain and re-engage that audience.

Strategic visibility: Centralized analytics replaced fragmented multi-site tracking, creating a shared foundation for understanding dealer behavior and making evidence-based decisions about content investment, product positioning, and engagement optimization.

Market reach: Accessibility remediation across five properties extended the platform to dealers using assistive technology, a population that had been excluded by the previous architecture.

The Strategic Takeaway

Complex B2B organizations accumulate digital debt one property at a time. By the time the cost becomes visible, it has already slowed marketing, obscured what matters, and turned internal fragmentation into a customer-facing problem.

CarGurus’ situation is common. What made the engagement different was the diagnosis. The dealer experience needed to be treated as an integrated system rather than a collection of sites to be redesigned. The distinction matters. A site redesign solves today’s problem. A system creates the infrastructure to solve tomorrow’s.

Oomph delivered the architecture, governance model, and editorial capability for CarGurus to keep improving dealer engagement over time, not as a one-time project, but as an ongoing organizational capability.

Ready to turn your digital fragmentation into a system? Let’s talk about what’s possible for your organization.

Bill Gates wrote “Content is King” back in 1996. He was right for about thirty years. On the open web, the winners were the ones who could produce, distribute, and monetize content at scale. That era shaped how we built digital products, how we organized marketing teams, and how we thought about content platforms.

That era is getting a new chapter.

When content becomes context

In the age of agents, content is context. It’s the raw material an AI uses to answer a customer’s question, draft a proposal, summarize a policy, or make a decision on behalf of your business.

If your context is a mess, your agent is a mess. Garbage in, confident-sounding garbage out.

For organizations in healthcare, higher education, and associations (industries where we work every day) that governance layer isn’t a nice-to-have. A health system deploying an agent to answer patient questions needs to know which clinical protocol is current, who approved it, and what the agent is and isn’t allowed to cite. An association managing member benefits can’t afford an agent that surfaces a two-year-old policy document as current guidance. And it’s not just the regulated organizations themselves. The enterprise technology companies that serve these industries, the SaaS platforms, the data providers, the system integrators, face the same challenge: if the content powering their products isn’t structured and governed, the agents built on top of it will inherit every gap. The stakes in regulated industries make the content-as-context problem concrete and urgent, but the same dynamics show up everywhere brand, voice, and accuracy matter: retail pricing, financial disclosures, B2B product specifications, public sector policy. Different risk profiles, same fundamental problem.

This isn’t theoretical. Gartner predicts that 40% of enterprise applications will include task-specific AI agents by the end of 2026, up from less than 5% in 2025. The shift is already moving from prediction to product.

The platforms we work with every day show the movement clearly. The Drupal AI Initiative launched last June and hit $1 million in funding within five months, with the Drupal AI and AI Agents modules reaching production-ready status in October 2025. Acquia built on that foundation with Acquia Source, shipping three AI agents for its Drupal-powered SaaS CMS in December. Contentful open-sourced its MCP server and has been publishing active guidance on agentic content operations. These aren’t experiments. They’re shipping.

Across the category, the pattern is broad. Contentstack launched Agent OS in September 2025 and introduced what it calls the “Context Economy” as its positioning. Kontent.ai shipped what it calls an Agentic CMS the following month. The Model Context Protocol that Anthropic introduced in late 2024 has become the connective tissue, adopted by OpenAI, Google DeepMind, and most of the CMS world.

The platforms are ready. The question is whether your content is.

What agents actually need

An agent doesn’t want a rendered web page. It wants structured, canonical, permissioned, versioned truth. That means:

That’s the same job a mature content platform has been doing for years, just pointed at a new kind of consumer.

We’ve seen this movie before

Every channel shift exposes whether your content was ever really structured to begin with. CD-ROM, then the web, then mobile, now agents. Each one forces organizations to untangle content from presentation. Headless CMS platforms like Drupal, Contentful, Sanity, and Strapi won that argument. Content as structured data, delivered via API, rendered wherever you need it.

Agents are the most demanding channel yet. They don’t just display your content. They consume it, reason over it, and then take action. If your content is trapped inside HTML blobs or buried in PDFs that no one’s touched since 2021, it’s not ready to be context. Structure is the whole game now.

Where context lives today

Right now, company context is scattered across:

Some of these are built for governance. Most aren’t. GitHub is hands-down great for technical content and version control, but marketing and legal teams aren’t opening pull requests to update a pricing page. Notion is excellent for collaboration, weak on structured content models and role-based delivery. Every organization I talk to has some version of this scatter, and it’s about to become a much bigger problem.

The rise of the Context Management System

The old acronym still works. CMS. New job.

Headless CMS platforms have quietly solved about 70% of what agents need. Structured content models. API-first delivery. Editorial workflows. Roles and permissions. Versioning. Audit trails. What they’re adding now is the connective tissue. Acquia is embedding AI agents directly into Drupal-powered workflows through Acquia Source, and Contentful has open-sourced its MCP server to let agents take action on content operations. Across the rest of the category, Sanity launched its Content Agent in January 2026, and Storyblok, Brightspot, and dotCMS have released MCP servers of their own. MCP servers, vector indexing, semantic metadata, agent-optimized delivery endpoints. That’s a much smaller leap than building the whole governance layer from scratch.

The “just throw it all in a vector database” approach has real merit as a retrieval layer. Retrieval is one job. Governance is a different one: who owns canonical truth, who approved the content, when it expires, and who’s allowed to see it. That’s always been the CMS job. It matters more now, not less.

For teams working on Drupal, Contentful, or Acquia Source, this is encouraging. The architectural decisions those platforms made years ago (structured data, granular revisioning, API-first design) turn out to be exactly what AI agents need. Your investment in content architecture is paying off in ways you didn’t plan for. Call it a head start.

What to do about it

If you’re building agentic products, or planning to, the content question is the quiet one that will bite you later. This is the work we’re spending most of our time on with clients right now. A few forward moves:

  1. Audit where your content actually lives and who owns it. You will be surprised.
  2. Pick a source of truth for each category of content. Don’t let five systems claim the same ground.
  3. Get your structured content models right. If your content is trapped inside HTML, it isn’t ready to be context.
  4. Build the governance layer before you need it. Versioning, permissions, approval workflows. Your legal team will thank you. So will your agent.
  5. Connect your CMS to your agents via MCP or equivalent. This is how context flows. Do it early.

Content was king when the battle was for attention. Context is king now that the battle is for correctness. Agents are only as good as the material you feed them, and that material has to be managed with the same rigor we’ve applied to code, to data, and yes, to content itself.

The organizations that treat content governance as infrastructure, not a cleanup project, will be the ones whose agents are trustworthy from day one. That window is shorter than it looks.

Selecting a content management system in healthcare is no longer a purely technical decision. In today’s environment, a CMS directly impacts compliance, accessibility, speed to publish, and ultimately, trust. Healthcare organizations are under growing pressure to deliver accurate, timely information across multiple digital channels, while meeting strict regulatory and accessibility requirements. The CMS at the center of that effort needs to support far more than page updates.

Why Healthcare CMS Decisions Are Uniquely Complex

Healthcare websites serve a wide range of audiences, from patients and caregivers to providers, partners, and regulators. Content must be clear, accurate, and easy to update—often by multiple teams—without introducing risk.

At the same time, healthcare organizations face constraints that many other industries don’t. Accessibility standards, privacy expectations, and governance requirements are non-negotiable.

A CMS that lacks flexibility or control quickly becomes a bottleneck.

“The healthcare content management system market is projected to grow to over $61 billion by 2031, underscoring how healthcare organizations are prioritizing modern, scalable digital platforms to support compliance, multi-channel delivery, and governance.”

According to Mordor Intelligence

What Healthcare Teams Should Prioritize

Flexibility Without Compromising Security

Healthcare organizations often rely on complex digital ecosystems, including EHRs, portals, analytics tools, and consent platforms. A modern CMS should integrate cleanly with these systems rather than trying to replace them.

Flexibility matters, but not at the expense of security. The right CMS supports modular integration while keeping sensitive data protected and clearly separated from content operations.

Planning For Change, Not Just Launch

CMS selection shouldn’t be based solely on current needs. Healthcare regulations, digital expectations, and technologies continue to evolve. The most effective platforms are designed to adapt without requiring frequent replatforming.

This means supporting incremental improvements, phased rollouts, and long-term scalability—so teams can modernize at a pace that aligns with organizational priorities.

The Role Of Modern, Composable CMS Platforms

Composable CMS platforms are gaining traction in healthcare because they treat content as structured data rather than static pages. This approach supports reuse, consistency, and omnichannel delivery while maintaining governance.

For healthcare teams, this translates into faster publishing, fewer bottlenecks, and greater confidence in content accuracy without sacrificing compliance.

What This Means For Healthcare Teams

Healthcare CMS selection is about more than choosing a tool. It’s about enabling teams to communicate clearly, operate efficiently, and adapt responsibly in a complex digital landscape.

Organizations that prioritize governance, accessibility, and flexibility position themselves to deliver trusted digital experiences today and in the years ahead.

Ready to Evaluate Your Healthcare CMS? Our team helps healthcare organizations navigate complex CMS decisions with a focus on governance, accessibility, and long-term scalability. Let’s talk about what the right platform looks like for your organization.

To avoid significant financial penalties, which increased on January 1, 2025 to up to $7,988 per intentional violation, your website must function as a compliant interface for consumer privacy rights. Use this checklist to assess your current standing.

1. Mandatory Homepage Links

2. Automated Privacy Signals (Global Privacy Control)

3. Notice at Collection

4. Consumer Rights Intake (DSARs)

5. Technical & Policy Maintenance

Explore WCAG

Is your website one missing link or undetected signal away from a costly CCPA violation? Oomph’s team can walk you through a compliance audit, identify gaps in your current setup, and help you implement the technical and content updates needed to protect your organization. Get in touch with us today to book your CCPA compliance call.

Website accessibility has shifted from a “best practice” to a strictly codified legal requirement. Federal and state regulations have eliminated previous ambiguities, making WCAG 2.1 Level AA the mandatory technical standard for digital content. With updated deadlines now in place, organizations have a renewed window to get it right.

1. The Compliance Deadline: What’s Changed

The U.S. Department of Justice (DOJ) finalized a rule under Title II of the ADA that sets a firm compliance deadline for many entities:

2. Why WCAG 2.1 Level AA?

Unlike older versions, WCAG 2.1 includes 17 additional criteria specifically designed for mobile accessibility and users with cognitive disabilities. Compliance is measured by the “POUR” Principles:

3. Compliance Risks to Keep in Mind

4. Future-Proofing: Looking Toward WCAG 3.0

While WCAG 2.1/2.2 is the current law, WCAG 3.0 is in development (expected no earlier than 2028). It will move from a pass/fail model to a Bronze, Silver, and Gold scoring system. Achieving WCAG 2.1 Level AA now effectively places an organization at the “Bronze” level, providing a solid foundation for future shifts.

Is your website ready for the April 2027 deadline? Achieving WCAG 2.1 Level AA compliance requires more than a quick fix. It means addressing the underlying code, auditing every digital asset, and building accessibility into your process from the ground up. Whether you’re starting an audit, planning remediation, or building something new, get in touch with our team to start the conversation.

Overview

edX operates one of the world’s largest digital learning catalogs, serving millions of learners through professional certificates, microcredentials, and degree programs from top universities and institutions worldwide. As the platform evolved from its MOOC origins into a revenue-driving marketplace of credentialed programs, digital experience became central to competitive differentiation and learner acquisition.

The challenge wasn’t course quality or platform stability—it was operational velocity. Marketing teams couldn’t move fast enough to support growth, and the content architecture that served 1,000 courses was breaking under the weight of 4,000. For edX and parent company 2U, this represented a structural constraint on growth, not a publishing workflow problem.

The Challenge

When Content Architecture Becomes a Growth Limiter

edX faced a common problem for organizations operating at scale: their content and data systems were tightly coupled, creating dependencies that slowed marketing execution and limited experimentation.

Discovery Was Breaking at Scale: Thousands of courses existed in internal systems of record, but marketing pages struggled to surface the right context—audience fit, learning outcomes, format options, and credential value. Paid and organic traffic landed on pages that couldn’t adapt to query intent or learner type, creating friction in the conversion path.

Content Velocity Required Engineering: Every new program launch, campaign page, or SEO test required custom development. Editors faced a choice between rigid templates that couldn’t express program nuance or hard-coded pages that created bottlenecks with engineering. This constrained speed to market and limited the team’s ability to test, iterate, and optimize.

Platform Coupling Created Organizational Drag: Course metadata lived in proprietary databases. Marketing narratives lived elsewhere. Assembling a page required manual coordination across systems and teams. For a platform competing in an increasingly crowded eLearning market, this wasn’t a workflow issue—it was a structural constraint on growth capacity.

Our Approach

Building a Content Operating System for Scale

Oomph worked with edX to design and implement a content architecture that decoupled marketing execution from platform dependencies. The goal wasn’t to replace existing systems—it was to create the right separation of concerns so teams could operate independently at scale.

System Design: Oomph implemented Contentful as a central content orchestration layer, integrated with edX’s existing course databases. Course data remained authoritative in internal systems, while marketing and narrative content moved into a structured CMS. Pages were dynamically assembled using structured course metadata, modular editorial content, and reusable components governed by design system rules.

This architecture allowed edX to scale content output without duplicating data, increasing engineering dependency, or sacrificing brand consistency.

Content Governance at Scale: Oomph structured content models and component libraries to enforce design system standards while giving editors flexibility to adapt messaging by audience, channel, or campaign. Taxonomy and metadata schemas were designed to support SEO systematically rather than through manual optimization. Reusable content patterns minimized duplication across credential types and program categories.

Operational Enablement: The system was designed to shift content creation and optimization from engineering to marketing. Editors could launch program pages, build campaign landing experiences, and iterate based on performance—all without custom development. This freed engineering to focus on platform capabilities while giving marketing teams the speed and flexibility needed to support business growth.

What This Made Possible

The new content architecture fundamentally changed how edX’s marketing teams could operate:

Speed to Market: New program launches no longer required bespoke page builds or engineering sprints. Campaign landing pages could be adapted by audience segment or acquisition channel in real time. Testing and iteration became routine rather than exceptional.

Systematic SEO: Content structure improved indexability across thousands of URLs. Program-level pages could be optimized without breaking templates or creating technical debt. Internal linking, metadata, and taxonomy became consistent by design rather than through manual intervention.

Scalable Operations: Following launch, edX published approximately 1,000 new pages without additional headcount. Content creation centralized into a single system of record, eliminating duplicate workflows and reducing coordination overhead. Marketing teams gained operational independence while maintaining governance and brand standards.

Foundation for Performance: The system created a clear path for data-informed optimization. Structured content made A/B testing feasible at scale. Clear ownership and reduced dependencies positioned the team to measure, learn, and iterate on conversion performance over time.

The result

edX transformed its content operations from project-based execution to a scalable operating model. Marketing teams gained the speed and flexibility to support growth while maintaining brand consistency and governance at scale. Engineering dependencies for routine marketing needs were eliminated, freeing technical resources for platform innovation.

For higher-ed and eLearning platforms competing on learner experience and acquisition efficiency, this represents a shift in operating model—not just a technology implementation.

As part of ongoing platform optimization, edX implemented Cloudflare image optimization to improve Core Web Vitals, reduce bandwidth consumption, and enhance performance for global users—demonstrating the kind of continuous improvement the new architecture was designed to support.

Why This Matters

Organizations operating digital marketplaces face a common tension: growth requires speed and flexibility, but scale requires structure and governance. The answer isn’t choosing between the two—it’s designing systems that deliver both.

Oomph’s work with edX demonstrates how strategic content architecture can unlock operational capacity without adding headcount, enable marketing velocity without sacrificing brand standards, and create the foundation for data-informed optimization at scale.

This is how complex organizations move the metrics that matter: by building resilient systems that scale, adapt, and perform.

Contentful is no longer just an alternative CMS—it’s become a foundational platform for organizations navigating complexity, regulation, and rapid digital change. In 2026, the question isn’t what is Contentful? It’s why are so many organizations rebuilding their digital ecosystems around it? The answer lies in how digital experiences are built, managed, and scaled today.

Contentful Is Built for Systems, Not Pages

Traditional CMS platforms were designed around pages and templates. That model breaks down when content needs to move faster, live in more places, and remain consistent across teams and channels.

Contentful takes a different approach. It treats content as structured data, not static pages. That means teams create content once and deliver it anywhere—websites, apps, portals, email, or future channels that don’t yet exist.

In 2026, this isn’t a “nice to have.” It’s how modern digital platforms operate.

Composable Architecture Is Now the Default

Composable architecture has moved from trend to standard. Organizations want the freedom to choose best-in-class tools without being locked into monolithic platforms.

Contentful fits cleanly into this model. It integrates with design systems, analytics platforms, personalization tools, consent managers, and AI services through APIs—without forcing teams into rigid workflows.

This flexibility allows organizations to evolve their stack over time instead of rebuilding every few years.

AI Depends on Structured Content

AI-driven experiences are only as good as the content behind them. In 2026, organizations are using AI to support personalization, search, localization, content optimization, and automation.

Contentful’s structured content model makes this possible. Clean, well-defined content enables AI tools to understand, reuse, and adapt content accurately—without introducing risk or inconsistency.

For teams exploring AI responsibly, Contentful provides the infrastructure needed to scale with confidence.

Governance and Compliance Are Built In, Not Bolted On

For regulated and mission-driven organizations, governance isn’t optional. Publishing controls, audit trails, permissions, and review workflows are essential.

Contentful supports these needs at scale. Teams can define roles, control who edits or publishes content, and maintain visibility into changes across environments. This level of governance is critical in industries like healthcare, legal, finance, and the public sector.

In 2026, compliance isn’t something teams add later—it’s designed into the platform from day one.

Marketing and Development Work Better Together

One of Contentful’s biggest advantages is how it aligns marketing and engineering teams. Developers maintain design systems and integrations. Content teams manage content without breaking layouts or workflows.

This separation of concerns reduces friction, speeds up delivery, and minimizes production errors—especially as digital ecosystems grow more complex.

Ready to explore what Contentful could do for your organization? Whether you’re evaluating platforms, planning a migration, or looking to optimize your current setup, Oomph can help you build a content infrastructure designed for the long term. Let’s talk about your next move.

Why Organizations Move to Contentful Now

Organizations typically migrate to Contentful when legacy systems start holding them back. Common triggers include:

In 2026, Contentful isn’t chosen because it’s new. It’s chosen because it’s resilient.

For organizations new to the platform, getting started doesn’t have to mean a complete rebuild. Oomph’s Contentful Kickstart Package helps teams move from decision to deployment with a structured, low-risk approach—giving you the foundation to scale as your needs evolve.

The Takeaway

Contentful has evolved alongside the modern digital landscape. It’s not just a CMS—it’s a content platform designed for scale, governance, and change.

For organizations planning beyond their next website launch and toward long-term digital maturity, Contentful provides the flexibility and confidence needed to move forward.

Ready to explore what Contentful could do for your organization? Whether you’re evaluating platforms, planning a migration, or looking to optimize your current setup, Oomph can help you build a content infrastructure designed for the long term. Let’s talk about your next move.

Overview

Catch Carbon is powered by Rare, a global conservation organization with 40 years of experience driving behavior change across 60 countries. Their mission depends on mobilizing individuals and communities to take actions that benefit both people and the planet.

To expand the voluntary carbon credit market, Rare needed a digital platform that could explain carbon offsets clearly, build trust with everyday users, and convert awareness into action—all while maintaining the flexibility to test, learn, and scale based on real user behavior.

The Challenge

The voluntary carbon market had a visibility problem. Carbon offsets represent a powerful tool for individual climate action, but public awareness remained low. Most people didn’t understand what carbon offsets were, why they mattered, or how to purchase them confidently.

Rare needed more than a website. They needed a digital experience system that could:

The existing infrastructure couldn’t support this level of agility or growth. Rare needed a modern platform built for continuous improvement, not static delivery.

The Approach

Oomph designed and built a flexible, performance-ready platform in under three months.

Strategy and Platform Design

We began by evaluating Rare’s content needs, user behaviors, and operational constraints. The platform needed to support rapid publishing, consistent design patterns, and easy editorial workflows—without locking the team into rigid templates or slow release cycles.

We recommended Contentful as the content foundation and React for the front-end experience. This headless architecture separated content management from presentation, giving Rare the ability to update messaging, test new pages, and refine user flows without developer dependencies.

Experience Design and System Thinking

We built a modular design system that balanced clarity, trust, and accessibility. Every component—from educational explainers to conversion flows—was designed to reduce friction and build confidence for users new to carbon markets.

The design system ensured consistency across pages while giving editors the flexibility to structure content based on evolving user needs and campaign goals.

Engineering and Integration

We extended Rare’s existing API to support the new platform, working alongside their internal development team to ensure seamless data flow and operational continuity. Front-end development brought the design system to life, while back-end integration connected content, user data, and transaction workflows into a unified experience.

Throughout, we treated the platform as a system, not a site—designed for iteration, not completion.

What This Made Possible

The new platform gave Rare the operational infrastructure to:

  • Test and refine messaging at speed, publishing new content and campaign pages without platform delays
  • Scale outreach efforts efficiently, supported by a design system that maintains quality and consistency across growth
  • Reduce editorial and technical dependencies, empowering the team to manage content, flows, and user experiences independently
  • Build user trust through clarity, with educational content and conversion flows designed to meet users where they are

By decoupling content from code, Rare gained the flexibility to respond to user feedback, market conditions, and organizational priorities in real time—without platform friction or cost escalation.

The Result

Catch Carbon launched on a modern, headless platform designed for continuous improvement. The system supports Rare’s mission to make carbon markets accessible and actionable for everyday users, with the operational flexibility to evolve as the market and audience grow.

The platform positions Catch Carbon to move key engagement and conversion metrics over time—not through one-time delivery, but through ongoing iteration and optimization.

Why This Matters

Most organizations in the climate and nonprofit space face the same trade-off: build something fast and limited, or invest in systems that take too long and cost too much. Catch Carbon proves that speed and sustainability aren’t mutually exclusive.

By treating digital infrastructure as a system to operate, not a project to complete, Rare gained the foundation to test, learn, and scale—on their terms, within their budget.

At Oomph, we believe that moving the metrics that matter starts with building platforms that can adapt, perform, and grow. Catch Carbon is doing exactly that.

It’s nice to have a partnership [with Adapt] where you guys are so honest, straightforward, hardworking, and thoughtful.

— Catch Carbon

For many organizations, privacy regulations like GDPR and CCPA seem like distant legal concerns rather than operational priorities. In practice, however, websites serve as the primary point of data collection—making compliance far more relevant than most teams assume. If your site collects user data in any form, privacy compliance isn’t optional.

Understanding When GDPR and CCPA Apply

GDPR governs the collection of personal data from users in the European Union, while CCPA applies to personal data collected from California residents.

Crucially, these regulations are triggered by user location, not company headquarters. A U.S.-based organization serving a global audience may be subject to both frameworks.

Why Websites Are at the Center of Compliance

Most modern websites collect data through multiple channels:

Each of these collection points creates compliance obligations around consent, transparency, and user control.

Moving Beyond Cookie Banners

Meaningful compliance extends well beyond footer disclaimers. Effective privacy management requires:

Legacy CMS platforms frequently lack the flexibility and governance capabilities needed to meet these requirements.

The Role of Your CMS in Privacy Compliance

Your content management system is instrumental in supporting privacy obligations. A modern, composable CMS enables organizations to:

For regulated and mission-driven organizations, CMS limitations can translate directly into compliance vulnerabilities.

The Cost of Non-Compliance

While regulatory penalties are a concern, the greater risk lies in eroding user trust.

Today’s users expect transparency and control over their personal information. Organizations unable to deliver on these expectations risk damaging their reputation with customers, donors, and partners.

Final Thoughts

GDPR and CCPA represent more than legal obligations—they present fundamental digital experience challenges. Websites built on flexible, compliance-ready platforms are better positioned to adapt as privacy expectations continue to evolve.

In today’s environment, privacy compliance shouldn’t be viewed as a constraint. It’s an essential component of delivering a modern, trustworthy digital experience.

Need help ensuring your website meets modern privacy standards? Our team specializes in building compliance-ready digital platforms that protect your users and your organization. Let’s discuss your requirements.

Overview

nCino, Inc. is a leader in intelligent banking solutions and a pioneer in the financial technology space. As their business continues to grow and their digital strategy evolves, they needed to ensure their content management capabilities could keep pace with their expanding marketing needs.

Our collaboration with nCino focuses on optimizing their use of the Contentful platform to enhance their internal marketing and website capabilities. By leveraging Contentful, we’re helping nCino streamline and improve their content management processes, allowing their teams to focus more on innovation and growth within their core business.

The approach

We’re working alongside nCino to optimize their Contentful platform implementation. The goal is ensuring their digital presence continues to align with their evolving strategy and marketing needs while supporting their ongoing success as pioneers in the financial technology space.

By enhancing their content management processes, we’re empowering nCino’s internal teams to work more efficiently and strategically.

Why this project matters

This work represents an important step in ensuring nCino’s digital presence continues to align with their evolving strategy and marketing needs. The optimization supports their ongoing success as pioneers in the financial technology space by removing operational friction and enabling their teams to focus on what matters most — innovation and growth.

Overview

Aerospike specializes in high-performance NoSQL databases known for their speed, scalability, and reliability in handling large volumes of data in real-time applications. Their database technology is designed to meet the demands of modern data-intensive applications.

The company’s platform offers features such as strong consistency, high availability, and automatic failover to ensure continuous operations even in the event of hardware failures or network issues. Aerospike also provides tools and integrations to support analytics, monitoring, and management of the database environment, empowering developers and operations teams to optimize performance and scalability.

Think of a NoSQL database as a big, organized digital filing cabinet for storing different kinds of information. Traditional databases are like organized spreadsheets where everything is neatly arranged in rows and columns. However, NoSQL databases are designed to handle different types of data—like text, numbers, pictures, and more—and can store huge amounts of it very quickly. They’re a super-fast and flexible digital storage system.

The challenge

Aerospike needed a new platform to provide consistent, clean rebranding, increases in speed and efficiency, an enhanced user and client experience, and streamlined communication with clients.

Despite their renown in the NoSQL database market, their website lacked the clarity needed to capture conversion rates fitting for a brand in the spotlight of their digital industry.

The approach

Headless CMS functions similarly to NoSQL databases, allowing content managers to view and manage content of all forms easily and from one place. Under the guidance of our team, Aerospike decided that a migration to a headless CMS with Contentful was the right option.

This decision, along with brand redesign and consistent messaging, were all instrumental parts of Aerospike’s digital revolution. We were able to work side by side with Aerospike to give them a refresh that tells a story.

The Results

The result is a totally remastered headless CMS website, providing Aerospike the foundation needed for continued success and reputability. The new platform delivers the consistent, clean rebranding they needed along with the speed, efficiency, and enhanced user experience that positions them for growth.

We were able to work side by side with Aerospike to give them a refresh that tells a story and matches the innovative spirit of their cutting-edge database technology.

Throughout the process, I was impressed by the ways Aerospike would experiment with its database. That fits how [Oomph] approaches our projects: open-minded and ready to break the mold.

— Jesse Day, Technical Director