Post

maybe dumb question but why is this a problem? this basically means they get inlined into initial HTML (ok maybe a bit silly) and then driven from DOM for new renders. “use client” does NOT mean “exclude me from HTML”

Oops, i meant to say i tested in 2022 *on my Steam Deck.* Throwing weird devices at a website and looking for breaks is a sure way to make sure what you’re building will help others.

Sad that the agency that came in and pushed me out later moved the whole thing to a third-party SaaS, because it really made me happy knowing that the site i developed was battle tested and would work no matter what kind of browser you threw at it.

It's always sad to see work like that get lost or scrapped when new teams take over. Accessibility is often one of the first things to go.

"Go sit in an uncomfortable chair, in an uncomfortable location, and stare at an uncomfortably small screen with an uncomfortably outdated web browser. How easy is it to use the websites you've created?"

In the old days I'd use the Lynx browser to see how badly the HTML structure's semantic foundation would hold up in a *text-only* browser. You can also disable CSS and JS to see if the site still works as plain HTML. This is good QC as it reveals all sorts of hidden things one can improve as well.

You don't need a content management system if you're not going to manage your content. That's half the budget back right there.