191–200 of 236 posts
Earlier quoted context omitted.
It's a compilation of best practices, and valuable as a one-stop-shop and checklist.
Sites like these have existed for a long time. I've used this one for years: https://frontendchecklist.io/rules I think what sets this specific one apart is its focus on "AI-readiness"
Earlier quoted context omitted.
It's a compilation of best practices, and valuable as a one-stop-shop and checklist.
That's debatable. Every best-practice arose to solve a real problem within a context, and is only "best" if that context applies. If you apply best-practices without a regard for that context, you end up with a dull, cargo-culted checklist of must-haves to beat people over the head with, without deriving any true human value. The compiler of this artifact is making a judgement call[0] of what best practices apply som…
The approach of marking items as required/recommended/optional addresses your concern. Too bad this specific checklist is LLM-generated.
Earlier quoted context omitted.
I swear to God. I just want to go back to the 2000s where everything was just plain HTML and some basic CSS, if at all any, by default you got responsive design out of the box, readable text and super user friendly GUI from the browser's own default stylesheet. Today you open any website. Everything is a fucking component. A simple dropdown with a finite list? Has its own loader and makes 10 fetch requests for no rea…
The 2000s, the golden age of web design, when people built inaccessible IE6-only mystery-meat navigation websites with Flash and HTML tables that dynamically loaded JS using iframes.
Earlier quoted context omitted.
In the 2000s wasn't everything just misused/abused table layouts? Maybe we frequented different places, but that's how I remember it.
That's funny because the argument against tables was always that they added extra markup a.k.a lines of code, only to replace them with dozens of nested divs, half assed CSS layout ideologies (floats and clear's, for example) and barely functional JS that all somehow needed to work in sync which was almost never. That's how NPM was born. Tables worked with 100% of the browsers. The alternatives needed polyfills and s…
2. https://validator.w3.org/check?uri=https://www.tirreno.com/&...
Earlier quoted context omitted.
That's funny because the argument against tables was always that they added extra markup a.k.a lines of code, only to replace them with dozens of nested divs, half assed CSS layout ideologies (floats and clear's, for example) and barely functional JS that all somehow needed to work in sync which was almost never. That's how NPM was born. Tables worked with 100% of the browsers. The alternatives needed polyfills and s…
True. We have a product website (1) built entirely with tables and HTML 4.01 (2) in 2026. Works as expected everywhere. 1. https://www.tirreno.com 2. https://validator.w3.org/check?uri=https://www.tirreno.com/&...
Earlier quoted context omitted.
That's funny because the argument against tables was always that they added extra markup a.k.a lines of code, only to replace them with dozens of nested divs, half assed CSS layout ideologies (floats and clear's, for example) and barely functional JS that all somehow needed to work in sync which was almost never. That's how NPM was born. Tables worked with 100% of the browsers. The alternatives needed polyfills and s…
True. We have a product website (1) built entirely with tables and HTML 4.01 (2) in 2026. Works as expected everywhere. 1. https://www.tirreno.com 2. https://validator.w3.org/check?uri=https://www.tirreno.com/&...
Earlier quoted context omitted.
The 2000s, the golden age of web design, when people built inaccessible IE6-only mystery-meat navigation websites with Flash and HTML tables that dynamically loaded JS using iframes.
Can't upvote this enough. People have very selective memory of how the 2000s web worked. Every other website requires Flash just to show you a carousel of images. "Serious" business websites implemented in slow, buggy Java applets. iframes everywhere. Incredibly fucked up tables with no semantic meanings in your HTML just to do what modern flexbox now does in two lines. No one cared about accessibility of anything. C…
> Every other website requires Flash just to show you a carousel of images. "Serious" business websites implemented in slow, buggy Java applets. iframes everywhere.
Do you see the irony? This is a very selective example by itself. The table based minimal HTML + CSS websites existed throughout the decades (even so today) which is what I'm referring to specifically.
Earlier quoted context omitted.
> Yeah, the entire suite of proposed "standards" catering to agents looks like a temporary measure to duct-tape over the limitations and token costs of today's agents. That's fine. We need a fix for today's problems today.
> That's fine. We need a fix for today's problems today. No, we don't. It is Anthropic, Google, OpenAI et al. who need a fix for those problems today. Let them deal with it.
I don't think you understand what an instruction files or a agent skill is. They are nothing more than glorified custom prompts that are automatically integrated in sessions by the user agent. The likes of Anthropic are paid either way.
It's not Anthropic et al who seek to do less work to get models to do their work, nor do they care if prompts are shared. At most it is a minor UX improvement, and one which is shared across AI vendors.
Earlier quoted context omitted.
Right but how would you even display a vertical menu back then? `float: left` was rather bad, so you went back to using tables[0]. Good luck making these responsive. [0]: and to using dozens of images sliced to fit your table cells, for that cool hover effect as well as round corners. :-)
Why would documents have menus? Menus are for applications. And there was nothing wrong with tables for layout, especially back then when the alternatives were very brittle.
s/menu/navigation
> And there was nothing wrong with tables for layout, especially back then when the alternatives were very brittle.
I never said there was anything wrong with tables. OP said there was nothing preventing the design from being responsive, to which I responded yes, there was, at least in a lot of cases.
(Responsiveness was also mostly irrelevant back then because smartphones were not a thing yet.)
"Agent Readiness" will likely age as well as "Web 4.0 Blockchain Integration" has. (To be entirely clear, not because agents won't be a relevant thing, although certainly I have my doubts, but because I believe even if they are a relevant thing, requiring special allowances from sites undermines the whole point, and such things will only end up used by bad actors to mismatch what agents see to what humans see, and so…
I swear to God. I just want to go back to the 2000s where everything was just plain HTML and some basic CSS, if at all any, by default you got responsive design out of the box, readable text and super user friendly GUI from the browser's own default stylesheet. Today you open any website. Everything is a fucking component. A simple dropdown with a finite list? Has its own loader and makes 10 fetch requests for no rea…