Can we make default Tailwind a more accessible choice?

Published by hadi on

A sharp look at Tailwind’s default rem-based breakpoints, and the accessibility tradeoff they make. It explains how browser font-size preferences can shift layouts, why that can help some users, and why px breakpoints are still a defensible choice.

Read more

Categories: PHP
Tags:

Related Posts

PHP

Why we removed AI solutions from Flare

We explain why Flare’s old AI-generated solutions no longer fit the way developers debug with modern coding agents. The replacement is a better workflow built around the MCP server, CLI, Copy for AI prompts, and Read more…

PHP

`exit()` may silently break your parallel tests

Michael explains why exit() can make parallel test workers crash without useful diagnostics, and why verbose flags do not help when the process dies outside PHPUnit’s control. The fix is simple: throw an exception instead, Read more…

PHP

Amped up

Sebastian explains why Amp became his default coding harness, and why user experience now matters more to him than model churn. He also shares the AGENTS.md tweaks that reduced overzealous verification during day-to-day coding. Read Read more…