Show HN: HTML for People

Original Article ↗ Hacker News Discussion ↗

A new site, “HTML for People,” aims to teach anyone to build a simple website using just a plain-text editor and basic HTML, avoiding the modern tangle of frameworks, build tools, and heavy JavaScript. Commenters praise its gentle, deployment-first approach as far more approachable than MDN-style docs for non-professionals, but note it still assumes skills—like understanding files and folders—that many everyday computer and mobile users now lack. The exchange surfaces deeper questions about whether ordinary people should learn raw HTML at all versus using WYSIWYG tools or AI generators, and how much technical literacy is reasonable to expect in order to publish on the open web.

Overall reception

  • Many commenters praise the project as an approachable, humane intro to HTML, especially for non‑professionals and complete beginners.
  • Several see it as aligned with the original, open, “small web” ethos and as a counterweight to complex JS-heavy stacks and corporate platforms.
  • Some plan to use it in teaching (high school classes, spouses, non‑technical friends) or as a “next step” after simple blogging/CMS tools.

Teaching approach & scope

  • Strong approval for starting with:
    • plain text editors (Notepad/TextEdit),
    • a single index.html,
    • immediate deployment (e.g., Neocities),
    • then gradually adding structure and better tools.
  • Many like the decision to lean on a simple external CSS (simplecss.org) instead of teaching full CSS early.
  • Some argue sandboxes (online editors) are better than local files for reducing friction and “small mistakes,” others insist basic file handling is an essential skill.
  • Debate on whether to add more CSS, templates, or keep the focus tightly on HTML.

HTML semantics & minimal documents

  • Discussion about what constitutes a “proper” HTML5 document:
    • <!DOCTYPE html> is required to avoid quirks mode.
    • Only doctype and a non-empty <title> are strictly necessary; <html>, <head>, <body> are optional.
    • Many tags can be left unclosed and still be valid HTML5; some dislike treating HTML like XHTML.
  • Some advocate for semantic structure (sections, header/main/footer, avoiding “sea of divs”) and minimal/no JS.

Accessibility, defaults, and styling

  • Some lament that browser default styles are unattractive; speculate that nicer defaults might have encouraged more plain-HTML sites.
  • Mentions of CSS resets and tiny baseline styles to improve readability (margins, line-height, fonts).
  • One accessibility-oriented critique of another popular tutorial (low text contrast) used as a contrast to this site’s clarity.

Computer literacy & filesystem issues

  • Repeated concern: many modern users, especially younger/mobile-first ones, struggle with files, folders, downloads, and encodings.
  • Some think this is a serious barrier to following “create a folder and a file” instructions; others find this overblown or a symptom of weak education.
  • Suggestions include linking to basic OS/file tutorials or short YouTube primers.

Meta: who HTML is “for”

  • Strong agreement that HTML should be for “everyone who wants it,” not just professionals.
  • Counterpoint: most people neither need nor want markup; WYSIWYG and higher-level tools are better for them.
  • Some argue LLM/code tools now reduce the incentive to learn HTML; others still see lasting value in understanding the basics.