17. Nested lists
Module 4 · About 20 minutes · Lesson 16; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use nested lists, and how can you prove it?
- Explain nested lists 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
A nested list belongs inside an li that owns the subitems. Putting it as a direct sibling between list items breaks the intended relationship. Indentation in source helps humans see depth, but DOM parentage defines the structure. Keep navigation hierarchies shallow enough to understand and give groups meaningful text labels.
Important source lines
- index.html:1 <ul><li>Website files<ul><li>index.html</li><li>styles.css</li></ul></li><li>Publishing checklist</li></ul>
- An unordered list of peer items. Attribute guidance: global attributes.
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: Nested lists
The two files form a sublist owned by the Website files item.
index.html
<ul><li>Website files<ul><li>index.html</li><li>styles.css</li></ul></li><li>Publishing checklist</li></ul>
styles.css
script.js
Expected: The two files form a sublist owned by the Website files item.
Edit and Render This ExampleExample 2: Element: ul
An unordered list of peer items.
index.html
<ul><li>HTML</li><li>CSS</li><li>Testing</li></ul>
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: An unordered list of peer items. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleExample 3: Element: li
One list item inside a supported list container.
index.html
<ul><li>A parent topic<ul><li>A nested detail</li></ul></li></ul>
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: One list item inside a supported list container. 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 two files form a sublist owned by the Website files item. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<ul><li>Website files<span>index.html, styles.css</span></li><li>Publishing checklist</li></ul>
Starter styles.css
Objective contract
[
{
"type": "count",
"selector": "li > ul",
"value": 1,
"label": "Include 1 matching li > ul 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 <ul><li>index.html</li><li>styles.css</li></ul>. The exercise instead uses <span>index.html, styles.css</span>. Identify its effect before changing it.
Hint 3
Restore the intended <ul><li>index.html</li><li>styles.css</li></ul> operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<ul><li>Website files<ul><li>index.html</li><li>styles.css</li></ul></li><li>Publishing checklist</li></ul>
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 two files form a sublist owned by the Website files item.
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.