6. Doctype and document structure
Module 2 · About 20 minutes · Lesson 5; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use doctype and document structure, and how can you prove it?
- Explain doctype and document structure using the example source
- Predict the visual or structural effect of one controlled change
- Repair the supplied fault and verify actual output
Predict
Record the expected structure or visual change before rendering. Name one thing that should remain unchanged.
Understand
The HTML doctype requests standards-mode rendering. It is not an HTML element and has no closing tag. A document should have one html root with head and body children. Whitespace and indentation help humans but do not create semantic sections. The academy can wrap fragments for convenience; use a complete document when practicing document structure or exporting pages.
Important source lines
- index.html:1 <!doctype html>
- This line groups or completes the surrounding structure. Inspect its actual parent/child relationship and compare with the lesson explanation.
- index.html:2 <html lang="en">
- The root of an HTML document, with its content language. Attribute guidance: lang="en".
- index.html:3 <head><title>Document structure</title></head>
- The metadata container rather than visible page content. Attribute guidance: none required.
- index.html:4 <body><main><h1>A complete document</h1></main></body>
- The visible and interactive document content. Attribute guidance: global attributes.
- index.html:5 </html>
- This line groups or completes the surrounding structure. Inspect its actual parent/child relationship and compare with the lesson explanation.
The first example teaches this lesson’s primary contract. Additional examples are optional related references or applications, each with its own purpose and source; an example without an authored check requires the stated visual/manual review.
Example 1: Doctype and document structure
A main landmark contains the page heading; the doctype requests standards mode.
index.html
<!doctype html> <html lang="en"> <head><title>Document structure</title></head> <body><main><h1>A complete document</h1></main></body> </html>
styles.css
script.js
Expected: A main landmark contains the page heading; the doctype requests standards mode.
Edit and Render This ExampleExample 2: Element: title
The document title used in browser UI and navigation.
index.html
<!doctype html><html lang="en"><head><title>Specific page — Field Notes</title></head><body><h1>A title is not a body heading</h1></body></html>
styles.css
body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }script.js
Expected: The document title used in browser UI and navigation. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleExample 3: Element: h1
The highest-level heading for a page topic.
index.html
<h1>Workshop handbook</h1><p>A principal heading introduces the page.</p>
styles.css
body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }script.js
Expected: The highest-level heading for a page topic. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleExample 4: Element: p
A paragraph of prose.
index.html
<p>One idea belongs in a coherent paragraph.</p><p>A second paragraph develops another idea.</p>
styles.css
body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }script.js
Expected: A paragraph of prose. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleExample 5: Element: strong
Strong importance rather than merely bold appearance.
index.html
<p><strong>Important:</strong> keep a recovery copy before replacing files.</p>
styles.css
body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }script.js
Expected: Strong importance rather than merely bold appearance. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleBuild and test
A main landmark contains the page heading; the doctype requests standards mode. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<!doctype html> <html lang="en"> <head><title>Document structure</title></head> <body><div>A complete document</div></body> </html>
Starter styles.css
Objective contract
[
{
"type": "count",
"selector": "main h1",
"value": 1,
"label": "Include 1 matching main h1 element(s)"
}
]Hint 1
Locate the first difference between the intended result and the real preview. Inspect matching elements and computed styles.
Hint 2
The relevant source uses <main><h1>A complete document</h1></main>. The exercise instead uses <div>A complete document</div>. Identify its effect before changing it.
Hint 3
Restore the intended <main><h1>A complete document</h1></main> operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<!doctype html> <html lang="en"> <head><title>Document structure</title></head> <body><main><h1>A complete document</h1></main></body> </html>
styles.css
Explain, reflect and extend
Which part of the actual preview or inspector proves this result? Explain one boundary case and name what automated checks do not verify.
Apply this concept to a different realistic piece of content. Predict its structure or visual behavior, test narrow and wide widths where relevant, then record one invalid case and its repair.
Troubleshooting and professional practice
If nothing changes, confirm that you edited the active file and ran Run Preview, or enabled Auto Preview. Inspect the actual DOM because the browser may repair invalid nesting. For CSS, check selector matches, valid declarations, active queries and computed values. Preserve local asset paths and inspect warnings. A main landmark contains the page heading; the doctype requests standards mode.
Knowledge check
Explain why the stated result follows from the source. Predict a second input or width and test it independently. Automated contracts and written explanations are reviewed separately.
Optional AI prompts
- Explain this lesson’s source line by line using the actual objective above.
- Help implement one small extension and define normal, boundary and failure tests.
- Review/debug the source against actual preview observations; verify standards and never claim rendering without evidence.