Capstone builds · Lesson 2 of 8 · 7 minutes

Capstone builds: Event landing page

An event page should answer what, when, and where before asking someone to take action.

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 event landing page
Build this first target: <main>; <h1> inside <main> containing “Library Linux workshop”; <p> inside <main> containing “Practice your first commands.”. Inspect the structure before checking the lesson.
Hint & worked example
An event page should answer what, when, and where before asking someone to take action.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<main><h1>Library Linux workshop</h1><p>Practice your first commands.</p></main>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the event landing page example
Extend your file to include: <main>; <h1> inside <main> containing “Library Linux workshop”; <p> inside <main> containing “Practice your first commands.”; <time> inside <main> (datetime="2026-09-12") containing “September 12”; <p> inside <main> containing “Library Room 2.”. Inspect the structure before checking the lesson.
Hint & worked example
An event page should answer what, when, and where before asking someone to take action.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<main><h1>Library Linux workshop</h1><p>Practice your first commands.</p><time datetime="2026-09-12">September 12</time><p>Library Room 2.</p></main>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete event landing page pattern
Finish the pattern with: <main>; <h1> inside <main> containing “Library Linux workshop”; <p> inside <main> containing “Practice your first commands.”; <time> inside <main> (datetime="2026-09-12") containing “September 12”; <p> inside <main> containing “Library Room 2.”; <a> inside <main> (href="/signup/") containing “Review workshop signup”. Inspect the structure before checking the lesson.
Hint & worked example
An event page should answer what, when, and where before asking someone to take action.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<main><h1>Library Linux workshop</h1><p>Practice your first commands.</p><time datetime="2026-09-12">September 12</time><p>Library Room 2.</p><a href="/signup/">Review workshop signup</a></main>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

An event page should answer what, when, and where before asking someone to take action.

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

<main><h1>Library Linux workshop</h1><p>Practice your first commands.</p><time datetime="2026-09-12">September 12</time><p>Library Room 2.</p><a href="/signup/">Review workshop signup</a></main>

An event page should answer what, when, and where before asking someone to take action.

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 event landing page?An event page should answer what, when, and where before asking someone to take action.A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Capstone builds: Accessible signup flow 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