HTML Resources and Book Recommendations
Introduction
You have built pages, forms, semantic layouts, and small sites. The HTML track on this site covers daily practice; books and official references add depth when you need specification details, design pairing, or accessibility expertise. This chapter points you to the best next resources and how they fit with other hello_code tutorials.
Prerequisites
- Most chapters in this HTML track, or equivalent hands-on practice
- At least one completed project from chapters 31–35
How to Study After This Track
- Keep MDN HTML open while coding.
- Validate important pages with the W3C validator.
- Test keyboard navigation and Lighthouse on real projects.
- Learn CSS next for layout and visual design.
- Learn JavaScript for interactivity and DOM updates.
HTML is the foundation. Most production web work uses all three.
Tip
Build, Do Not Only Read
For each resource section you read, change one page you already built. Reading without typing fades quickly.
Official Documentation (Free)
| Resource | Best for |
|---|---|
| MDN HTML element reference | Day-to-day tag lookup |
| MDN Learn HTML | Structured tutorials |
| WHATWG HTML Living Standard | Authoritative spec when MDN is unclear |
| W3C Markup Validation Service | Finding invalid markup |
| WebAIM | Accessibility articles and checklists |
| Can I use | Browser support for newer elements |
Bookmark MDN first. Use the living standard when you need precise parsing rules.
Recommended Books
HTML and CSS: Design and Build Websites — Jon Duckett
Why read it:
- Visual, beginner-friendly layout
- Pairs structure (HTML) with presentation (CSS)
- Good if you learn better from print design than long spec text
Best for:
- Right after this track, before or alongside your first CSS chapter
Learning Web Design — Jennifer Niederst Robbins
Why read it:
- Broader web design fundamentals
- Covers HTML, CSS, graphics, and workflow
- Strong for self-directed learners building a portfolio
Best for:
- Students who want one book that spans the whole front-end basics
Inclusive Design Patterns — Heydon Pickering
Why read it:
- Practical accessibility and semantic patterns
- Goes beyond checkbox audits into real component design
Best for:
- After chapters 18–22 and project work; when you care about inclusive UI
Don't Make Me Think — Steve Krug (UX, not HTML-only)
Why read it:
- Teaches how users scan pages and what makes navigation obvious
- Helps you write better headings, links, and page structure
Best for:
- Complementing landing page and multi-page site projects
Pairing with Other hello_code Tracks
| Your goal | Read next on hello_code |
|---|---|
| Style pages | CSS track (when published) or MDN CSS |
| Interactivity | JavaScript introduction |
| Deploy on a VPS | Linux, Nginx |
| Backend forms | Server-side language track + JDBC if using databases |
| Build tools | Maven or Gradle for Java projects |
HTML stays relevant even when frameworks generate markup—you still debug output, accessibility, and SEO metadata.
Four-Week Follow-Up Plan
Week 1
- Re-read Semantic HTML layout and refactor one old page
- MDN: forms and tables sections
- Run W3C validator on all project pages
Week 2
- Start CSS: layout (box model, flexbox intro on MDN)
- Add external stylesheet to chapter 35 site
- Keep semantic HTML; move presentation to CSS
Week 3
- Start JavaScript: DOM selection and events
- Replace one
onclick-style pattern withaddEventListener - Read DOM manipulation
Week 4
- Deploy site to a static host (chapter 37)
- Add Open Graph tags to one article page
- Write a short post-mortem: what you would improve
Topics to Explore Later
| Topic | Why |
|---|---|
| CSS Grid and Flexbox | Page layout |
| Responsive design | Mobile-first CSS |
| Static site generators | Less copy-paste across pages |
| Web components | Reusable custom elements |
| Frameworks (React, Vue, etc.) | Large app UIs—still output HTML |
| HTTP/2 and CDN | Production performance |
| CSP and security headers | Hardening live sites |
You do not need all of these immediately. Go deep on CSS and accessibility before chasing frameworks.
FAQ
Is the HTML living standard too hard to read?
For daily work, use MDN. Use the spec when you need exact rules (parsing, void elements, obscure attributes).
One book or docs only?
Docs-only is enough for many developers. A book helps if you want a guided narrative and exercises.
Should I learn HTML5 separately?
Modern tutorials teach HTML5 by default. There is no separate "HTML5 course" needed beyond living-standard features as they appear.