Tech conferences have a sameness problem. Most of them are polished until they are sterile, with speakers hiding behind a 100 slide deck and demos that were pre-recorded and are still announced as live. It is boring, and it looks nothing like the way senior developers actually work. That is why SmashingConf Amsterdam caught my eye for April 2026.
If you have been in the WordPress or WooCommerce ecosystem as long as I have, you know the real learning happens when something breaks. Watching a senior engineer chase down a race condition in real time teaches you more than a thousand Hello World tutorials. SmashingConf Amsterdam leans hard into that with its live-work philosophy.
Gezelligheid meets frontend craftsmanship
The Dutch have a word for this, Gezelligheid. There is no clean translation, but it lands somewhere between coziness and being among your own people. Running a conference in that spirit inside the Pathé Tuschinski, one of the most beautiful Art Deco cinemas anywhere, is a good instinct. Most conferences make you feel like you are stuck in a basement. This one is held in a room somebody cared about.
The lineup covers what actually matters in 2026: design systems, accessibility, and the point where AI meets UI engineering. Not “use ChatGPT to write a function,” but how you architect a context-based design system for a product with AI in it. If you are still working through modern CSS layouts and view transitions, this is the room where those get taken apart properly.
Modern CSS and the live-work philosophy
What sells me on SmashingConf Amsterdam is that the speakers are willing to fail in front of a room full of people. Watching Kevin Powell or Sara Soueidan work through a CSS bottleneck or an accessibility bug live is worth more than the tidy version of the same talk. It is the difference between theory and the war stories people trade at the pub after a launch.
So instead of a finished layout, I expect to see what it actually takes to get something like the View Transitions API working in a complicated application. This is the kind of modern CSS that reads as trivial in the docs and then turns awkward the moment it hits a legacy WordPress theme:
/* A naive approach to view transitions that often breaks on heavy DOMs */
::view-transition-old(root),
::view-transition-new(root) {
animation-duration: 0.5s;
}
/* The Smashing way: specifically targeting elements to avoid layout shifts */
.bbioon-product-card {
view-transition-name: product-expand;
}
@keyframes scale-up {
from { transform: scale(0.8); opacity: 0; }
to { transform: scale(1); opacity: 1; }
}The hands-on sessions
The workshops around the main stage are, frankly, more useful than most online bootcamps. Component anatomy with Nathan Curtis, measuring UX impact with Vitaly Friedman: that is the material that decides whether an enterprise project holds together. You also get one to one time, which is where the questions you would never post on Stack Overflow finally get answered.
If the front-end work coming out of events like SmashingConf Amsterdam is eating your dev hours, I can take it on. I have been wrestling with WordPress since the 4.x days, and I know how to land these patterns without breaking your backend logic.
Final takeaway for teams
If you own the business, this is not a holiday for your devs. It gets them out of shiny object syndrome and back into solving problems that are in front of them. April in Amsterdam is pleasant, but the part that improves your software is a few days inside a community that talks openly about what went wrong. The official SmashingConf Amsterdam site has the details, and there is a “Convince Your Boss” PDF if you need something to hand upstairs.
