Fernandez is a technology leader with 20+ years across software development, architecture, and martech. He has delivered 250+ projects in 25 countries for global brands, taking on roles from developer to CTO and strategist. Fluent in Spanish, Portuguese, and English, he bridges business vision with technical execution. As Executive Director of Technology at VML, he focuses on AI, composable architectures, and data-driven personalization.
[ENG] No Authors. No Pages. No CMS. More Content Than Ever. Welcome to 2030.
The fundamentals of a CMS were built around three assumptions: humans author content, the system stores and publishes pages, and frontends are built once and rendered many times. By 2030, on a ride that has already started, all three will have inverted, and the architectural decisions we make now will determine whether our platforms travel with the shift or get left behind. Production inverts. It's already happening: bots draft and humans orchestrate. Quite very often, the author's job is no longer to "create" content, but to describe intent, voice, and acceptance criteria — then direct the agents who draft, fact-check, localize, and adapt. WYSIWYG gives way to WYDIWYG: (What You Describe Is What You Get...most of the time, at least). So, new CMS primitives are emerging: intent objects, brand contracts, agent identities, evals, and cost budgets per piece. Substrate inverts. What we used to call CMS becomes invisible. It becomes a semantic layer of authored and derived content (embeddings, summaries, translations, agent-ready chunks, voice variants), addressable by agents over MCP, where "publish" is continuous and the URL is one address among many. Most content in 2030 won't be authored; it will be derived. CMSs will become a materialization engine rather than a repository. Surface inverts. Frontends are synthesized on demand. Design tokens and component logic become runtime contracts that an agent assembles into an ephemeral UI per request — voice, AR, web fragment, embedded inside someone else's agent. The frontend stops being something you build and becomes something that's requested. This talk walks all three inversions as one connected architectural shift, with concrete patterns for each, what survives (the content model, governance, the design system as contract), what dies (the page, the template, the publish button, the URL as primary address), and what every CMS team should be doing now to prepare.