The Website Specification
- Latty - 34408 sekunder sedan"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 will be intentionally ignored.)
- fmajid - 28462 sekunder sedanI'd love best practices around, say, login forms, e.g.:
- use standard input field names password managers recognize - disable autocompletion and autocapitalization on the login field
- if it's an email, use the correct HTML5 input type
- don't have a form with just a login email and force the user to click to enter the password
- follow NIST SP 800-53, e.g. no SMS 2FA and no arbitrary password rotation and composition rules
Or how many sites that have a form with only one input don't automatically focus on it.
- kaiokendev - 10356 sekunder sedanI 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.
- _ache_ - 29696 sekunder sedanhttps://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".
- zophi - 35278 sekunder sedanHmm wondering how common some of these are ... I'd love /.well-known/change-password but it looks like https://news.ycombinator.com/.well-known/change-password and google.com/.well-known/change-password don't seem to be implemented?
- unchar1 - 24955 sekunder sedanOpening the site on my macbook shot the CPU usage to >50%.
Seems a bit ironic considering that it's supposed to be a specification on how a website should be.
- ramon156 - 8362 sekunder sedanMy favorite specs are hallucinated ones. Good job, I suppose?
Can't wait for an ISO alternative that is agent-driven, or slot machines that are run by LLMs
- selfhoster1312 - 34388 sekunder sedanThis looks like slop from a slop factory. "SEO", "Agent-readiness". That's precisely what a good website doesn't do (to paraphrase the homepage).
Oh yes, it's produced by a Wordpress "SEO" expert and private investor using Claude LLM. What a surprise. A man who built a fortune destroying the internet we loved with advertisement slop now working on destroying whatever's left with LLM slop.
- npc73x - 12729 sekunder sedanApart from this, we need standards in what features the website should have for it's domain. for example the hospital website should have a Doctors timings, portal to register and track the ticket, Address with google map link for it's branches, building's schematic for basic navigation, and track the registrations. the Glassy UI comes next before the basic features
- ItsABytecode - 31244 sekunder sedanSome of this is pretty good stuff, but I hope standardizing on a 128 item checklist doesn't discourage people from making websites
- sammy2255 - 11791 sekunder sedanIronic how this "Website spec" website doesn't have caching
- tanepiper - 16918 sekunder sedanI actually thought about this a couple of weeks back that for agents - going backwards actually makes sites more capable - WAP would even be more appropriate. The ultimate irony though is that making websites MORE accessible makes them more agent friendly - the last decade of SPAs is what makes things harder.
- - 18159 sekunder sedan
- WA - 35459 sekunder sedan.well-known/security is listed as a prominent example, but is not in the well-known category.
- baliex - 33994 sekunder sedanWhat a great resource. As someone who’s been making websites for 30 years, it’s amazing to still be picking up some of the basics. Though to be fair many of these didn’t exist back then.
I’ll be using this to add some extra tags to my pages.
It looks like there are some features noted as “required” that are actually required by the spec (e.g. a title tag), and others that are required by opinion (e.g. https) so there’s an element^ of pragmatic best practice being recommended.
I find it curious that setting a colour hint for the browser is recommended. I’m one for letting the browser look as vanilla as possible and letting my pages do the talking.
^Pun not intended, blink and you’ll miss it
- Dwedit - 10431 sekunder sedanI've seen Google Webmaster Tools misidentify a page as a "Soft 404" page before.
- andai - 8312 sekunder sedanWill this make my website good though?
- bag_boy - 12556 sekunder sedanWhy include the LLMs.txt?
- Nizoss - 20894 sekunder sedanGood resource and nicely organized. I took the opportunity to apply a couple new things.
- mschuster91 - 33820 sekunder sedanI heavily assume this is at least partially AI generated... but I have to admit, this is actually useful (aka, human driven). Nice work.
- incognitoninja - 34871 sekunder sedanThis seems good especially as beginner still face deep in the weeds of just the pure introductory functional concepts
- sinansaka - 35477 sekunder sedanThis is pretty cool, didnt even know of half the options under well-known urls. Thanks!
- Kwpolska - 32120 sekunder sedanLet’s look at the Git history: https://github.com/jdevalk/specification.website/commits/mai...
Yeah, mostly slop. I wonder why the slop slingers never disable Claude's self-attribution, and are too lazy to commit themselves, are they proud that they're delegating everything to a slop machine?
- franze - 34611 sekunder sedanllms.txt is supported by 0 of the relevant ai providers and must be seen as harmful
.. as the webmaster implemented something that they might thought has an impact (false sense of impact), but has zero
so net gain negative
i consider such lists harmful - a good website is one that supports the goal of the website providers and its desired users (some of these users might be bots)
a bad website is a website that does everything for everyone just because
- cbm-vic-20 - 34733 sekunder sedan
- tosti - 32208 sekunder sedanI haven't seen this much bullshit in a long time. Can we just run a webserver, write the html and whatnot and call it a day? It's not like a webdev didn't have anything to do already.
- todotask2 - 25885 sekunder sedanSome good parts, some bad practices, and a few missing pieces. I spent a lot of time auditing websites and brought all issues down to zero.
Many web and SEO agencies have let technical debt build up over the years. I raised some issues to them, but didn’t hear back.
After auditing a million websites, can we fix them? We could rebuild the web.
- pratikdeoghare - 32495 sekunder sedanHaving such a list is great. I am all for such lists.
BUT
Some people memorize these things. Take them too seriously. You are thought stupid if you don't know them. Somewhere someone then makes a story on Jira to verify that your product does all of these things and you have to convince them that we are fine without them or we don't need all of them etc.
- outageroom - 12364 sekunder sedan[flagged]
- - 29137 sekunder sedan
- vladsiu - 33671 sekunder sedan[dead]
- ai_fry_ur_brain - 21525 sekunder sedan[flagged]
- nimitlabs - 34607 sekunder sedanGreat!
- throwaw12 - 36074 sekunder sedanLooks interesting, can you convert it to a skill with bunch of scripts to validate those guidelines and use it to build the websites?
- knowmygpa - 30879 sekunder sedanThis would be a really great resource website in 2016.
But right now, when AI can just spit out everything you have on website faster and in a more personalized way then i dont think that people would wanna use this much.
Just my perspective, dont wanna be rude
- BubbleRings - 9050 sekunder sedanCool. I just dropped the following prompt on the Claude iPhone app and got a nice report out of it:
Look at the part of the website at my first link, that describes how to do an audit using their guidelines, then after that, run such an audit on my website at the second link.
https://specification.website/
Www.my-personal-squarespace-site-not-a-real-url.com
Nördnytt! 🤓