Jeff Fischer

Drupal just got easier to work with — without losing what makes it powerful. 🧩 Canvas 1.0 introduces a component-based visual builder that balances layout control with developer flexibility. It’s not a shortcut—it’s a smarter path. In this week’s editor’s pick, Kazima Abbas highlights: • What Canvas means for editors and devs • Reactions from leaders like Aaron McHale and Jillian Chueka • How it fits Drupal’s low-code ambitions Read the full breakdown + other key ecosystem updates: https://lnkd.in/gVHfK6gG #Drupal #OpenSource #WebDev #LowCode

15

🔧 Technical Update: SSD Consulting Website + LMS Redesign The new site rebuild is running on Next.js 13+ with modern React patterns, strict TypeScript, and an LMS-ready architecture. Recent code review results: ✅ Code Quality & TS: 9/10 🔐 Security: Hardened (noted improvements around storage & auth) ⚡ Performance: Optimized imports, image handling, and layouts ♿ Accessibility: Semantic HTML + Tailwind-first UX 🧪 Next step: Adding unit/integration tests Approved for production with minor fixes—now focused on security hardening, testing, and scale.

3

Did you know Drupal Webform can redirect users to a custom page after they submit a form? Instead of showing a basic confirmation message, you can send them to any URL on your site or off it. Here is how to set it up: - Create a simple confirmation page on your site. - Go to the Webform settings and open the confirmation section. - Change the confirmation type to "URL with message." - Enter the page path into the Confirmation URL field. When someone submits the form, they get redirected to that page. Webform also passes a submission token in the URL. You can use that to load the submission data and personalise the confirmation page. #Drupal #Webform ~~~ If you found this post helpful. ♻️ Please repost and follow. Need help with your Drupal project? Send me a message.

11

1 Comment

Server side rendering (Twig in Drupal’s case) with a sprinkling of JavaScript is the best architecture for content websites. HTMX makes the “sprinkling of JavaScript” part easy, enough library help to avoid bespoke code and avoid the bloated frontend frameworks that have been overprescribed. HTMX works with the DOM, doesn’t replace it. HTMX believes in the durability of hypertext, it doesn’t shun it. Thanks to everyone involved in this effort. Truly well done. Can’t wait to use it!👏

25

2 Comments

Feeling left out on the Claude Code talk? If you're a non-technical, knowledge worker or business owner - this is for you Been building a lot of workflows and automations with coding agents (Claude code and open code), here's my tips Setting up your files 1. Push as much as possible to deterministic scripts. Never use AI when a script (or combo) can get the job done. 2. Use YAML files as many databases inside of your skills and agents. 3 Use Markdown files as templates, and digested consolidated reference documents on anything you’re dealing with, from your business marketing strategy to your hiring protocol to langgraph documentation. 4. Your skills should explain how and even detailed instructions on why. 5. Always include checklist in your skills. These are checklists used for validating if a skill was done correctly, plans on how to correctly carry out a skill, and various sub, niche references, such as compliance, checklist, or marketing voice checklist. 6. Your skills should be lighter than your deterministic scripts and templates and references. Do you want most of your meat in those reference files, database files and scripts. Do you want skills to be the next layer to help navigate and use all of that. 7. Agents should have goals and outcomes in outputs. It should be the what it should inform about the skills available, the possible workflows and succession of skills and provide the end goal, and the perspective. 8. The agent should also call out the validation of that output, using the references in skills, such as checklists. 9. Commands should act like small orchestras that peace together various agents with a targeted outcome. 10. Commands should take arguments in those arguments should be specified inside the command marked down file. This is how we feed it ideas or concepts or tasks and makes it much cleaner to execute. The concept is - commands - thinnest - agents - thin - skills - thick - scripts - thicker - reference - thicker The reason we do this is - control (through deterministic work) - context management (by starting thin and only pulling in what we need when we need.) - token preservation Stacking commands into extremely flexible and powerful workflows is where you start to really get work done in a powerful, controlled, validated way Once your command give you the outputs you want (testing and modifying agents/skills/references to dial outputs) you can then create a script to run commands on autopilot and fully automate large builds. This is the Ralph Wiggum script you may read about. After that, you start spinning up multiple sessions to do things so you’re not waiting on a 2 hour build before you ask a quick 5 min task Finally, you realize that you can create an agent to spin up additional sessions as needed and run commands or scripts, without being tied up. This is orchestration layer you e seem mentioned This is a very basic primer on setting up Claude Code for the very non technical

3

1 Comment

Custom software isn’t just tailored, it’s built to last. Off the shelf tools may seem quick or budget friendly at first glance, but they come with hidden limitations: 1. rigid structures that stifle growth, 2. costly integrations as your needs evolve, 3. and an uphill battle against generic features. We’ve seen it again and again, custom solutions future proof your business by adapting seamlessly to scale, integrating precisely where you need them, and delivering long term savings. So here’s the real question: Are you asking for something that grows with you or settling for what fits in a box? #CustomSoftware #Scalability #BusinessGrowth

7

If you follow me on Twitter, you might remember a post where I mentioned solving a tricky architectural challenge while working on the official PHP MCP SDK and how PHP Fibers came to the rescue. We needed a way to pause execution mid-request, let the server talk to the client, wait for a response (in some cases), and then resume exactly where we left off, all while keeping the developer API looking standard, synchronous and simple. I promised a deep dive into the solution, and today I’m delivering it. (🔗 Link to the article is in the comments) This is probably the longest and most comprehensive article I have ever written. It’s not a quick tutorial. It’s technical, thorough and designed to reward patient reading. I went all in discussing the exact problem faced, how Fibers solved the issue for MCP’s client communication flow, the full architectural patterns used for cooperative multitasking in the SDK, and a build-from-scratch example of a cooperative task manager. It’s a lot, but I promise, you will walk away with a solid understanding of how to leverage Fibers for your own complex systems when the need arises. Cheers 🥂

29

1 Comment

Quick tip for anyone building custom Typst templates for use with Quarto: If special characters like $ are causing mysterious compilation errors that standard escaping won't fix, try hexadecimal escape sequences instead. For example: \u{24} for the dollar sign. Wrote up a quick note covering this technique, including how to use Typst's ASCII table tool to find hex codes for any character. Could save you some debugging headaches! https://lnkd.in/eE62SBGb #Typst #Quarto

39

Ensuring ADA compliance is an ongoing challenge, not a one-time task. From updating themes like Beaver Builder to auditing new content monthly, accessibility requires constant vigilance. Standards like WCAG, plugin updates, and even minor modifications can disrupt previous fixes. For many businesses, managing multiple websites becomes time-consuming and costly. While tools like Wave or automated scanners help, true accessibility necessitates a hands-on approach. Ultimately, investing in accessibility goes beyond avoiding lawsuits; it’s about fostering an inclusive web experience for everyone. Jackson Dunagan and Carlos Caneja https://brightcommerce.io/ #ADACompliance #Accessibility #WCAG #WebDevelopment #InclusiveDesign #WordPress #WooCommerce

34

3 Comments

If every Drupal change requires caution, the platform isn’t stable. It’s just quiet. Upgrade anxiety, manual deployments, and firefighting aren’t normal. They’re warning signs. We’ve written about what’s usually hiding underneath. https://lnkd.in/ecN2MXeb #CodeEnigma #WebDevelopment #Drupal

2