90. Combining components into templates
Module 18 · About 20 minutes · Lesson 89; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use combining components into templates, and how can you prove it?
- Explain combining components into templates 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 website template combines content regions, reusable components and a consistent style system. It must still have real links, meaningful headings and responsive behavior. Start from content requirements and avoid filling every region with decorative cards. The Build Studio lets you create multiple files, navigate internal pages and export the complete project with local assets.
Important source lines
- index.html:1 <header><nav aria-label="Primary"><a href="#main">Field Notes</a></nav></header><main id="main"><section class="hero"><h1>Useful design, clearly taught.</h1><p>Build small, test often.</p></section><section><h2>Featured lesson</h2><article class="card"><h3>Flexible layouts</h3><p>Learn by changing the code.</p></article></section></main><footer>Original learning template</footer>
- Introductory content for its page or section. Attribute guidance: global attributes.
- styles.css:1 body { font:18px/1.6 system-ui; margin:0; } header,main,footer { padding:1.5rem; max-width:70rem; margin-inline:auto; } .hero { padding-block:3rem; } .card { border:1px solid #abc; padding:1rem; }
- 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: Combining components into templates
Shared spacing and real semantic regions combine into a complete, readable page.
index.html
<header><nav aria-label="Primary"><a href="#main">Field Notes</a></nav></header><main id="main"><section class="hero"><h1>Useful design, clearly taught.</h1><p>Build small, test often.</p></section><section><h2>Featured lesson</h2><article class="card"><h3>Flexible layouts</h3><p>Learn by changing the code.</p></article></section></main><footer>Original learning template</footer>
styles.css
body { font:18px/1.6 system-ui; margin:0; } header,main,footer { padding:1.5rem; max-width:70rem; margin-inline:auto; } .hero { padding-block:3rem; } .card { border:1px solid #abc; padding:1rem; }script.js
Expected: Shared spacing and real semantic regions combine into a complete, readable page.
Edit and Render This ExampleExample 2: Property: max-width
Constrains the maximum width without requiring a fixed width.
index.html
<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>
styles.css
body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { max-width: 28rem; }script.js
Expected: Inspect .sample in the block context. Constrains the maximum width without requiring a fixed width. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.
Edit and Render This ExampleExample 3: Property: padding
Creates internal space between content and border.
index.html
<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>
styles.css
body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { padding: 24px; }script.js
Expected: Inspect .sample in the block context. Creates internal space between content and border. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.
Edit and Render This ExampleExample 4: Property: padding-block
Sets internal spacing on logical block edges.
index.html
<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>
styles.css
body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { padding-block: 16px; }script.js
Expected: Inspect .sample in the block context. Sets internal spacing on logical block edges. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.
Edit and Render This ExampleExample 5: Property: margin
Creates external separation; some block margins can collapse.
index.html
<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>
styles.css
body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { margin: 24px; }script.js
Expected: Inspect .sample in the block context. Creates external separation; some block margins can collapse. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.
Edit and Render This ExampleBuild and test
Shared spacing and real semantic regions combine into a complete, readable page. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<header><nav aria-label="Primary"><a href="#main">Field Notes</a></nav></header><main id="main"><section class="hero"><h1>Useful design, clearly taught.</h1><p>Build small, test often.</p></section><section><h2>Featured lesson</h2><article class="card"><h3>Flexible layouts</h3><p>Learn by changing the code.</p></article></section></main>
Starter styles.css
body { font:18px/1.6 system-ui; margin:0; } header,main,footer { padding:1.5rem; max-width:70rem; margin-inline:auto; } .hero { padding-block:3rem; } .card { border:1px solid #abc; padding:1rem; }Objective contract
[
{
"type": "count",
"selector": "footer",
"value": 1,
"label": "Include 1 matching footer 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 <footer>Original learning template</footer>. The exercise instead uses an omitted operation. Identify its effect before changing it.
Hint 3
Restore the intended <footer>Original learning template</footer> operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<header><nav aria-label="Primary"><a href="#main">Field Notes</a></nav></header><main id="main"><section class="hero"><h1>Useful design, clearly taught.</h1><p>Build small, test often.</p></section><section><h2>Featured lesson</h2><article class="card"><h3>Flexible layouts</h3><p>Learn by changing the code.</p></article></section></main><footer>Original learning template</footer>
styles.css
body { font:18px/1.6 system-ui; margin:0; } header,main,footer { padding:1.5rem; max-width:70rem; margin-inline:auto; } .hero { padding-block:3rem; } .card { border:1px solid #abc; padding:1rem; }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. Shared spacing and real semantic regions combine into a complete, readable page.
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.
Continue to Lesson 91: Browser developer tools and inspection