Omar Aguirre @omers

When Opus 4.5 came out, it was a one-way door to a new way of engineering. Agents now do most of our coding. Knowing the inherent flaws and over-confidence of LLMs, we sent a clear message to our teams. Vibing and mission-critical infrastructure don’t go together. We’re sharing some of our early internal guidance in how we’re “agenting responsibly”, prioritizing security, durability, and availability at all times. vercel.com/blog/agent-res…

What does a production-ready decoupled Drupal setup actually look like? We recorded a full demo to show you. We just released our latest Drupal Decoupled webinar, where @jmolivas and @omers walk through the entire stack live. Content architecture, front-end integration, editorial workflows, and how it all connects out of the box. If you've been evaluating headless Drupal or you want to see how your team could start building on it today, this is a good place to start. Sign up now, you still get full access to the recording: octahedroid.com/webinars/drupa…

¡Hoy tenemos reunión! Agentic AI: El nuevo modelo de desarrollo de software social.org.mx/events/f27cbcb…

The DrupalCon gala was something else. Celebrating 25 years of Drupal surrounded by people who actually made those 25 years happen. That was something. Best part was catching up with Raul Solano, Alain Martínez, and Ronald Aguilar. We've known each other for years through this community. Different companies, different countries, but always crossing paths at these events. Those are the relationships that make open source worth it. I've been around Drupal long enough to see it evolve in ways none of us expected. And being in that room, you could feel there's still a lot left to build. Happy 25, Drupal, and cheers to everyone who's been part of this! #DrupalCon #DrupalConChicago

I'm at DrupalCon Chicago this week. Always good to catch up with familiar faces and have those conversations that only happen in person. We've been putting a lot of work into Drupal Decoupled over the past months, and I'm excited to show where the project is. But I also want to hear what you're building and what challenges you're running into. If you're here, DM me or come say hi between sessions! #DrupalConChicago #DrupalCon

Every time someone tells me decoupled Drupal means losing previews, a painful setup, or giving up the features that make Drupal useful. I want to show them this demo. So that's exactly what we did. We recorded a full live walkthrough of Drupal Decoupled. One-click cloud deployment to a working local environment, editing content, reordering components, submitting forms, all in real time. Instead of explaining why these misconceptions are wrong, we just built it in front of the camera. Every feature people assume you lose when you decouple is right there working. We also cover what's coming next, including Canvas drag-and-drop support and new framework starters. If your team wants a modern front end without giving up the structured content, workflows, and editorial tools that your clients and teams actually depend on, this is worth 30 minutes of your time. We'll be at DrupalCon Chicago next week. If you want to see this live or just want to say hi, come find us. Sign up here: octahedroid.com/webinars/drupa…

"Content editors will hate it." "You lose all the Drupal features." "It's too complex to set up." We've heard every reason why teams avoid decoupling Drupal. So instead of talking about it again, we decided to just show it. In our latest webinar, @omers and I do a live demo of Drupal Decoupled: from a one-click cloud deployment on Tugboat to a full local setup on your machine. The whole thing is the actual workflow running in real time. Here's what we cover: • One-click deployment with Tugboat. • Storybook integration for standalone component development. • Live content editing with iframe preview: edit, reorder, preview, and publish. • Webform integration so your forms still connect to Mailchimp, your CRM, etc. • Full local setup with DDEV, Drupal 11, Next.js 16, Tailwind 4, and shadcn Base UI. If you've been on the fence about decoupled Drupal, this is the fastest way to see what it actually looks like in practice. We'll also be at DrupalCon Chicago next week. If you want to see this running live or just want to talk more, come say hi! Sign up for the demo here: octahedroid.com/webinars/drupa…

Drupal's editorial experience doesn't have to break when you go decoupled, and your developers don't have to give up the tools they already prefer. We recorded a live demo of Drupal Decoupled, our opinionated headless stack, to show what it looks like when both sides get what they need. Our cofounders, Jesús Manuel Olivas and Omar Aguirre, walk through Drupal Decoupled end to end: one-click Tugboat deployment, iframe preview with instant content updates, webforms integration, and a local setup. All running on Drupal 11, GraphQL Compose, Drupal Recipes, Next.js, and Storybook. Available on demand starting March 26th. You can register here: octahedroid.com/webinars/drupa…

There's a version of this conversation that keeps going in circles: CMS or AI, structured content or speed, governance or flexibility. And if you've been building for the web long enough, you've seen this exact framing applied to every new tool that shows up. The answer is almost never one or the other. What actually changes the game for teams managing content at scale is when each layer does what it's good at. Structured content stays where it belongs, AI handles reasoning and generation, and the architecture connecting them is what makes both useful. That's where things get interesting, and it's the conversation we had in our latest Dev Talk. Full video here: youtu.be/L95jkTJe2yE?si…

Jesus Manuel Olivas @jmolivas

3 months ago

