Capstone builds · Lesson 7 of 8 · 7 minutes

Capstone builds: Portfolio case study

A case study explains the problem, the work, and the evidence for the result without inventing impact metrics.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

Current edit

PreviewNo external resources

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Build portfolio case study
Build this first target: <article>; <h1> inside <article> containing “Making logs easier to inspect”; <section> inside <article>; <h2> inside <section> containing “Problem”; <p> inside <section> containing “Failures were buried in noisy output.”. Inspect the structure before checking the lesson.
Hint & worked example
A case study explains the problem, the work, and the evidence for the result without inventing impact metrics.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<article><h1>Making logs easier to inspect</h1><section><h2>Problem</h2><p>Failures were buried in noisy output.</p></section></article>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the portfolio case study example
Extend your file to include: <article>; <h1> inside <article> containing “Making logs easier to inspect”; <section> inside <article>; <h2> inside <section> containing “Problem”; <p> inside <section> containing “Failures were buried in noisy output.”; <section> inside <article>; <h2> inside <section> containing “Approach”; <p> inside <section> containing “Filter the time window and retain the original log.”. Inspect the structure before checking the lesson.
Hint & worked example
A case study explains the problem, the work, and the evidence for the result without inventing impact metrics.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<article><h1>Making logs easier to inspect</h1><section><h2>Problem</h2><p>Failures were buried in noisy output.</p></section><section><h2>Approach</h2><p>Filter the time window and retain the original log.</p></section></article>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete portfolio case study pattern
Finish the pattern with: <article>; <h1> inside <article> containing “Making logs easier to inspect”; <section> inside <article>; <h2> inside <section> containing “Problem”; <p> inside <section> containing “Failures were buried in noisy output.”; <section> inside <article>; <h2> inside <section> containing “Approach”; <p> inside <section> containing “Filter the time window and retain the original log.”; <section> inside <article>; <h2> inside <section> containing “Evidence”; <p> inside <section> containing “The fixture replay identifies all three expected failures.”. Inspect the structure before checking the lesson.
Hint & worked example
A case study explains the problem, the work, and the evidence for the result without inventing impact metrics.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<article><h1>Making logs easier to inspect</h1><section><h2>Problem</h2><p>Failures were buried in noisy output.</p></section><section><h2>Approach</h2><p>Filter the time window and retain the original log.</p></section><section><h2>Evidence</h2><p>The fixture replay identifies all three expected failures.</p></section></article>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

A case study explains the problem, the work, and the evidence for the result without inventing impact metrics.

Misconceptions to reject

A visual appearance alone guarantees the intended HTML meaning.
Replacing semantic elements with generic divs automatically improves accessibility.

The preview is a sanitized subset, not a full browser compatibility test.

Worked example and expected result

<article><h1>Making logs easier to inspect</h1><section><h2>Problem</h2><p>Failures were buried in noisy output.</p></section><section><h2>Approach</h2><p>Filter the time window and retain the original log.</p></section><section><h2>Evidence</h2><p>The fixture replay identifies all three expected failures.</p></section></article>

A case study explains the problem, the work, and the evidence for the result without inventing impact metrics.

Try a variation

Adapt the final example to a different project name while retaining its structure and relationships. A different context still needs a real browser and accessibility check.

Explain it

Which statement correctly explains portfolio case study?Replacing semantic elements with generic divs automatically improves accessibility.A case study explains the problem, the work, and the evidence for the result without inventing impact metrics.A visual appearance alone guarantees the intended HTML meaning.

Apply it elsewhere

You reuse portfolio case study in a different project. What must still be verified?The meaning, relationships, and accessible names in the new document.Nothing; passing a single exercise guarantees every future use.Only whether the source code has the same number of lines.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Capstone builds: Web foundations finale Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

MDN: HTML structure