
AGENTS.md, ACCESSIBILITY.md but also A11Y.md, DESIGN.md—as well as taste.md. Following this trend of...
AGENTS.md, ACCESSIBILITY.md but also A11Y.md, DESIGN.md—as well as taste.md.
Following this trend of specialized specification files, here is a draft for HTML.md (gist)—foundational instructions you need for writing HTML, geared towards both humans and machines (if only to improve parsing and save tokens).
* Use the elements most appropriate semantically.
* Use as little HTML as possible.
* Validate all HTML output against an HTML validator (preferably the W3C one), and fix any errors.
That’s it.
Is this a joke?
No: While these instructions are opinionated insofar as they reflect a school of minimal web development honoring the first rule of ARIA and suggesting no use of optional markup, they acknowledge the reality that the HTML code on most websites often isn’t using the right elements for the job (e.g., divitis) and that it’s essentially never error-free (i.e., commonly invalid). Note, then, that this guidance intentionally doesn’t handle “everything,” like accessibility, performance, and search optimization, but the foundation.
Although we can memorize the three instructions, it is useful to document them in writing.
Whether that’s actually in form of an “HTML.md,” however, that’s everyone’s individual call. So this is not a serious request for this particular file convention—but one for us to pay more attention to HTML quality.
aiMost of us have seen a coding agent fail to complete a task we know it can do. We just don't...
googlecloudWhen building Generative AI applications, developers often encounter a massive bottleneck: sequential...
discussI’ve been thinking about sharing some electronic circuit posts on Dev.to — small circuits, DIY...
agentsWhat nobody tells you about exporting your multi-agent prototype to a local workspace. Every...
agenticarchitectAutonomous agents are genuinely good at answering messy business questions. Give one an LLM and a set...
aiPR volume went up, ticket quality didn't, and the gap got filled with LLMs on both sides of the review: bots reviewing, bots replying, bots occasionally arguing with bots about priorities that only existed in a teammate's head. Our CEO named the actual problem, and it's bigger than code review.
Workflows from the Neura Market marketplace related to this Stable Diffusion resource