Every page on the web is HTML at the end of the pipeline. Frameworks come and go; HTML is the contract they all compile to. Non-negotiable knowledge.
The problem it solves
HTML provides the universal structure and meaning of web content, making pages readable by browsers, search engines, and assistive technologies while enabling responsive mobile layouts.
Where it came from
Created at CERN as a simple markup for sharing physics documents. Standardized through browser wars, nearly replaced by XHTML, then reborn as the living HTML5 standard.
1991: Tim Berners-Lee published the first HTML tag set for linked documents.
1995: HTML 2.0 became the first formal standard.
1997: HTML 4.x emphasized separation of structure from presentation (with CSS).
2014: HTML5 became a major milestone with semantic elements and rich media support.
Now: WHATWG maintains HTML as a Living Standard with ongoing incremental improvements.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
Build a page using only semantic tags (no divs).
Make an accessible form with labels & fieldsets.
Explain the difference between <section>, <article>, <aside>.
Hand-write a valid document with meta tags for SEO/social.
Audit a real site's markup with a11y devtools and fix 5 issues.
More ways to practice
Level 1
5-Minute Semantic Upgrade
Replace a `div`-only page with `header`, `main`, `section`, and `footer`. Keep it to one phone screen.
Level 2
Accessible Image Card
Build a card with an image, heading, short text, and link. Use meaningful `alt` text and logical heading order.
Level 3
Mobile Form Essentials
Create a sign-up form using `label` + matching `id`, proper input types (`email`, `tel`), and `required` fields.
Level 4
Daily Reflection Snippet
Write a short journal entry using semantic text tags (`article`, `time`, `p`) and validate the HTML.
Level 5
Mini Landing Page Skeleton
Create a fast-loading page skeleton with viewport meta, semantic landmarks, and lazy-loaded image placeholders.
Illustrative business scenario · AI-generated from linked documentation · Not a measured customer case study
Archival Document Skeleton Standardization
A historical society digitizing paper records for public web access.
The business problem
Inconsistent document structures across digitized files prevent search engines from indexing content correctly, leading to poor discoverability.
How this topic solves it
Implementing a standardized HTML document skeleton ensures that metadata, headers, and content sections are semantically defined, allowing crawlers to parse the archival records accurately.
Define the root document structure using the standard HTML skeleton.
Insert metadata within the head element to describe the archival record.
Use semantic elements like header, article, and footer to organize the digitized text.
Apply links to connect related historical documents.
Validate the markup to ensure compliance with web standards.
Archival Document Parsing Flow · Process flow
The flow shows how raw data is transformed into a structured HTML document for web consumption.
Raw Text
Unstructured digitized archival data
HTML Skeleton
Standardized tags like head and body
Semantic Markup
Using article and header for content
Search Engine
External crawler indexing the content
Raw Text → wraps → HTML Skeleton
HTML Skeleton → organizes → Semantic Markup
Semantic Markup → exposes → Search Engine
Expected business outcome
Improved search engine visibility and consistent rendering of historical documents across all user devices.
Limitations and checks
HTML defines structure but not visual presentation; checking for visual consistency requires external CSS validation.