Latest post Dries
How Claude reviews our docs every Monday
How we keep our docs up to date with a weekly Claude review in GitHub Actions.
Latest post Dries
How we keep our docs up to date with a weekly Claude review in GitHub Actions.
I tried moving a side project from Tailwind to StyleX, mainly to see whether its more explicit approach to styling works better with LLMs. I still find Tailwind faster to write by hand, but StyleX made me notice the value of having things like CSS properties, tokens, variants, and component styling conventions represented directly in the code. This post is mostly about those trade-offs, and why the extra verbosity bothers me less now that an LLM is doing more of the mechanical typing.
SébastienThe pipe operator was a great addition in PHP 8.5. It brings the ergonomics of wrapper objects with the composability of standalone functions. Unfortunately, the standard array & string manipulation functions in PHP aren't exactly known for their API consistency, which makes the pipe operator awkward to use. Piper is an attempt to wrap the standard library to make it compatible with the pipe operator.
SebastianI spent the large part of two days reviewing a front-end that was built almost entirely by AI for a real product. Short verdict: locally great, globally drifting. Here's how I did it, how I used AI to help me out, and the ruleset I came back with.
SébastienIntroducing ourray.app, a shared cloud-based Ray instance where everyone's debugging output streams live on one dashboard. Install spatie/our-ray, prepend our() before your ray() calls, and your dumps are visible to the world.
Native HTML/CSS features like dialog, the Popover API, CSS Anchor Positioning, and customizable selects are catching up to what libraries like shadcn and Radix provide. Here's what changed, what's possible now, and how it might reshape how we build frontend components at Spatie.
Nick BeversWith multiple large, long-running Inertia apps in production we know what we like, don't like, and what works. It’s time to formalize our thoughts and decisions as we’re starting new projects and onboarding a few developers this year.
SebastianWhere possible, we try to stick with the popular choice for our tools. There's a lot of value in sticking to defaults. We only stray away from them when we have a really good reason. In the case of Laravel (and Inertia), the popular choice would be Vue, but we've landed on React. Why? Story time!
SebastianIn short: we'd like to be a substantial part of your project.
Get in touch via email