One website, one CMS  🔗 **Source:** [One website, one CMS](https://www.jonoalderson.com/conjecture/one-website-one-cms/) > [!note]+ Document Notes > tags: [content-management, web-architecture, organizational-design] > author: Jono Alderson > source: jonoalderson.com > reference: https://www.jonoalderson.com/conjecture/one-website-one-cms/ > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: One website, one CMS > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ## 📝 Summary - Multiple CMSs on one website fragment organizational knowledge and capabilities over time. - Teams initially gain local autonomy but the organization loses systemic coherence. - Websites transition from building systems to merely publishing pages. - The real cost isn't technical debt but institutional debt as architecture becomes political structure. - Modern websites need coherent underlying systems where truth and relationships are managed canonically. ## 📖 Main Content Jono Alderson argues that running multiple content management systems on a single website is almost always a strategic mistake—not for SEO reasons, but because it fundamentally damages an organization's ability to build coherent digital experiences. ### The Hidden Organizational Cost The pattern is common: Shopify stores add WordPress for SEO, SaaS companies run marketing sites separately from product applications, enterprises bolt WordPress onto locked-down enterprise CMSs. These decisions feel sensible locally—marketing gains autonomy, engineering gets flexibility, teams move faster. But once websites fragment across multiple systems, organizations gradually lose the ability to build experiences where understanding compounds naturally. Instead of defining relationships once and propagating changes systemically, teams begin duplicating meaning across disconnected environments. ### From Systems to Pages The core distinction is between publishing pages versus building systems. Sophisticated digital experiences require that products relate to categories, categories connect to guides, reviews influence recommendations, and editorial context shapes discovery. These relationships should be defined once and cascade through navigation, search, recommendations, and AI interfaces. Fragmented architectures break this coherence. Organizations stop building systems and start building pages. Websites plateau despite having large teams and healthy publishing schedules because every meaningful improvement requires coordination across multiple CMSs, deployment pipelines, and political boundaries. ### Architecture Becomes Politics Multiple CMSs don't just fragment technology—they fragment authority. WordPress becomes "marketing territory," React applications belong to engineering, support centers belong to customer success. Each team gains local autonomy, but the organization loses systemic coherence. Eventually, the architecture becomes embedded in reporting lines, workflows, ownership models, and internal politics. Unwinding fragmentation stops being technical debt and becomes institutional debt. ## 🗒️ Notes - The issue isn't multiple frontends or technical separation—it's whether the organization operates from a coherent underlying system - Fragmented websites often look superficially successful but hit quality ceilings - Teams adapt by proposing safer ideas that don't require cross-system coordination - The strategic asset shifts from individual pages to systems that allow knowledge reuse across surfaces - Modern retrieval systems handle fragmented signals well, but internal organizational capabilities suffer ## 📚 References - [Jono Alderson](https://www.jonoalderson.com/) ## 🗣️ Paraphrase Running multiple content management systems on one website creates a slow-motion organizational disaster. While teams initially benefit from increased autonomy and faster publishing, the website gradually stops functioning as a coherent system. Knowledge becomes trapped in departmental silos, relationships between content must be manually recreated across platforms, and every improvement requires expensive coordination work. The real damage isn't technical—it's that organizations lose the ability to build sophisticated digital experiences where understanding accumulates and propagates naturally. Teams adapt by avoiding ambitious projects that would require cross-system integration. What starts as a practical technical decision eventually reshapes organizational structure and limits strategic imagination. ## 📰 Newsletter **Why Your Multi-CMS Strategy Is Quietly Sabotaging Your Website** That WordPress blog bolted onto your Shopify store? That Webflow marketing site running alongside your React app? Jono Alderson's latest piece explains why these seemingly practical decisions gradually undermine your organization's ability to build coherent digital experiences. The issue isn't SEO confusion—modern systems handle fragmented signals fine. The real cost is internal: once websites fragment across multiple CMSs, teams lose the ability to build systems where knowledge compounds naturally. Instead of defining product relationships once and propagating them through navigation, search, and recommendations, you end up manually recreating meaning across disconnected platforms. Worth reading for anyone managing complex WordPress sites or considering headless architectures. The piece offers a fresh lens on why some websites plateau despite healthy publishing schedules and competent teams. [Read the full analysis →](https://www.jonoalderson.com/conjecture/one-website-one-cms/) ## ✅ Action Items #### WordPress - **Core:** Evaluate multi-CMS warning patterns in site health checks - **Documentation:** Create guidance on unified content architecture best practices - **Community:** Workshop sessions on avoiding fragmentation in headless implementations #### OSPO - **Strategic Alignment:** Assess internal WordPress.org properties for CMS fragmentation risks - **Developer Support:** Create decision frameworks for unified vs. fragmented architecture choices #### Community - **Maintainers:** Document headless WordPress patterns that preserve content coherence - **Contributors:** Identify integration points that prevent organizational silos ## 🧪 Hypotheses 1. Organizations with unified CMS architectures show measurably higher content reuse rates across digital properties 2. Multi-CMS websites plateau in user engagement metrics after initial productivity gains 3. Teams working within fragmented architectures propose fewer cross-functional improvements over time 4. The institutional debt of unwinding multi-CMS architectures grows exponentially with time 5. Organizations can maintain coherence with multiple frontends if they preserve unified content modeling ## 📊 Methodology - **Longitudinal study**: Track content reuse patterns and cross-functional project proposals in unified vs. fragmented organizations over 2-3 years - **Engagement analysis**: Compare user behavior metrics before and after CMS fragmentation in matched cohorts - **Organizational surveys**: Measure perceived coordination costs and strategic ambition across different architecture patterns - **Cost modeling**: Quantify integration overhead and unwinding expenses for multi-CMS implementations ## ❓ Questions - How can organizations measure the hidden costs of architectural fragmentation before they become embedded in politics? - What technical patterns allow multiple frontends while preserving content coherence? - How do AI-mediated interfaces change the stakes for unified content modeling? - What governance structures prevent multi-CMS architectures from becoming political structures? ## 🔮 Future Research - Develop frameworks for measuring "content coherence debt" in digital organizations - Study successful patterns for maintaining unified content models across distributed rendering layers - Investigate how AI interfaces amplify the costs of fragmented content architectures - Research organizational design patterns that preserve systemic thinking in technical architectures ## 💡 Implications **Practice**: Organizations should audit existing multi-CMS implementations for early signs of knowledge fragmentation and coordination overhead. **Policy**: Enterprise technology decisions should include organizational coherence assessments alongside technical and security reviews. **Education**: Developer and marketing education should emphasize the relationship between technical architecture and organizational capabilities. **Funding**: Investment in unified content platforms may yield higher long-term returns than funding multiple specialized systems. ## 🧠 Learning Styles Assessment Reading level estimate: Flesch-Kincaid Grade 12.2 - sophisticated business/technical audience #### 👀 Visual learners - **Present**: Clear section structure, conceptual progression from technical to organizational - **Improve**: Add diagram showing fragmentation progression, before/after organizational charts, content relationship maps #### 🔊 Aural learners - **Present**: Strong narrative flow, clear argumentation structure - **Improve**: Audio version would benefit from emphasized transitions between technical and organizational concepts #### 🗣️ Verbal learners - **Present**: Rich analogies (websites as systems vs. pages), clear definitions of fragmentation - **Improve**: Add glossary for "systemic coherence," "institutional debt," more concrete examples #### 🧩 Kinesthetic learners - **Present**: Concrete examples (Shopify + WordPress, React + Webflow) - **Improve**: Add decision trees, assessment checklists, step-by-step fragmentation audit process #### 🧠 Logical learners - **Present**: Clear cause-effect relationships, logical progression from technical to organizational consequences - **Improve**: Add decision framework matrix, quantified cost models, ROI comparisons #### 🧑‍🤝‍🧑 Social learners - **Present**: Focus on organizational dynamics and team behavior - **Improve**: Case studies with team interviews, workshop discussion guides, collaborative assessment tools #### 🧘‍♀️ Solitary learners - **Present**: Reflective questions embedded in argument, self-assessment implications - **Improve**: Add self-audit worksheets, personal reflection prompts on current architecture decisions #### 🌿 Naturalistic learners - **Present**: Systems thinking approach, organic growth metaphors - **Improve**: Ecosystem analogies, sustainability framing for long-term organizational health ## 📊 Accessibility Assessment #### Screen reader semantics - **Present**: Good heading hierarchy, logical document structure - **Improve**: Add ARIA landmarks for main argument sections, alt text for conceptual diagrams if added #### Keyboard navigation - **Present**: Standard web navigation, logical focus order - **Improve**: Add skip links for long-form content, keyboard shortcuts for section navigation #### Contrast and readability - **Present**: Clean typography, adequate contrast in original design - **Improve**: Ensure code examples meet contrast requirements, test with high contrast mode #### Text resizing and reflow - **Present**: Responsive design handles scaling - **Improve**: Test complex nested concepts at 200% zoom, ensure no horizontal scrolling #### Media and captions - **Present**: Text-based content, no embedded media requiring captions - **Improve**: If audio version added, provide full transcript with timestamps #### Forms and interactions - **Present**: Minimal interactive elements - **Improve**: Ensure newsletter signup forms meet accessibility standards ## 🌍 DEIB Assessment #### Cultural breadth - **Present**: Business concepts applicable across organizational cultures - **Improve**: Add examples from diverse company sizes and global contexts, non-Western organizational models #### Inclusive language - **Present**: Professional tone, avoids technical jargon exclusion - **Improve**: Define "CMS," "technical debt," ensure metaphors translate across cultures #### Neurodiversity support - **Present**: Clear structure, logical progression - **Improve**: Add visual breaks, summary bullets, alternative ways to process dense conceptual content #### Representation - **Present**: Neutral organizational examples - **Improve**: Include diverse company examples, various team structures, different technical maturity levels #### Psychological safety - **Present**: Non-judgmental framing of common architectural decisions - **Improve**: Add reassurance that fragmentation is common and fixable, avoid blame-focused language ## ✅ Logical Validity #### Strong reasoning - **Causal reasoning** (paragraph 4): "Once a website is split across multiple CMSs, the organisation gradually loses the ability to build anything coherent" - strong because it identifies specific mechanism (coordination costs) and acknowledges gradual timeline - **Systems thinking** (paragraph 12): Explanation of how content relationships should propagate demonstrates understanding of complex interdependencies - **Analogical reasoning** (throughout): Comparison between pages vs. systems effectively clarifies abstract concept through concrete distinction #### Fallacies - **False dichotomy** (implied): Presents unified CMS vs. multiple CMSs as binary choice, but acknowledges in clarification section that multiple frontends can work with unified backend - **Hasty generalization** (paragraph 2): Claims multi-CMS is "almost always" a mistake based on pattern recognition rather than systematic study #### Tone of voice Professional and analytical with prescriptive undertones. Uses confident declarative statements ("This pattern is everywhere," "The real damage happens internally") combined with nuanced acknowledgment of complexity. ## 🛡️ DARVO Analysis No DARVO patterns detected. The article presents a critical analysis of common architectural decisions but maintains a systems-focused rather than personal blame approach. The author acknowledges that fragmented architectures arise through "sensible local decisions" and avoids attacking individuals or teams for these choices. ## 🎯 Conclusion Alderson makes a compelling case that multi-CMS architectures create hidden organizational costs that far exceed their technical benefits. The core insight—that fragmented systems gradually transform from technical decisions into political structures—offers a valuable framework for evaluating content strategy decisions. For readers managing complex WordPress installations or considering headless approaches, the key takeaway is to prioritize content model coherence over short-term autonomy gains. The article serves as both warning and guide for maintaining systemic thinking in an era of distributed web architectures. ## 🔄 Refactor Appendix — One website, one CMS ### 📚 Literature Atoms #### Multi-CMS architectures fragment organizational knowledge management capabilities over time > [!quote] > Once a website is split across multiple content management systems, the organisation gradually loses the ability to build anything coherent on top of it. **Context & use**: - Core thesis statement establishing the hidden organizational cost - Applies to content strategy and enterprise architecture decisions **Tags**: #xref #content-management #organizational-design #### Content relationships should be defined canonically and propagated systemically > [!quote] > Products relate to categories. Categories relate to guides. Locations inherit meaning from regions. Reviews influence recommendations. **Context & use**: - Defines the difference between systems thinking and page-based publishing - Critical for information architecture and content modeling **Tags**: #xref #information-architecture #### Architecture decisions eventually reshape organizational structure and imagination > [!quote] > Once systems split apart, teams begin organising themselves around the boundaries imposed by the architecture itself. **Context & use**: - Explains Conway's Law in reverse - how technical decisions influence organizational behavior - Key insight for technology leadership and change management **Tags**: #xref #organizational-design #conways-law ### 🧠 Permanent Candidates #### Technical architecture influences organizational capabilities and strategic imagination **Claim**: Technical system boundaries eventually become political boundaries that limit organizational coherence and strategic ambition. **Evidence pointer**: [[#Architecture decisions eventually reshape organizational structure and imagination]] **Scope & conditions**: Applies when systems fragment authority across teams; may not hold with strong governance frameworks **Links**: - [[Conway's Law]] — because extends the concept in reverse direction - [[Technical debt]] — because contrasts with institutional debt concept - [[Content strategy]] — because applies-in enterprise content management ### ✏️ Fleeting Queue - Does WordPress.org itself exhibit multi-CMS fragmentation across its properties? — audit opportunity - How do headless WordPress implementations avoid the coherence problems described? — documentation gap ### → Things 3 - [ ] Audit current WordPress project properties for CMS fragmentation patterns — content-strategy #things <!-- deep-read:sections end --> ## Highlights - Once a website is split across multiple content management systems, the organisation gradually loses the ability to build anything coherent on top of it. - Note: 📚 Multi-CMS architectures fragment organizational knowledge management capabilities over time · - Core thesis statement establishing the hidden organizational cost - Applies to content strategy and enterprise architecture decisions · #atom/literature/h1 - Products relate to categories. Categories relate to guides. Locations inherit meaning from regions. Reviews influence recommendations. - Note: 📚 Content relationships should be defined canonically and propagated systemically · - Defines the difference between systems thinking and page-based publishing - Critical for information architecture and content modeling · #atom/literature/h2 - Once systems split apart, teams begin organising themselves around the boundaries imposed by the architecture itself. - Note: 📚 Architecture decisions eventually reshape organizational structure and imagination · - Explains Conway's Law in reverse - how technical decisions influence organizational behavior - Key insight for technology leadership and change management · #atom/literature/h3 - Technical architecture influences organizational capabilities and strategic imagination - Note: [[Conway's Law]] — because extends the concept in reverse direction · - [[Conway's Law]] — because extends the concept in reverse direction · #atom/zettel/z1 - Claims multi-CMS is "almost always" a mistake based on pattern recognition rather than systematic study - Note: 🔍 Fallacy: Hasty Generalization #fallacy/hasty-generalization ## New Highlights added 2026-05-26 at 8:49 AM - Teams stop proposing ambitious ideas because experience has taught them that every improvement will trigger weeks of integration work, deployment risk, stakeholder negotiation, or edge-case management. Editorial teams work around the architecture instead of improving it. SEO teams optimise the surfaces they control because they can’t meaningfully influence the product itself. Engineers become defensive about change because complexity has made the system fragile. ([View Highlight](https://read.readwise.io/read/01ksj4xwpsyspy1bkf1ta92qkd)) - Marketing owns the blog because it cannot safely influence the product. Product teams ignore editorial because the publishing stack lives elsewhere. SEO works on “resources” and aggregation pages because core commercial surfaces are politically or technically inaccessible. Support content drifts away from the customer experience because it exists inside another platform entirely. Nobody owns the whole system because the whole system no longer meaningfully exists. ([View Highlight](https://read.readwise.io/read/01ksj4yj654njhgjcajke4hcpw))