13. Relative and absolute paths
Module 3 · About 20 minutes · Lesson 12; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use relative and absolute paths, and how can you prove it?
- Explain relative and absolute paths 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
An absolute URL includes a scheme and host; a relative path is resolved from the current document’s directory. A leading slash starts at the site root, not the current folder. File names are often case-sensitive after upload. In the Build Studio, project page links resolve against the active virtual file. Exported folders preserve the same relationship. Review internal links after renaming a page.
Important source lines
- index.html:1 <h1>Path examples</h1>
- The highest-level heading for a page topic. Attribute guidance: global attributes.
- index.html:2 <a href="about.html">About this project</a>
- A hyperlink with a meaningful destination and link text. Attribute guidance: href; rel/target when relevant.
- index.html:3 <a href="https://developer.mozilla.org/">MDN documentation</a>
- A hyperlink with a meaningful destination and link text. Attribute guidance: href; rel/target when relevant.
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: Relative and absolute paths
The first URL is a sibling file; the second is an absolute external destination.
index.html
<h1>Path examples</h1> <a href="about.html">About this project</a> <a href="https://developer.mozilla.org/">MDN documentation</a>
styles.css
script.js
Expected: The first URL is a sibling file; the second is an absolute external destination.
Edit and Render This ExampleExample 2: Element: a
A hyperlink with a meaningful destination and link text.
index.html
<a href="#destination">Read the destination</a><section id="destination"><h1>Destination</h1></section>
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 hyperlink with a meaningful destination and link text. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleExample 3: 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 4: 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 ExampleExample 5: 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 ExampleBuild and test
The first URL is a sibling file; the second is an absolute external destination. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<h1>Path examples</h1> <a href="About.HTML">About this project</a> <a href="https://developer.mozilla.org/">MDN documentation</a>
Starter styles.css
Objective contract
[
{
"type": "attr",
"selector": "a",
"property": "href",
"value": "about.html",
"label": "a has href=about.html"
}
]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 href="about.html". The exercise instead uses href="About.HTML". Identify its effect before changing it.
Hint 3
Restore the intended href="about.html" operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<h1>Path examples</h1> <a href="about.html">About this project</a> <a href="https://developer.mozilla.org/">MDN documentation</a>
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 first URL is a sibling file; the second is an absolute external destination.
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.