Components are becoming the shared language between developers, editors, and AI. That's the shift worth paying attention to. Developers build them. Editors compose pages with them visually. And AI can reason about them because they're structured data. When your CMS understands

0 0 1 185 0

Drupal Console has over 15 million downloads. But the thing that got it there wasn't better code or more features. It was treating it like a product. Most open source maintainers build for an imaginary user who thinks exactly like they do. @omers and I made the same mistake early on. When we started doing actual user research, identifying distinct personas, understanding what each group actually needed from the tool, everything changed. Contributors wanted rapid iteration. Daily users wanted stability. Evaluators wanted signs the project would still be around in two years. Product thinking helped us make those trade-offs on purpose instead of by accident. We wrote about the full framework we used, from documentation strategy to developer experience to marketing an open source tool. You can read it in full here: octahedroid.com/blog/productiz… P.S. These same principles are what we're applying now to Drupal Decoupled. I'll be talking more about that in the coming days as we get closer to DrupalCon Chicago.

Most open-source projects fail before they truly begin, and wrong motivations are usually the reason. If you start a project expecting to make money right away or build your personal brand, you'll quit the moment those things don't materialize fast enough. With Drupal Console, @omers and I weren't thinking about any of that. Drupal 8 was a massive breaking change and we genuinely didn't know how the new things worked, so we built a tool to learn and solve our own problem. Fifteen million downloads and a community of contributors came much later, but none of that was the goal when we started. Drupal Decoupled followed the same logic. Drupal has always been incredibly powerful for managing structured content and complex backend requirements, but pairing it with modern frontend technologies was still way more painful than it needed to be. We built Drupal Decoupled to close that gap, so teams could take full advantage of what Drupal does best while building faster and more efficient websites with the modern tools they already wanted to use. That organic process of starting with a real problem you live with every day is what gives a project the foundation to actually last. Recognition, community, sustainability, all of that can come eventually, but only if the starting point is honest. We wrote about what we've learned building open source projects and what actually keeps them alive long term. Link here: octahedroid.com/blog/why-most-…

The open source landscape is full of ambitious READMEs followed by silence. Repositories that launched with energy and then went dark within months. The conventional take blames documentation, marketing, or technical debt. But after years of maintaining Drupal Console and watching countless projects rise and fall, our co-founders @omers (CTO) and @jmolivas (CEO) have a different diagnosis: most projects are doomed before the first commit because of why they were started. In this article, they unpack the motivation patterns that lead to abandonment, the dangerous phase where enthusiasm becomes obligation, and three sustainability paths that give projects a real chance at longevity. Read the full piece on our blog: octahedroid.com/blog/why-most-…

15.75 million downloads on Drupal Console taught us that successful open source isn't about the numbers. It's about understanding who uses your tool and why they need it. @omers and I learned to approach our projects like products: clear documentation, realistic scope, and honest communication about what we can support. We also learned when to step back and let others contribute. In this webinar, we share frameworks for building projects that last: starting with problems you actually need to solve, creating sustainability models that work for your situation, and setting boundaries that protect both you and your users. Final chance to register here: octahedroid.com/webinars/open-…

After months of testing AI integration on real projects, we created five principles that actually help us decide when and how to use it. Some experiments worked. Many didn't. But the pattern became clear: the gap between AI hype and useful implementation isn't about which model you use or how you craft prompts. It's about augmentation over replacement. Process before automation. Context engineering instead of prompt tricks. Building for actual needs, not trends. And technical pragmatism over chasing every new release. This article breaks down each principle with examples from our work. No fluff about AI revolutionizing everything. Just what works when you're shipping production code with real users and real consequences. Read the full breakdown here: octahedroid.com/blog/our-5-ant…

This is a fun one, and my first webinar too 😅 🤗 🚀

Jesus Manuel Olivas @jmolivas

7 months ago

Building Drupal Console taught me that sustainable open source starts with solving your own problem first, not seeking recognition. @omers and I learned the hard way, along with lessons about treating projects like products, navigating inner circles, and understanding when your

0 1 3 176 0

Linux in a nutshell

Real diversity: Whoever shows up is welcome. Real equity: We all help carry the meaningful burden. Real inclusion: Your political opinions are your own. Open source gets better when it's focused on making great software for all, and doesn't obsess over tiresome divisive dogma.

Cloudflare just donated $150,000 to support Astro's open source development as our newest official hosting partner. Thank you @cloudflare! 🚀

Your SSG investment isn't technical debt if it's solving real problems. The issue is usually implementation, not the tool itself. Before planning a migration, understand your edge cases. Analyze your content volume, team expertise, and actual pain points. Then decide if you need new tools or better architecture. Our webinar covers the decision framework enterprise teams need. Available tomorrow! Be sure to save your spot here: octahedroid.com/webinar/state-…

joining the super talented team at @vercel as a designer. working on @v0 and the next gen of creative tools