100. Publishing and presenting your website capstone
Module 20 · About 20 minutes · Lesson 99; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use publishing and presenting your website capstone, and how can you prove it?
- Explain publishing and presenting your website capstone 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
Publishing places the actual HTML, CSS, scripts and assets on a web server. index.html is commonly the default document in a directory, while relative paths depend on the uploaded folder structure. SFTP transfers files through an encrypted connection; use the hosting provider’s instructions. Demonstrate the finished site with a real task, one deliberate failure and an explanation of the repair. Record browser and accessibility tests honestly rather than assuming a local preview proves production quality.
Important source lines
- index.html:1 <header><a href="#work">Alex’s portfolio</a></header><main><h1>A website I can explain</h1><section id="work"><h2>Selected work</h2><p>Original projects with tested source.</p></section><section><h2>Verification</h2><p>Responsive, keyboard and content review documented.</p></section></main><footer>Built for learning and sharing.</footer>
- Introductory content for its page or section. Attribute guidance: global attributes.
- styles.css:1 body { font:18px/1.6 system-ui; margin:0; color:#172f54; } header,main,footer { max-width:70rem; margin-inline:auto; padding:1.5rem; } section { margin-block:2rem; }
- This line groups or completes the surrounding structure. Inspect its actual parent/child relationship and compare with the lesson explanation.
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: Publishing and presenting your website capstone
The portfolio has a working internal destination, readable structure and a documented verification story.
index.html
<header><a href="#work">Alex’s portfolio</a></header><main><h1>A website I can explain</h1><section id="work"><h2>Selected work</h2><p>Original projects with tested source.</p></section><section><h2>Verification</h2><p>Responsive, keyboard and content review documented.</p></section></main><footer>Built for learning and sharing.</footer>
styles.css
body { font:18px/1.6 system-ui; margin:0; color:#172f54; } header,main,footer { max-width:70rem; margin-inline:auto; padding:1.5rem; } section { margin-block:2rem; }script.js
Expected: The portfolio has a working internal destination, readable structure and a documented verification story.
Edit and Render This ExampleExample 2: Property: color
Sets the foreground text color; contrast depends on the actual background.
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 { color: #17324d; }script.js
Expected: Inspect .sample in the block context. Sets the foreground text color; contrast depends on the actual background. 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: 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 4: 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 5: Property: margin
Creates external separation; some block margins can collapse.
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: 24px; }script.js
Expected: Inspect .sample in the block context. Creates external separation; some block margins can collapse. 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 ExampleBuild and test
The portfolio has a working internal destination, readable structure and a documented verification story. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<header><a href="#work">Alex’s portfolio</a></header><main><h1>A website I can explain</h1><section id="missing"><h2>Selected work</h2><p>Original projects with tested source.</p></section><section><h2>Verification</h2><p>Responsive, keyboard and content review documented.</p></section></main><footer>Built for learning and sharing.</footer>
Starter styles.css
body { font:18px/1.6 system-ui; margin:0; color:#172f54; } header,main,footer { max-width:70rem; margin-inline:auto; padding:1.5rem; } section { margin-block:2rem; }Objective contract
[
{
"type": "count",
"selector": "#work h2",
"value": 1,
"label": "Include 1 matching #work h2 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 id="work". The exercise instead uses id="missing". Identify its effect before changing it.
Hint 3
Restore the intended id="work" operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<header><a href="#work">Alex’s portfolio</a></header><main><h1>A website I can explain</h1><section id="work"><h2>Selected work</h2><p>Original projects with tested source.</p></section><section><h2>Verification</h2><p>Responsive, keyboard and content review documented.</p></section></main><footer>Built for learning and sharing.</footer>
styles.css
body { font:18px/1.6 system-ui; margin:0; color:#172f54; } header,main,footer { max-width:70rem; margin-inline:auto; padding:1.5rem; } section { margin-block:2rem; }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 portfolio has a working internal destination, readable structure and a documented verification story.
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.