> just plain HTML and some basic CSS, if at all any I built my own website like this and I love it. Highly recommended.
I built a website the other month with just pure HTML. It seems even easier to maintain.
First version of my website was pure HTML but that got unwieldly fast. I've been maintaining my own fork of the old pug/jade templating engine instead. It's essentially pure HTML but with no closing tags and with features to reduce repetition. I've been enjoying it a lot.
I think the presentation may fail to land because, on the surface, it is nearly wholly AI-generated, but also after reading through many of the entries, everything besides the Agent section seems to clearly communicate solid web hygiene and I wouldn't mind sending this to a burgeoning web developer. It is ironic though that the site itself fails to employ even its own "required" practices, but that's more of an aside…
Thanks for making this! I planed to make something like this as a skill for my self, but pasting this into any agent chat works like a charm. I just had my local model (Qwen3.6 27B / pi) make a list of all the required standards an older hugo site of mine was missing, make a todo list and then run through the whole thing one by one, giving me chance to review each change. It even made the missing favicon by cropping…
How much have you mucked with `pi`? I love the "zero overhead" aspect of the short agent/system prompt, but I can just imagine the waiting and potential dead-end's it'd get itself into if I just let it rip on a random task.
"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…
The simple fix of the modern web is simple: no JavaScript. Enforce it as a security measure or whatever, but scripting is what is making the web worse.
Thanks for making this! I planed to make something like this as a skill for my self, but pasting this into any agent chat works like a charm. I just had my local model (Qwen3.6 27B / pi) make a list of all the required standards an older hugo site of mine was missing, make a todo list and then run through the whole thing one by one, giving me chance to review each change. It even made the missing favicon by cropping…
How much have you mucked with `pi`? I love the "zero overhead" aspect of the short agent/system prompt, but I can just imagine the waiting and potential dead-end's it'd get itself into if I just let it rip on a random task.
I have used it almost daily for the last few months, with only 3 simple extensions. On this project I spent a few minutes adding context to an AGENTS.md and having it write a todo list based on the spec, then I start a new chat for each task on the list. Most changes are just a few lines of code so it is very quick to review. But this a very small website project though.
modern agents already do this via content negotiation and will attempt to retrieve the markdown version of a given site https://www.sanity.io/learn/course/markdown-routes-with-next...
But that isn't that different from requesting the llms.txt version. Why not just make it so the useful content you want the LLM to focus on is easily retrievable from the same HTML the user's browser gets? The sanity.io page writes: > serving agents a bunch of HTML might just bloat their context window. That's only true if you assume the the agent can't extract the useful text before it goes into the model as tokens.…
How can it know which tokens not to read without reading them? and llms.txt is a single file for the whole site... not the same
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…
Responsive design out of the box? Were you actually there? Back in 2000 you could make a career out of scripting browser polyfills or "DHTML".
The idea that 00s websites were responsive is laughable. Websites used to tell you they are designed for resolutions 1024x768 and above, because they hardcoded the size and position and everything and the moment you sizes your browser window down a horizontal scroll bar appears, or worse. Say what you want about modern web practices but responsibility is only getting better, not worse.
https://validator.w3.org/nu/?doc=https%3A%2F%2Fspecification... I don't get the goal of the website. It's averted as a specification, but to spec what ?! Everything is sourced to another "source of truth".
It's a compilation of best practices, and valuable as a one-stop-shop and checklist.
Never mind, it’s LLM-generated, not the product of considered thought.
The W3C should really be doing this kind of curation. Or people like those who run caniuse.com.