99. Testing and preparing publication
Module 20 · About 20 minutes · Lesson 98; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use testing and preparing publication, and how can you prove it?
- Explain testing and preparing publication 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 release review includes internal links, image alternatives, labels, heading order, keyboard focus, responsive overflow, content accuracy and exported assets. Automated checks cover only their explicit contracts. Test the downloaded site independently and verify the uploaded server paths, HTTPS and cache behavior. Keep a previous working version for recovery.
Important source lines
- index.html:1 <main><h1>Publication checklist</h1><ul><li>Check all page links.</li><li>Review accessibility manually.</li><li>Test narrow and wide layouts.</li><li>Keep a recovery copy.</li></ul></main>
- The document’s principal content, normally one visible instance. Attribute guidance: id useful for skip links.
- styles.css:1 main { max-width:60ch; margin-inline:auto; padding:1rem; }
- Constrains the maximum width without requiring a fixed width. Accepted grammar: none | <length-percentage [0,∞]> | min-content | max-content | fit-content | fit-content(<length-percentage [0,∞]>) | <calc-size()> | <anchor-size()>. Context: block.
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: Testing and preparing publication
The checklist includes recovery as well as appearance and technical checks.
index.html
<main><h1>Publication checklist</h1><ul><li>Check all page links.</li><li>Review accessibility manually.</li><li>Test narrow and wide layouts.</li><li>Keep a recovery copy.</li></ul></main>
styles.css
main { max-width:60ch; margin-inline:auto; padding:1rem; }script.js
Expected: The checklist includes recovery as well as appearance and technical checks.
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: margin-inline
Can center an appropriately sized block along the inline axis.
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-inline: auto; }script.js
Expected: Inspect .sample in the block context. Can center an appropriately sized block along the inline axis. 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: Volume slider
Range inputs provide keyboard steps and a constrained numeric value. Use input for continuous feedback.
index.html
<section data-component aria-label="Volume slider"> <label>Volume <input id="volume" type="range" min="0" max="100" value="30"></label><output id="value" for="volume">30%</output> </section>
styles.css
* { box-sizing: border-box; }
body { margin: 0; color: #142537; background: #eef4fa; font: 16px/1.5 system-ui, sans-serif; }
[data-component] { max-width: 44rem; margin: 1rem auto; padding: 1rem; border: 1px solid #a1b2c4; border-radius: .75rem; background: white; }
button, input, select, textarea { font: inherit; padding: .4rem .65rem; margin: .2rem; }
button { cursor: pointer; } :focus-visible { outline: 3px solid #a33e0c; outline-offset: 3px; }
label { display: block; } [hidden] { display: none !important; }
table { border-collapse: collapse; } th, td { padding: .4rem; border-bottom: 1px solid #a1b2c4; }
script.js
const root=document.querySelector("[data-component]");
root.querySelector('#volume').oninput=e=>{root.querySelector('#value').textContent=e.target.value+'%';};Expected: Use step=5 and verify the announced value.
Edit and Render This ExampleBuild and test
The checklist includes recovery as well as appearance and technical checks. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<main><h1>Publication checklist</h1><ul><li>Check all page links.</li><li>Review accessibility manually.</li><li>Test narrow and wide layouts.</li></ul></main>
Starter styles.css
main { max-width:60ch; margin-inline:auto; padding:1rem; }Objective contract
[
{
"type": "count",
"selector": "ul li",
"value": 4,
"label": "Include 4 matching ul li 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 <li>Keep a recovery copy.</li>. The exercise instead uses an omitted operation. Identify its effect before changing it.
Hint 3
Restore the intended <li>Keep a recovery copy.</li> operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<main><h1>Publication checklist</h1><ul><li>Check all page links.</li><li>Review accessibility manually.</li><li>Test narrow and wide layouts.</li><li>Keep a recovery copy.</li></ul></main>
styles.css
main { max-width:60ch; margin-inline:auto; 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. The checklist includes recovery as well as appearance and technical checks.
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 100: Publishing and presenting your website capstone