John Carbone

When installing Drupal CMS 2.0, you get to choose between two different site templates: Starter and Byte. These aren't just themes. Site templates are actually a type of recipe that configures your entire site, not just its look and feel. Think of them more like installation profiles. ➜ Byte gives you a full demo site with the new Mercury theme. A clean, agency-style layout with pricing tables, feature grids, and all the components you'd expect from a modern SaaS site. ➜ Starter keeps things minimal, giving you a clean foundation for custom builds. Either way, you're getting a complete site configuration. Modules, content types, layouts, and functionality all packaged together and ready to go. Link to full tutorial and video below. #drupalcms #drupal ~~~ If you found this post helpful. ♻️ Please repost and follow. 📧 Join our newsletter; link in the first comment.

44

1 Comment

Most legacy PHP systems aren’t unstable because they’re old. They’re unstable because they’ve absorbed years of unstructured change. Quick fixes. Partial rewrites. Urgent features layered on fragile foundations. Over time, the system stops being predictable. When predictability goes, confidence follows. When confidence goes, progress slows. Stability rarely requires dramatic rebuilding. It usually requires structured assessment, risk mapping, and controlled intervention. Calm, methodical work. In business-critical environments, that approach outperforms urgency almost every time.

2

🔐 Enhancing security in Drupal with a simple composer command🔐 I’ve been using "composer audit" lately in Drupal projects and it’s one of those simple tools that just makes a lot of sense. If you’re not familiar: it checks your "composer.lock" file for known security issues using public advisories. Just run in your CLI: ⌨️ composer audit ⌨️ No setup, no plugins - and it can catch vulnerabilities in contrib modules and PHP libraries before they cause trouble. Why it is important (especially for Drupal devs and DevOps): ➡️ Drupal relies on a ton of third-party packages. ➡️ Vulnerabilities often show up after you’ve deployed. ➡️ Super easy to integrate into CI/CD pipelines. 🤖 Want machine-readable output? There’s a "--format=json" flag. And if you only care about critical/high severity issues, this one-liner with "jq" is really handy and works without any additional packages directly in DDEVs CLI: ⌨️ composer audit --format=json | jq '.advisories[] | .[] | select(.severity == "high" or .severity == "critical")' ⌨️ Also, don’t forget to subscribe to the Drupal Security Team email list - Composer helps spot general PHP package issues, but the email list is your early warning system for core and contrib-specific vulnerabilities. Security is a lot of work but it doesn't need to be painful. Little habits like this go a long way. #Drupal #Composer #Security #DevOps #PHP #Drupal

51

3 Comments

Web editors shouldn't waste time wrestling with HTML — they should be busy bringing great stories to life. At Smith College, we completely flipped the Drupal experience: 🌟 Editors create visually, joyfully, and in real-time — without developers, HTML, or CSS. 🌟 Content workflows now rival the best consumer-friendly platforms (think Wix and Squarespace), giving editors total creative freedom and control. 🌟 The real innovation wasn't technical — it was strategic. We replaced gatekeepers with trust. Editors went from frustrated to fearless. When you trust your content creators, your website transforms. 👇 Learn how Smith College editors became passionate advocates of their website — and #Drupal: https://4ktch.in/smith #DrupalRevolution #ContentStrategy #EditorExperience #DigitalTransformation #HigherEdWeb

48

4 Comments

What we are seeing here is the same Drupal CMS AI Agents, that come bundled with Drupal CMS, using Claude Code itself as the runner to actually run the agents. End-user can use the Chatbot like normal. Behind the scenes you can see a Claude Code Process appear and on the right of this screenshot is a view into the session that is stored inside Claude Code. Claude code stores its history as JSON files and now Drupal can view that history. It works! We're using a new Tool CLI module that takes the tool api and allow you to call individual tools and agents via CLI. In Terminal we can click "Behave as Agent" where the debugger pretends to be an AI Agent that has already been created. Whats cool about this, is there is no migration needed. A little flag on any Agent you've already built in Drupal can now run with Claude Code itself! #Drupal #DrupalAI #AI #ClaudeAgentSDK #ClaudeCode #MaybedothiswithDrupal?

110

11 Comments