10. Attributes, comments and nesting
Module 2 · About 20 minutes · Lesson 9; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use attributes, comments and nesting, and how can you prove it?
- Explain attributes, comments and nesting 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
Attributes add information to an opening tag, such as an identifier or language. Attribute values should be quoted consistently. id values identify a unique element and can be used by links and selectors. Comments explain intent to future authors but are not visible content. Nest children inside a permitted parent and close them in reverse order. The DOM tree is the final evidence of how the browser interpreted your nesting.
Important source lines
- index.html:1 <!-- The introduction is a link target. -->
- This line groups or completes the surrounding structure. Inspect its actual parent/child relationship and compare with the lesson explanation.
- index.html:2 <section id="intro"><h1>Introduction</h1><p>Start with <em>one</em> change.</p></section>
- A thematic grouping, usually identified by a heading. Attribute guidance: aria-labelledby optional for an explicitly named region.
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: Attributes, comments and nesting
The section has a stable link target and contains the heading and paragraph as children.
index.html
<!-- The introduction is a link target. --> <section id="intro"><h1>Introduction</h1><p>Start with <em>one</em> change.</p></section>
styles.css
script.js
Expected: The section has a stable link target and contains the heading and paragraph as children.
Edit and Render This ExampleExample 2: Element: section
A thematic grouping, usually identified by a heading.
index.html
<section aria-labelledby="outcomes"><h2 id="outcomes">Learning outcomes</h2><p>Build and explain a page.</p></section>
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 thematic grouping, usually identified by a heading. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleExample 3: Element: em
Stress emphasis within prose.
index.html
<p>Change <em>one</em> property before comparing.</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: Stress emphasis within prose. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleExample 4: 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 5: 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 ExampleBuild and test
The section has a stable link target and contains the heading and paragraph as children. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<!-- The introduction is a link target. --> <section id="wrong"><h1>Introduction</h1><p>Start with <em>one</em> change.</p></section>
Starter styles.css
Objective contract
[
{
"type": "attr",
"selector": "section",
"property": "id",
"value": "intro",
"label": "section has id=intro"
}
]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 id="intro". The exercise instead uses id="wrong". Identify its effect before changing it.
Hint 3
Restore the intended id="intro" operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<!-- The introduction is a link target. --> <section id="intro"><h1>Introduction</h1><p>Start with <em>one</em> change.</p></section>
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. The section has a stable link target and contains the heading and paragraph as children.
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.