| Me | https://jamesbasoo.com |
| Me | https://jamesbasoo.com |
London. Next week. The Astro core team, more than 100 Astro devs, and… you?
Unique swag, talks from @ascorbic, @matthewp, @swithinbank, and more.
Sign up: https://luma.com/lzh944vx
2026 work update. Still looking for full time or part time work. Remote or onsite in Spain.
I fall neatly into the creative developer / design engineer category. I'm good at #html, #css and #js
I mainly work with #AstroJS, #CraftCMS, #Kirby and #Shopify. I don't use UI frameworks and take pride in a craft I’ve spent over 20 years learning.
Open to collaborating with companies and individuals to bring projects to life. It would be nice if you do work that gives good belly feels.
📆 4 March 2026
Are you a web developer, or content author, with questions about why the web is the way it is, how it's evolving, or suggestions on how it should evolve? Do you want to know more about how the standards that govern how the platform works are being developed?
Meet the TAG for a panel discussion at Samsung KX, London 🇬🇧
#WebStandards #WebArchitecture #TechnicalArchitectureGroup
See more at:
https://www.w3.org/events/happenings/2026/meet-the-w3c-technical-architecture-group/
I'm officially a curmudgeon. Here's a rant about the Shadcn component library and how over-complicated its radio buttons are: https://paulmakeswebsites.com/writing/shadcn-radio-button/
(Inspired by this week's work frustrations lol)

Radio buttons are built into web browsers. Why are we using a UI library that wraps another UI library that rebuilds radio buttons from scratch? Why does rendering a radio button require multiple dependencies and several kilobytes of JavaScript? How did we make a built-in browser control so complicated?