The Product We Should Not Have Killed  ## Metadata - Author: [[Dries Buytaert]] - Full Title: The Product We Should Not Have Killed - Category: #articles - Document Note: --- tags: [Drupal, SaaS, Open Source] author: Dries Buytaert source: dri.es reference: [https://dri.es/the-product-we-should-not-have-killed] date created: 2025-11-17 00:00 --- # 🏷️ Title: The product we should not have killed ## 🧭 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) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: Dries announces Acquia Source, “a new Drupal SaaS,” revisiting the shuttered Drupal Gardens concept with modern capabilities. - Why it matters: Aims to unify simple and complex site needs on one Drupal-based platform, reducing multi-CMS sprawl and operational overhead. - Key stakeholders: Marketing teams, IT/dev teams, enterprise web owners, Drupal community, Acquia customers. - Risks and tradeoffs: Product focus across SaaS and enterprise stacks; migration/export expectations; balancing “opinionated SaaS” with extensibility. - Bottom line: Acquia Source complements Acquia Cloud/Site Factory to “help teams launch sites fast, without updates or maintenance,” while keeping an open, exportable path. ## 📖 Main Content - Core arguments: - Shutting Drupal Gardens (2009–~2015) was “one of the biggest business mistakes” despite Site Factory’s success. - Enterprises need both quick-launch simple sites and deeply integrated complex ones; running multiple CMSs increases cost and friction. - Acquia now has resources to deliver a modern SaaS that preserves openness and exportability. - Context/definitions: - Drupal Gardens: no-code Drupal SaaS for fast site launches; reached 100k+ sites. - Acquia Cloud Site Factory: enterprise fleet management with governance and integrations. - Acquia Source: opinionated SaaS, export code/config/content; built “in the open,” e.g., with Drupal Canvas. - Uncertainties: - Pricing/GA timeline (currently limited availability). - Depth of customization vs. SaaS guardrails. - Migration paths from non-Drupal SaaS back to Drupal. ### 🗒️ Notes - “We’re building a new Drupal SaaS called Acquia Source.” - Regret: “shutting down Drupal Gardens feels like one of the biggest business mistakes we made.” - Tradeoff then: limited resources forced a focus on enterprise; Site Factory thrived but lost the no-dev user. - Problem: multi-CMS setups add training, UX inconsistency, siloed content, multiple stacks. - Bezos frame: things true 10 years ago, today, and 10 years from now—organizations need varied site complexity; multi-stack inefficiency persists. - Positioning: Source complements (not replaces) Acquia Cloud/Site Factory; shared Drupal foundation enables shared skills/code. - Openness: exportable sites; components developed “in the open” (Drupal Canvas). ## 📚 References - Acquia Source announcement (article): https://dri.es/the-product-we-should-not-have-killed - Acquia Cloud Site Factory: https://www.acquia.com/products/drupal-cloud/site-factory - Drupal Canvas (open source): https://www.drupal.org/project/canvas - Drupal (project): https://www.drupal.org/ ## 🗣️ Paraphrase - Paragraph A: Acquia regrets ending Drupal Gardens and is launching Acquia Source to fulfill the original SaaS vision with modern Drupal and open principles. - Paragraph B: Enterprises struggle with multi-CMS costs; Source aims to cover simple-to-complex sites on one platform while coexisting with Cloud and Site Factory. ## 📰 Newsletter Acquia is reviving the spirit of Drupal Gardens with Acquia Source—a modern, opinionated Drupal SaaS that launches sites fast without maintenance headaches, while keeping exportability and community roots via projects like Drupal Canvas. For teams juggling WordPress or assorted SaaS for microsites and Drupal for flagships, this could streamline ops, standardize tooling, and consolidate skills. Also worth a look: governance at scale with Site Factory, plus paths to share code and components across stacks. Resources: - Acquia Source overview by Dries - Site Factory for fleets - Drupal Canvas for open, visual building ## ✅ Action Items #### DevRel - Run live demos comparing Source vs. Site Factory use cases; publish quickstarts and starter templates. - Build “export and extend” tutorials with CI/CD examples. - Collect developer feedback via office hours; instrument docs for search gaps. #### OSPO - Define contribution pathways for Canvas; publish governance and CLA notes. - Establish license/compliance checks for Source-exported code. - Document security response and signing/attestation for SaaS artifacts. #### Community - Host roadmap clinics on SaaS guardrails vs. extensibility. - First-issue rotations on Canvas; pairing sessions for theme/module authors. - Publish transparent funding reports for community workstreams. #### WordPress - Comparative guides for marketers migrating micro/campaign sites. - Performance budget templates; plugin/theme provenance checks. - Accessibility audits and documentation for parity comparisons. #### The WPCC - Microgrants for migration playbooks and governance templates. - Release-team sprints to test multi-site fleet workflows. ### FAIR - Ship export signatures and provenance metadata. - Publish sunset/portability covenants and anti-lock-in guarantees. - Provide reusable governance artifacts (charters, scorecards). ## 🧪 Hypotheses - H1: Acquia Source reduces time-to-first-publish for simple sites by ≥50% vs. self-hosted Drupal. - H2: Organizations using Source plus Site Factory cut multi-CMS usage by ≥30% within a year. - H3: Exportability increases developer adoption and lowers churn by ≥15%. - H4: Shared Drupal foundation reduces training hours per editor by ≥25%. ## 📊 Methodology - Quasi-experimental rollout with matched cohorts (multi-CMS vs. Source+Drupal). - Metrics: TTFP, editor training hours, CMS count, churn, governance incident rate. - Surveys and time-motion studies; telemetry on site creation and export flows. ## ❓ Questions - How opinionated is Source’s plugin/theme model? - What are migration paths from WordPress/other SaaS? - How are governance and multi-brand design systems supported? - What SLAs and data residency options exist? ## 🔮 Future Research - Cost modeling of single- vs multi-CMS over 3 years. - Editor UX studies across Source, WordPress, and headless builders. - Best practices for export-to-custom-cloud workflows. ## 💡 Implications - Practice: Faster campaign launches with consistent design and governance. - Policy: Stronger portability and anti-lock-in commitments in contracts. - Security: Centralized patching; clearer SBOM/export attestations. - Education: Unified training across marketing and IT. ## 🧠 Learning Styles Assessment - Reading level: ~Grade 9–10 (Flesch-Kincaid estimate). #### 👀 Visual learners - Present: Concept framing. - Improve: Architecture diagrams and export flow maps. #### 🔊 Aural learners - Improve: 3–5 minute audio summary and Q&A. #### 🗣️ Verbal learners - Present: Clear contrasts (Gardens vs. Source). - Improve: Glossary for SaaS terms. #### 🧩 Kinesthetic learners - Improve: Hands-on quickstarts and sandboxes. #### 🧠 Logical learners - Present: Problem-solution structure. - Improve: Decision trees for product fit. #### 🧑‍🤝‍🧑 Social learners - Improve: Cohort onboarding and moderated forums. #### 🧘‍♀️ Solitary learners - Improve: Self-checklists and reflection prompts. #### 🌿 Naturalistic learners - Improve: Lifecycle and sustainability analogies. ### 📊 Accessibility Assessment #### Screen reader semantics - Improve: Confirm headings/landmarks and descriptive alt text. #### Keyboard navigation - Improve: Verify v - Summary: We're building a new Drupal SaaS called Acquia Source. - URL: https://dri.es/the-product-we-should-not-have-killed ## Document Notes --- tags: [Drupal, SaaS, Open Source] author: Dries Buytaert source: dri.es reference: [https://dri.es/the-product-we-should-not-have-killed] date created: 2025-11-17 00:00 --- # 🏷️ Title: The product we should not have killed ## 🧭 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) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: Dries announces Acquia Source, “a new Drupal SaaS,” revisiting the shuttered Drupal Gardens concept with modern capabilities. - Why it matters: Aims to unify simple and complex site needs on one Drupal-based platform, reducing multi-CMS sprawl and operational overhead. - Key stakeholders: Marketing teams, IT/dev teams, enterprise web owners, Drupal community, Acquia customers. - Risks and tradeoffs: Product focus across SaaS and enterprise stacks; migration/export expectations; balancing “opinionated SaaS” with extensibility. - Bottom line: Acquia Source complements Acquia Cloud/Site Factory to “help teams launch sites fast, without updates or maintenance,” while keeping an open, exportable path. ## 📖 Main Content - Core arguments: - Shutting Drupal Gardens (2009–~2015) was “one of the biggest business mistakes” despite Site Factory’s success. - Enterprises need both quick-launch simple sites and deeply integrated complex ones; running multiple CMSs increases cost and friction. - Acquia now has resources to deliver a modern SaaS that preserves openness and exportability. - Context/definitions: - Drupal Gardens: no-code Drupal SaaS for fast site launches; reached 100k+ sites. - Acquia Cloud Site Factory: enterprise fleet management with governance and integrations. - Acquia Source: opinionated SaaS, export code/config/content; built “in the open,” e.g., with Drupal Canvas. - Uncertainties: - Pricing/GA timeline (currently limited availability). - Depth of customization vs. SaaS guardrails. - Migration paths from non-Drupal SaaS back to Drupal. ### 🗒️ Notes - “We’re building a new Drupal SaaS called Acquia Source.” - Regret: “shutting down Drupal Gardens feels like one of the biggest business mistakes we made.” - Tradeoff then: limited resources forced a focus on enterprise; Site Factory thrived but lost the no-dev user. - Problem: multi-CMS setups add training, UX inconsistency, siloed content, multiple stacks. - Bezos frame: things true 10 years ago, today, and 10 years from now—organizations need varied site complexity; multi-stack inefficiency persists. - Positioning: Source complements (not replaces) Acquia Cloud/Site Factory; shared Drupal foundation enables shared skills/code. - Openness: exportable sites; components developed “in the open” (Drupal Canvas). ## 📚 References - Acquia Source announcement (article): https://dri.es/the-product-we-should-not-have-killed - Acquia Cloud Site Factory: https://www.acquia.com/products/drupal-cloud/site-factory - Drupal Canvas (open source): https://www.drupal.org/project/canvas - Drupal (project): https://www.drupal.org/ ## 🗣️ Paraphrase - Paragraph A: Acquia regrets ending Drupal Gardens and is launching Acquia Source to fulfill the original SaaS vision with modern Drupal and open principles. - Paragraph B: Enterprises struggle with multi-CMS costs; Source aims to cover simple-to-complex sites on one platform while coexisting with Cloud and Site Factory. ## 📰 Newsletter Acquia is reviving the spirit of Drupal Gardens with Acquia Source—a modern, opinionated Drupal SaaS that launches sites fast without maintenance headaches, while keeping exportability and community roots via projects like Drupal Canvas. For teams juggling WordPress or assorted SaaS for microsites and Drupal for flagships, this could streamline ops, standardize tooling, and consolidate skills. Also worth a look: governance at scale with Site Factory, plus paths to share code and components across stacks. Resources: - Acquia Source overview by Dries - Site Factory for fleets - Drupal Canvas for open, visual building ## ✅ Action Items #### DevRel - Run live demos comparing Source vs. Site Factory use cases; publish quickstarts and starter templates. - Build “export and extend” tutorials with CI/CD examples. - Collect developer feedback via office hours; instrument docs for search gaps. #### OSPO - Define contribution pathways for Canvas; publish governance and CLA notes. - Establish license/compliance checks for Source-exported code. - Document security response and signing/attestation for SaaS artifacts. #### Community - Host roadmap clinics on SaaS guardrails vs. extensibility. - First-issue rotations on Canvas; pairing sessions for theme/module authors. - Publish transparent funding reports for community workstreams. #### WordPress - Comparative guides for marketers migrating micro/campaign sites. - Performance budget templates; plugin/theme provenance checks. - Accessibility audits and documentation for parity comparisons. #### The WPCC - Microgrants for migration playbooks and governance templates. - Release-team sprints to test multi-site fleet workflows. ### FAIR - Ship export signatures and provenance metadata. - Publish sunset/portability covenants and anti-lock-in guarantees. - Provide reusable governance artifacts (charters, scorecards). ## 🧪 Hypotheses - H1: Acquia Source reduces time-to-first-publish for simple sites by ≥50% vs. self-hosted Drupal. - H2: Organizations using Source plus Site Factory cut multi-CMS usage by ≥30% within a year. - H3: Exportability increases developer adoption and lowers churn by ≥15%. - H4: Shared Drupal foundation reduces training hours per editor by ≥25%. ## 📊 Methodology - Quasi-experimental rollout with matched cohorts (multi-CMS vs. Source+Drupal). - Metrics: TTFP, editor training hours, CMS count, churn, governance incident rate. - Surveys and time-motion studies; telemetry on site creation and export flows. ## ❓ Questions - How opinionated is Source’s plugin/theme model? - What are migration paths from WordPress/other SaaS? - How are governance and multi-brand design systems supported? - What SLAs and data residency options exist? ## 🔮 Future Research - Cost modeling of single- vs multi-CMS over 3 years. - Editor UX studies across Source, WordPress, and headless builders. - Best practices for export-to-custom-cloud workflows. ## 💡 Implications - Practice: Faster campaign launches with consistent design and governance. - Policy: Stronger portability and anti-lock-in commitments in contracts. - Security: Centralized patching; clearer SBOM/export attestations. - Education: Unified training across marketing and IT. ## 🧠 Learning Styles Assessment - Reading level: ~Grade 9–10 (Flesch-Kincaid estimate). #### 👀 Visual learners - Present: Concept framing. - Improve: Architecture diagrams and export flow maps. #### 🔊 Aural learners - Improve: 3–5 minute audio summary and Q&A. #### 🗣️ Verbal learners - Present: Clear contrasts (Gardens vs. Source). - Improve: Glossary for SaaS terms. #### 🧩 Kinesthetic learners - Improve: Hands-on quickstarts and sandboxes. #### 🧠 Logical learners - Present: Problem-solution structure. - Improve: Decision trees for product fit. #### 🧑‍🤝‍🧑 Social learners - Improve: Cohort onboarding and moderated forums. #### 🧘‍♀️ Solitary learners - Improve: Self-checklists and reflection prompts. #### 🌿 Naturalistic learners - Improve: Lifecycle and sustainability analogies. ### 📊 Accessibility Assessment #### Screen reader semantics - Improve: Confirm headings/landmarks and descriptive alt text. #### Keyboard navigation - Improve: Verify v > [!note]+ Document Notes > tags: [Drupal, SaaS, Open Source] > author: Dries Buytaert > source: dri.es > reference: [https://dri.es/the-product-we-should-not-have-killed] > date created: 2025-11-17 00:00 > > # 🏷️ Title: The product we should not have killed > <!-- 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) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: Dries announces Acquia Source, “a new Drupal SaaS,” revisiting the shuttered Drupal Gardens concept with modern capabilities. - Why it matters: Aims to unify simple and complex site needs on one Drupal-based platform, reducing multi-CMS sprawl and operational overhead. - Key stakeholders: Marketing teams, IT/dev teams, enterprise web owners, Drupal community, Acquia customers. - Risks and tradeoffs: Product focus across SaaS and enterprise stacks; migration/export expectations; balancing “opinionated SaaS” with extensibility. - Bottom line: Acquia Source complements Acquia Cloud/Site Factory to “help teams launch sites fast, without updates or maintenance,” while keeping an open, exportable path. ## 📖 Main Content - Core arguments: - Shutting Drupal Gardens (2009–~2015) was “one of the biggest business mistakes” despite Site Factory’s success. - Enterprises need both quick-launch simple sites and deeply integrated complex ones; running multiple CMSs increases cost and friction. - Acquia now has resources to deliver a modern SaaS that preserves openness and exportability. - Context/definitions: - Drupal Gardens: no-code Drupal SaaS for fast site launches; reached 100k+ sites. - Acquia Cloud Site Factory: enterprise fleet management with governance and integrations. - Acquia Source: opinionated SaaS, export code/config/content; built “in the open,” e.g., with Drupal Canvas. - Uncertainties: - Pricing/GA timeline (currently limited availability). - Depth of customization vs. SaaS guardrails. - Migration paths from non-Drupal SaaS back to Drupal. ### 🗒️ Notes - “We’re building a new Drupal SaaS called Acquia Source.” - Regret: “shutting down Drupal Gardens feels like one of the biggest business mistakes we made.” - Tradeoff then: limited resources forced a focus on enterprise; Site Factory thrived but lost the no-dev user. - Problem: multi-CMS setups add training, UX inconsistency, siloed content, multiple stacks. - Bezos frame: things true 10 years ago, today, and 10 years from now—organizations need varied site complexity; multi-stack inefficiency persists. - Positioning: Source complements (not replaces) Acquia Cloud/Site Factory; shared Drupal foundation enables shared skills/code. - Openness: exportable sites; components developed “in the open” (Drupal Canvas). ## 📚 References - Acquia Source announcement (article): https://dri.es/the-product-we-should-not-have-killed - Acquia Cloud Site Factory: https://www.acquia.com/products/drupal-cloud/site-factory - Drupal Canvas (open source): https://www.drupal.org/project/canvas - Drupal (project): https://www.drupal.org/ ## 🗣️ Paraphrase - Paragraph A: Acquia regrets ending Drupal Gardens and is launching Acquia Source to fulfill the original SaaS vision with modern Drupal and open principles. - Paragraph B: Enterprises struggle with multi-CMS costs; Source aims to cover simple-to-complex sites on one platform while coexisting with Cloud and Site Factory. ## 📰 Newsletter Acquia is reviving the spirit of Drupal Gardens with Acquia Source—a modern, opinionated Drupal SaaS that launches sites fast without maintenance headaches, while keeping exportability and community roots via projects like Drupal Canvas. For teams juggling WordPress or assorted SaaS for microsites and Drupal for flagships, this could streamline ops, standardize tooling, and consolidate skills. Also worth a look: governance at scale with Site Factory, plus paths to share code and components across stacks. Resources: - Acquia Source overview by Dries - Site Factory for fleets - Drupal Canvas for open, visual building ## ✅ Action Items #### DevRel - Run live demos comparing Source vs. Site Factory use cases; publish quickstarts and starter templates. - Build “export and extend” tutorials with CI/CD examples. - Collect developer feedback via office hours; instrument docs for search gaps. #### OSPO - Define contribution pathways for Canvas; publish governance and CLA notes. - Establish license/compliance checks for Source-exported code. - Document security response and signing/attestation for SaaS artifacts. #### Community - Host roadmap clinics on SaaS guardrails vs. extensibility. - First-issue rotations on Canvas; pairing sessions for theme/module authors. - Publish transparent funding reports for community workstreams. #### WordPress - Comparative guides for marketers migrating micro/campaign sites. - Performance budget templates; plugin/theme provenance checks. - Accessibility audits and documentation for parity comparisons. #### The WPOCC - Microgrants for migration playbooks and governance templates. - Release-team sprints to test multi-site fleet workflows. ### FAIR - Ship export signatures and provenance metadata. - Publish sunset/portability covenants and anti-lock-in guarantees. - Provide reusable governance artifacts (charters, scorecards). ## 🧪 Hypotheses - H1: Acquia Source reduces time-to-first-publish for simple sites by ≥50% vs. self-hosted Drupal. - H2: Organizations using Source plus Site Factory cut multi-CMS usage by ≥30% within a year. - H3: Exportability increases developer adoption and lowers churn by ≥15%. - H4: Shared Drupal foundation reduces training hours per editor by ≥25%. ## 📊 Methodology - Quasi-experimental rollout with matched cohorts (multi-CMS vs. Source+Drupal). - Metrics: TTFP, editor training hours, CMS count, churn, governance incident rate. - Surveys and time-motion studies; telemetry on site creation and export flows. ## ❓ Questions - How opinionated is Source’s plugin/theme model? - What are migration paths from WordPress/other SaaS? - How are governance and multi-brand design systems supported? - What SLAs and data residency options exist? ## 🔮 Future Research - Cost modeling of single- vs multi-CMS over 3 years. - Editor UX studies across Source, WordPress, and headless builders. - Best practices for export-to-custom-cloud workflows. ## 💡 Implications - Practice: Faster campaign launches with consistent design and governance. - Policy: Stronger portability and anti-lock-in commitments in contracts. - Security: Centralized patching; clearer SBOM/export attestations. - Education: Unified training across marketing and IT. ## 🧠 Learning Styles Assessment - Reading level: ~Grade 9–10 (Flesch-Kincaid estimate). #### 👀 Visual learners - Present: Concept framing. - Improve: Architecture diagrams and export flow maps. #### 🔊 Aural learners - Improve: 3–5 minute audio summary and Q&A. #### 🗣️ Verbal learners - Present: Clear contrasts (Gardens vs. Source). - Improve: Glossary for SaaS terms. #### 🧩 Kinesthetic learners - Improve: Hands-on quickstarts and sandboxes. #### 🧠 Logical learners - Present: Problem-solution structure. - Improve: Decision trees for product fit. #### 🧑‍🤝‍🧑 Social learners - Improve: Cohort onboarding and moderated forums. #### 🧘‍♀️ Solitary learners - Improve: Self-checklists and reflection prompts. #### 🌿 Naturalistic learners - Improve: Lifecycle and sustainability analogies. ### 📊 Accessibility Assessment #### Screen reader semantics - Improve: Confirm headings/landmarks and descriptive alt text. #### Keyboard navigation - Improve: Verify visible focus/skip links across product sites. #### Contrast and readability - Improve: Check 4.5:1 across themes. #### Text resizing and reflow - Improve: Reflow at 200% and reduced motion support. #### Media and captions - Improve: Provide captions and transcripts for launch media. #### Forms and interactions - Improve: Inline validation and accessible toasts. #### Standards reference - Map to WCAG 2.2 AA (labels, focus, contrast, reflow, motion). ### 🌍 DEIB Assessment #### Cultural breadth - Improve: Global examples and multilingual materials. #### Inclusive language - Present: Plain tone. - Improve: Expand glossaries and avoid idioms. #### Neurodiversity support - Present: Consistent structure. - Improve: More chunking and icon+text labels. #### Representation - Improve: Inclusive imagery and balanced quoting. #### Psychological safety - Improve: Community guidelines and escalation paths. ### ✅ Logical Validity #### Strong reasoning - Inductive: Multi-CMS costs inferred from repeated customer feedback—credible, aligns with industry patterns. - Causal: Resource constraints led to enterprise focus—plausible, historically grounded. #### Fallacies - Potential survivorship bias: Success of Site Factory as “right choice” by metrics; could add counter-metrics (missed TAM) to balance. #### Tone of voice - Reflective and candid: “biggest business mistakes we made.” ### 🛡️ DARVO Analysis - Deny: None—admits regret. - Attack: None. - Reverse victim/offender: None; frames as learning and course-correction. ## 🎯 Conclusion - Bottom line: Acquia Source revives Drupal’s SaaS promise to cover simple-to-complex sites on one open, exportable platform, complementing existing Acquia products. - Next steps: Monitor limited availability, review pricing/SLAs, pilot with low-risk sites, validate export and governance workflows, and plan training for editors and developers. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] One platform spans simple to complex > [!quote] [The product we should not have killed](https://dri.es/the-product-we-should-not-have-killed) by [[Dries Buytaert]] via [[dri.es]]. Published 2025-11-17. Accessed 2025-11-17. > “one platform that can support everything from simple sites to the most complex ones.” Two lines: positioning thesis; use for product fit decisions. [view highlight](https://dri.es/the-product-we-should-not-have-killed#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] Multi-CMS stacks increase operational cost > [!quote] [The product we should not have killed](https://dri.es/the-product-we-should-not-have-killed) > “a multi-CMS environment comes with a real cost.” Two lines: risk framing; use in consolidation business case. [view highlight](https://dri.es/the-product-we-should-not-have-killed#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] Drupal SaaS reduces time-to-publish - Scope: simple sites; measure TTFP vs. self-hosted. - Pointer: article thesis. - Links: [[Drupal]] [[SaaS Operational Efficiency]] #### [Z2] Exportability increases developer trust - Scope: SaaS with code/config/content export. - Pointer: openness claim. - Links: [[Open Source Governance]] [[Portability]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: Select one line → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Draft Source vs. Site Factory decision tree — https://dri.es/the-product-we-should-not-have-killed #fleeting #inbox - [F2] Validate export pipeline from Source to Cloud CI — https://dri.es/the-product-we-should-not-have-killed #fleeting #inbox - [F3] Build editor training for single-CMS consolidation — https://dri.es/the-product-we-should-not-have-killed #fleeting #inbox --- <!-- deep-read:sections end --> ## Highlights - Ten years ago, [Acquia](https://www.acquia.com/) shut down Drupal Gardens, a decision that I still regret. ([View Highlight](https://read.readwise.io/read/01ka9xbz1wxcwgep62erxj9b0c)) - Looking back, shutting down Drupal Gardens feels like one of the biggest business mistakes we made. ([View Highlight](https://read.readwise.io/read/01ka9xc5hv66jsja905251jb1r)) - Acquia Source is more powerful and more customizable than Drupal Gardens ever was. ([View Highlight](https://read.readwise.io/read/01kaa0r6r507hdeyf7atvpm2an)) - we are building Acquia Source with open principles in mind. It is easy to export your site, including code, configuration, and content. ([View Highlight](https://read.readwise.io/read/01kaa0rhch933vpj68bkcr03y1)) - Acquia Source does *not* replace Acquia Cloud or Acquia Cloud Site Factory. ([View Highlight](https://read.readwise.io/read/01kaa0s563vsmmk11zkh8txt61))