Michal Kokocinski’s Post

After 8 years, I cleaned up and refactored my UltimateDrupalReference repository. It is now a more curated, practical reference for modern Drupal developers and site builders, and I'll keep updating it regularly. If you work with Drupal — or onboard people into Drupal projects — this might be useful: https://lnkd.in/eqXus2JV 🚀

We Discovered Site Builders Are Still Using a 10-Year-Old Workaround for Drupal Cache Handling (The Core Team Finally Fixed It) https://lnkd.in/eSfYNbHB

Excited to share that I’ve published my Drupal project Content Migration Porter on Drupal.org. This project provides the Content Porter module, which helps migrate selected Drupal content from one project to another using a JSON export and import workflow. The module should be installed on both the source and destination Drupal sites. On the source site, administrators can select content, media, custom blocks, and related items to export as a JSON file. On the destination site, the same JSON file can be imported to recreate the selected content. Recommended flow: First migrate the required site structure, such as content types, fields, paragraph types, media types, taxonomy vocabularies, and custom block types. Then use Content Porter to migrate the actual content. This can also be used along with Config Entity Exporter when the destination site needs the required configuration before importing content. Key features: Export selected Drupal content as JSON Import exported JSON into another Drupal site Supports content, media, custom blocks, depending on the site structure Provides a simple admin UI under Content > Content Porter 🔗 Check it out here: https://lnkd.in/gdz5NgxE Have you tried this module? Let me know your thoughts, suggestions, or any improvements you’d like to see. Your feedback helps us make it even better! #Drupal #Drupal10 #Drupal11 #DrupalDevelopment #DrupalCommunity #DrupalContrib #DrupalModules #OpenSource #OpenSourceContribution #PHP #WebDevelopment #CMS #ContentMigration #DataMigration #MigrationTools #DeveloperTools #BackendDevelopment #SiteBuilding #JSON #ContentManagement #DrupalOrg

Updated my headline to just "Top-tier Drupal websites for complex needs" Often less is more. It's impossible to capture everything in a single sentence anyway, especially without resorting to LinkedIn lunatic corporate sounding lingo. Who I help? - no room given the average attention span Why I exist? - no room given the average attention span What's my USP? - no room given the average attention span So... I guess this will just have to come through from my posts and articles. For now, my headline is as snappy as I can make it to get the main point across. If you need a top-tier Drupal website to meet some complex needs, then it could be worth a conversation.

It's live. Same day. 🎉 This morning I wrote about building a headless Drupal CMS for a food truck client — choosing the hard path on purpose to learn a platform I need to know. By this evening, it's running in production. A Drupal instance on Render, feeding content into a Vue.js frontend via JSON:API. The client logs in, edits their menu, and the site updates. Exactly what I set out to build. The honest truth? Connecting Drupal up as a headless CMS was surprisingly straightforward. JSON:API ships with Drupal core. CORS config is a few lines in a YAML file. The content modelling just makes sense once you've done it once. Were there bumps? Of course. Ephemeral container filesystems. Apache config that silently ignored .htaccess. A CORS header that took 30 seconds to fix but felt like an hour to diagnose. But here's what made the difference — I paired with Claude as my guide throughout. Not just asking questions, but working through the architecture together, debugging in real time, and having someone (something?) that could see the whole picture at once. It's a genuinely different way to learn. You're not waiting for Stack Overflow. You're not skimming docs hoping the answer is on this page. You're just building, and getting unstuck fast. One client site. One day. Whole lot of Drupal reps logged. More to come. #Drupal #Vue #HeadlessCMS #WebDevelopment #LearningInPublic #BuildInPublic #ClaudeAI

Want to learn how to create a reusable Cypress login function that speeds up Drupal testing with session caching and saves your team time on every test run? Check out Daniel Davis-Boxleitner's latest article! https://lnkd.in/gmw6h62k

Last few months, there has been a lot of discussion regarding Drupal Canvas, which is being implemented as the new way of Page building in Drupal. Initially, I ignored it, thinking it was just another alternative to Layout Builder, Layout Paragraphs, or Display Suite. But since it has become a part of Drupal CMS 2.0, I thought of giving it a try. I was absolutely wowed by what it provides. This is not just a new way of page-building in Drupal. This is a rebirth of Drupal. Drupal Canvas gives the ability to create a Drupal website to even those who do not understand the basic concepts of Drupal like Content type and Taxonomy. Creating a landing page with Drupal is as easy as with Wix or Shopify. And the good thing is it's just version 1 and only going to get better in the coming days.

Speaking at Drupal Dev Days 2026 🇬🇷 I’ll be sharing a session on 𝗔𝗰𝗰𝗲𝗹𝗲𝗿𝗮𝘁𝗶𝗻𝗴 𝘆𝗼𝘂𝗿 𝘁𝗿𝗮𝗻𝘀𝗶𝘁𝗶𝗼𝗻 𝘁𝗼 𝗦𝗗𝗖 𝘄𝗶𝘁𝗵 𝗔𝗜-𝗣𝗼𝘄𝗲𝗿𝗲𝗱 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 on 𝗙𝗿𝗶𝗱𝗮𝘆, 𝟮𝟰 𝗔𝗽𝗿𝗶𝗹, from 𝟭𝟰:𝟱𝟬 𝘁𝗼 𝟭𝟱:𝟯𝟬 in 𝗥𝗼𝗼𝗺 𝟮 (𝗜𝗻𝗱𝗶𝗴𝗶𝘁𝗮𝗹) This came from a pattern we kept seeing during SDC transitions: the work was repetitive and manual. When you are moving a large design system from Twig components to Single Directory Components, a lot of time goes into repeating the same structural work component after component. The problem was not complexity. It was volume and consistency. We built an AI-assisted approach that analyzes existing Twig components and helps generate SDC-compatible output. Handling much of the heavy lifting through a combination of deterministic rules and guided intelligence rather than relying purely on end-to-end code generation. The practical value was clear: • less repeated migration effort • fewer avoidable errors • more time spent improving components instead of rewriting metadata The session will cover what was automated, what still needs review, and where this approach fits in real Drupal delivery. Also, I’ll be sharing about something we’ve been experimenting at QED42: 𝗙𝗶𝗴𝗺𝗮 𝘁𝗼 𝗱𝗲𝘀𝗶𝗴𝗻 𝘀𝘆𝘀𝘁𝗲𝗺 𝘄𝗶𝘁𝗵 𝗦𝗗𝗖 𝗰𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 If you are working through SDC adoption, would be good to connect there🤝 Looking forward to the discussions and collaborations!

New! Drupal 11: Cascading Select Forms With HTMX This is part four of a series of articles looking at HTMX in Drupal. In the last two articles we looked at using HTMX with controllers in different ways. This time I'll be venturing into the world of HTMX and forms. In this article we will look at creating a form that contains multiple select elements and then use HTMX (and a little bit of the form states API) to tie them together so that selecting one element updates the others. https://lnkd.in/eH3rQWDs #drupal #drupal11 #htmx #drupalDevelopment #hashbangcode

Still writing about HTMX and Drupal! I have planned out two more articles and then I might take a break for a bit :D Unless, of course, you want me to cover something specifically? Let me know!