AI-native CMS vs vibe coding
summary
Ten years of building developer portals in Drupal lead to a clear claim: AI changes the process, not just the output — adding metadata upstream in code (example: Apache Superset using Docusaurus) creates deterministic, higher‑quality docs rather than dumping content into RAG. Research across bank portals shows Drupal sites score better for AI visibility than many JavaScript stacks. The recommended pattern is structured ETL plus contextual AI (E3TL), enabling docs as code and new agentic experience platform services (80/20 centauric workflows).
AI-written summary · about
chapters (12)
- 0:00AI-native CMS intro
- 1:08Developer portal importance
- 2:29Choosing portal tech
- 4:38Tech choice insights
- 6:27Unifying docs with AI
- 8:30AI changes docs processes
- 10:38Docs as code benefits
- 12:47ETL in CMS evolution
- 14:55Need CMS in AI era?
- 16:20Drupal and AI trends
- 21:59AI-native workflows
- 22:46Q&A
related talks
35mHarnessing AI for API Business Documentation in a Devportal CMS [...]
26mMaking Docs and AI Work Together: Agentic Coding in the IDE
24mDocumentation and AI: How to write right now
23mDocumentation in the Age of AI: Why Docs Are a Product
51mLive Panel Discussion: Less Code? More Vibes? Web Dev in the AI Era
24mAI and Web Development: Hype or Reality
15mAI's Impact on Development, Post-Production & Support Journeys
01h 00mThe Future of Content: Context-Aware, Centralized, and Written by Robots