3. Source code and HTML elements
Module 1 · About 20 minutes · Lesson 2; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use source code and html elements, and how can you prove it?
- Explain source code and html elements 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
Source code is the text you author, while the DOM is the tree the browser constructs from it. Browsers repair some invalid markup, so the resulting tree can differ from the typed source. Elements can contain text and permitted child elements. strong communicates importance and em communicates emphasis; choosing them solely for bold or italic appearance loses the meaning. Inspect the document tree after a change rather than assuming indentation defines nesting.
Important source lines
- index.html:1 <p>Read <strong>important instructions</strong> before you <em>publish</em>.</p>
- A paragraph of prose. 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: Source code and HTML elements
The important phrase is a child of the paragraph and has explicit importance semantics.
index.html
<p>Read <strong>important instructions</strong> before you <em>publish</em>.</p>
styles.css
script.js
Expected: The important phrase is a child of the paragraph and has explicit importance semantics.
Edit and Render This ExampleExample 2: Element: strong
Strong importance rather than merely bold appearance.
index.html
<p><strong>Important:</strong> keep a recovery copy before replacing files.</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: Strong importance rather than merely bold appearance. 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 important phrase is a child of the paragraph and has explicit importance semantics. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<p>Read important instructions before you <em>publish</em>.</p>
Starter styles.css
Objective contract
[
{
"type": "count",
"selector": "p strong",
"value": 1,
"label": "Include 1 matching p strong 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 <strong>important instructions</strong>. The exercise instead uses important instructions. Identify its effect before changing it.
Hint 3
Restore the intended <strong>important instructions</strong> operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<p>Read <strong>important instructions</strong> before you <em>publish</em>.</p>
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 important phrase is a child of the paragraph and has explicit importance semantics.
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.