Educator resources and 25 presenter scripts
Use the Vibe Learning cycle to elicit predictions, observe actual output, repair faults, explain evidence and transfer to a new case. Demonstration timings are rehearsal estimates, not produced videos. Grade objective checks, explanation, visual judgment, accessibility review and independent transfer separately.
1. Your first website
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
A website is a collection of resources that a browser retrieves and interprets. HTML describes content and meaning; the browser builds a document tree and applies default presentation even without CSS. An element consists of an opening tag, content and usually a closing tag. h1 identifies the page’s principal heading, while p marks a paragraph. The preview is a real browser document inside an isolated frame. Changing source does not affect the page until it is rendered again, unless automatic preview is enabled. Start by editing words rather than adding layout rules.
- Write a prediction, then click Run Preview.
One main heading appears above a paragraph. The heading is semantic content, not merely a large font.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
2. HTML elements
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
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.
- Write a prediction, then click Run Preview.
The important phrase is a child of the paragraph and has explicit importance semantics.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
3. Document structure
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
The HTML doctype requests standards-mode rendering. It is not an HTML element and has no closing tag. A document should have one html root with head and body children. Whitespace and indentation help humans but do not create semantic sections. The academy can wrap fragments for convenience; use a complete document when practicing document structure or exporting pages.
- Write a prediction, then click Run Preview.
A main landmark contains the page heading; the doctype requests standards mode.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
4. Links and images
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
An img is a void element with no closing tag. src identifies the resource, while alt supplies a text alternative for its purpose. Decorative images generally use an empty alt rather than repeating irrelevant details. Width and height establish an aspect ratio and reduce layout shifts. The academy includes original local SVG illustrations; uploaded assets are restricted to supported raster image formats.
- Write a prediction, then click Run Preview.
The illustration has a purpose-specific text alternative and scales within its available width.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
5. Lists and tables
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
A caption names the table. scope clarifies whether a header applies to its row or column in simple tables. Complex multi-level tables may need explicit header associations and often benefit from redesign. Visual bold text alone does not make a data cell a header. Review relationships without relying on color or borders.
- Write a prediction, then click Run Preview.
Monday is a row header and the table caption supplies context for the seat count.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
6. Semantic HTML
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
Semantic elements describe purpose. main identifies the principal content; nav identifies navigation; article identifies a self-contained composition. A generic div remains appropriate when no more specific meaning applies. Do not select an element merely because its default display looks convenient. Review the landmark and heading outline together to understand the page.
- Write a prediction, then click Run Preview.
A self-contained article is placed inside the principal content landmark.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
7. Accessible forms
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
A label names an individual control through wrapping or a matching for/id pair. A placeholder is not a persistent label. fieldset and legend group related controls and state the group’s purpose. Instructions and errors can be connected with aria-describedby when needed. Do not add redundant ARIA when native relationships already communicate the correct meaning.
- Write a prediction, then click Run Preview.
The visible label is associated with the email input through matching identifiers.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
8. First CSS styles
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
A stylesheet contains rules. A selector identifies elements, and declarations assign property/value pairs. CSS is interpreted independently of HTML structure, so a rule matching no elements has no visible effect. Start with one property and compare before combining many changes. The browser’s computed style reveals which value actually won, while the rule list shows candidate declarations.
- Write a prediction, then click Run Preview.
Only the matched heading receives the blue text color; the paragraph keeps its inherited/default styling.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
9. CSS selectors
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
A type selector matches element names, a class selector matches reusable class tokens, and an ID selector matches a unique identifier. Classes usually make reusable component styling easier than IDs. Specificity is only one stage in the cascade; importance, layers and origin can take precedence. Inspect actual matches before diagnosing a conflict.
- Write a prediction, then click Run Preview.
Only the paragraph with the matching class receives the background; the other paragraph remains unchanged.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
10. The cascade
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
The cascade filters applicable declarations and orders them by origin and importance, layers, specificity, scoping proximity where relevant and source order. Specificity alone is not a universal winning score. This small example isolates same-origin, same-layer, equal-specificity source order so the later declaration wins. The rule inspector lists candidates and computed values; it does not pretend to reconstruct every browser cascade decision.
- Write a prediction, then click Run Preview.
With equal cascade priority and specificity, the later blue declaration overrides the earlier red declaration.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
11. Colors
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
Colors can be written as named values, hex, rgb or hsl, among other modern formats. Different notations may describe the same sRGB color. Alpha adds transparency, which changes the resulting contrast against the background. The contrast tool calculates opaque sRGB ratios and clearly states that scope. Do not infer accessibility from a color’s name or from its numerical lightness alone.
- Write a prediction, then click Run Preview.
The text color is specified directly while the white background makes the contrast context explicit.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
12. Typography
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
A typography system coordinates a small set of sizes, weights and spacing values. Hierarchy should reflect content structure rather than arbitrary scale changes. A max-width in ch is an approximate reading measure, not an exact character count. Keep body text, headings and interactive controls consistent, and verify that longer titles wrap gracefully.
- Write a prediction, then click Run Preview.
The article has a controlled reading measure and a restrained lead-text size.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
13. Box model
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
The box model separates content from internal padding, border and external margin. A background extends through padding by default but margin stays outside it. With content-box sizing, a declared width excludes padding and border. The box-model inspector reports actual browser dimensions and computed edges; its diagram is a labeled educational view. Change one edge at a time and compare the outer width.
- Write a prediction, then click Run Preview.
Twenty pixels of internal space separate content from its border; margin creates external separation.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
14. Positioning
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
An absolutely positioned box is removed from normal flow and positioned against its containing block. A positioned ancestor commonly establishes that block. Relative positioning keeps the original flow space while allowing offsets. Use positioning for deliberate overlays rather than replacing all page layout. Ensure overlaid labels remain readable and do not cover controls at zoom.
- Write a prediction, then click Run Preview.
The product card establishes the badge’s containing block, so the overlay stays attached to the card.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
15. Flexbox alignment
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
Alignment distributes available space rather than creating arbitrary fixed offsets. justify-content acts on the main axis; align-items controls items on the cross axis. Extra cross-axis space is necessary to see many alignments. align-content instead concerns the distribution of flex lines and generally needs wrapping plus extra space. Use the axis labels and actual item bounds to diagnose a change.
- Write a prediction, then click Run Preview.
The fixed minimum container height leaves cross-axis room, making vertical centering observable in a row layout.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
16. Flexible layouts
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
Use Flexbox for a group whose main relationship is one-dimensional: navigation, toolbars or a row of related cards. Let items wrap and keep source order meaningful. A gap-based layout is easier to maintain than carefully balanced item margins. Test both short and long labels before declaring the component responsive. Native links remain functional navigation inside the layout.
- Write a prediction, then click Run Preview.
The navigation can form additional rows without hiding links or requiring an unimplemented menu button.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
17. Grid layouts
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
A grid container creates a two-dimensional layout of tracks. Direct children become grid items, and grid-template-columns defines explicit columns. Grid differs from Flexbox by coordinating rows and columns together rather than primarily one axis. The source order still matters for reading and keyboard navigation even when visual placement changes.
- Write a prediction, then click Run Preview.
The articles enter an explicit two-column grid; remaining items continue onto another row.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
18. Grid templates
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
A complete layout combines meaningful landmarks, resilient tracks and a narrow-screen default. Grid is not a reason to invent meaningless wrappers or fixed pixel columns. The minmax zero minimum helps content shrink while a max-width controls very wide screens. Test header, article and supplementary information with actual text at zoom.
- Write a prediction, then click Run Preview.
Flexible columns coordinate the report and notes without requiring a fixed total page width.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
19. Responsive breakpoints
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
A media query conditionally applies rules according to the environment. Choose breakpoints where content needs them, not solely from device names. The browser evaluates width queries against the preview’s actual CSS viewport. The Responsive Lab reports active queries and measured overflow. Resize across both sides of the boundary and test the layout, not just the presence of a query.
- Write a prediction, then click Run Preview.
The single-column default gains three columns only when the width condition matches.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
20. Fluid typography
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
rem follows the root font size, em depends on the relevant element context, percentages depend on the property and containing block, and viewport units follow a viewport dimension. clamp sets a minimum, preferred value and maximum. A fluid formula should retain sensible limits and work with user text scaling. Do not use viewport sizing alone to make body text unreadably small.
- Write a prediction, then click Run Preview.
The preferred viewport-based size is constrained by minimum and maximum rem values.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
21. Custom properties
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
Custom properties store token values and participate in the cascade and inheritance. var substitutes a referenced value and can supply a fallback for missing values. Tokens are case-sensitive. An invalid substituted value can invalidate the consuming declaration at computed-value time, so a defined token does not guarantee a valid property. Keep token names tied to roles rather than arbitrary colors.
- Write a prediction, then click Run Preview.
The button consumes a named accent token; changing that token can update multiple components consistently.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
22. Animations
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
Keyframes define values at points along an animation timeline. animation-name connects an element to a named keyframe rule. Duration, iteration and fill behavior determine what users see before and after active motion. Start with a subtle bounded effect and provide a reduced-motion alternative. A CSS keyframe definition alone does not animate anything until a matching animation is assigned.
- Write a prediction, then click Run Preview.
The named keyframes and animation assignment agree, producing a short reveal rather than an undefined animation.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
23. Accessibility review
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
Review both objective checks and human experience. Missing alt attributes, absent labels and empty links are detectable patterns; whether an alternative description is appropriate requires judgment. Check heading meaning, keyboard flow, zoom, contrast and error recovery with realistic tasks. The audit lists findings and explicit manual-review items, not a certification badge.
- Write a prediction, then click Run Preview.
The link has meaningful text, the image is explicitly decorative and the document has a coherent heading sequence.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
24. AI-assisted verification
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
AI can help propose structure and styles, but its output must be checked. Define audience, requirements and acceptance tests, inspect semantics and selector behavior, and verify target-browser support. Never accept a claim of rendering as evidence. The prompt studio includes current source and actual diagnostics without sending data to a model. A correct simple implementation is preferable to unexplained complexity.
- Write a prediction, then click Run Preview.
The reviewed implementation uses native control semantics instead of an incomplete custom role.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
25. Publish a complete site
3–7 minutes; rehearse first
We will make one controlled source change and inspect a real browser result.
Launch Prepared Demo- Read the prepared HTML and CSS.
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.
- Write a prediction, then click Run Preview.
The portfolio has a working internal destination, readable structure and a documented verification story.
- Click Inspect Element and select the relevant box.
Compare actual DOM relationships, matched rules, computed styles and measured dimensions.
- Change one value and click Run Preview again.
Name the first visible difference and explain the CSS or HTML relationship.
- Click Show Finished Code, then save your explanation.
Use the reference for comparison; revealing it does not mark independent mastery.
- Export Website and review the publishing guide.
The downloaded source works independently. Record real browser and accessibility tests before publishing.
Summarize the input, operation, actual result and one remaining verification task.
Module plan 1: Discovering web development
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 2: HTML document structure
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 3: Text, links and images
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 4: Lists, tables and content
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 5: Semantic HTML
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 6: Forms and user input
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 7: Getting started with CSS
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 8: Colors and typography
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 9: The CSS box model
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 10: Selectors and the cascade
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 11: Display and positioning
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 12: Flexbox layout
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 13: Grid layout
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 14: Responsive web design
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 15: Modern CSS and systems
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 16: Transitions and animations
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 17: Accessibility and usability
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 18: Professional components
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 19: Debugging, performance and AI
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Module plan 20: Complete website development
Begin with the smallest relevant example and ask learners to predict its DOM or visual result. Demonstrate Run Preview and the inspector, then let pairs change one source operation and compare evidence.
Worksheet: record task, input, prediction, actual result, first mismatch, repair, second test and remaining manual review. Discuss why appearance alone cannot establish semantics or complete accessibility.
Rubric: 0 = no evidence; 1 = sample result only; 2 = normal and failure evidence with an accurate explanation; 3 = independent extension plus target-browser, accessibility and publishing review.
Assignment: choose a related project, implement a milestone, verify responsive and keyboard behavior and export a complete source folder. Review the source and observed outcomes rather than counting clicks.
Independent learning objects
- Browser rendering explorer
- HTML tag anatomy
- Opening and closing tags
- Document structure tree
- Element nesting
- HTML attributes
- Heading hierarchy
- Text formatting
- Link paths
- Image sizing and alternatives
- List builder
- Table designer
- Semantic landmarks
- Accessible form builder
- HTML validation
- CSS declaration anatomy
- Selector matching
- Class and ID selectors
- Specificity calculator
- Cascade inspector
- Inheritance
- Pseudo-class states
- Pseudo-elements
- CSS units
- Color formats
- Color palette
- Gradients
- Typography
- Text spacing
- Border radius
- Shadows
- Backgrounds
- Box model
- Box-sizing comparison
- Margin collapsing
- Block and inline display
- Overflow
- Positioning
- Stacking contexts
- Flexbox axes
- Flex alignment
- Grow and shrink
- Wrapping
- Grid tracks
- Grid placement
- Named areas
- Auto-fit and auto-fill
- Viewport sizes
- Media queries
- Fluid typography
- Responsive images
- Container queries
- Custom properties
- Theme tokens
- Transforms
- Transitions
- Keyframes
- Easing
- Contrast
- Keyboard focus