DiscoveryVIP / HTML & CSS AcademyHelp

97. Content planning, wireframes and visual design

Module 20 · About 20 minutes · Lesson 96; review earlier concepts as needed

Open Interactive Lesson

Discover

What changes when you use content planning, wireframes and visual design, and how can you prove it?

Predict

Record the expected structure or visual change before rendering. Name one thing that should remain unchanged.

Understand

A wireframe explains hierarchy and relationships without depending on final colors or images. Start with headings and content order, then identify reusable regions. Test long text, empty states and narrow widths early. Visual design can improve the reading hierarchy, but it should not hide unclear information architecture. The Structure Studio supports adding, moving and inspecting actual elements.

Important source lines

index.html:1 <main><h1>Content-first wireframe</h1><section><h2>What you will learn</h2><p>Skills and outcomes.</p></section><section><h2>How to join</h2><p>Dates and contact details.</p></section></main>
The document’s principal content, normally one visible instance. Attribute guidance: id useful for skip links.
styles.css:1 section { border:1px dashed #789; padding:1rem; margin-block:1rem; }
Combines border width, style and color. Accepted grammar: <line-width> || <line-style> || <color>. 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: Content planning, wireframes and visual design

Two explicit sections give the page a content hierarchy before the visual system is elaborated.

index.html

<main><h1>Content-first wireframe</h1><section><h2>What you will learn</h2><p>Skills and outcomes.</p></section><section><h2>How to join</h2><p>Dates and contact details.</p></section></main>

styles.css

section { border:1px dashed #789; padding:1rem; margin-block:1rem; }

script.js

Expected: Two explicit sections give the page a content hierarchy before the visual system is elaborated.

Edit and Render This Example
Example 2: 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 Example
Example 3: Property: margin-block

Sets logical block-axis separation.

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-block: 24px; }

script.js

Expected: Inspect .sample in the block context. Sets logical block-axis separation. 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 Example
Example 4: Property: border

Combines border width, style and color.

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 { border: 3px solid #234f9b; }

script.js

Expected: Inspect .sample in the block context. Combines border width, style and color. 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 Example
Example 5: Status notification

A polite status can announce noncritical updates without stealing focus.

index.html

<section data-component aria-label="Status notification">
<button id="save">Save item</button><p id="toast" role="status"></p>
</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('#save').onclick=()=>{root.querySelector('#toast').textContent='Item saved';};

Expected: Add a persistent notification history.

Edit and Render This Example

Build and test

Two explicit sections give the page a content hierarchy before the visual system is elaborated. 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>Content-first wireframe</h1><section><h2>What you will learn</h2><p>Skills and outcomes.</p></section></main>

Starter styles.css

section { border:1px dashed #789; padding:1rem; margin-block:1rem; }

Objective contract

[
  {
    "type": "count",
    "selector": "main > section",
    "value": 2,
    "label": "Include 2 matching main > section 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 <section><h2>How to join</h2><p>Dates and contact details.</p></section>. The exercise instead uses an omitted operation. Identify its effect before changing it.

Hint 3

Restore the intended <section><h2>How to join</h2><p>Dates and contact details.</p></section> operation or implement an equivalent structure/style. Run the actual checks and explain why it works.

Complete reference solution

index.html

<main><h1>Content-first wireframe</h1><section><h2>What you will learn</h2><p>Skills and outcomes.</p></section><section><h2>How to join</h2><p>Dates and contact details.</p></section></main>

styles.css

section { border:1px dashed #789; padding:1rem; margin-block: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. Two explicit sections give the page a content hierarchy before the visual system is elaborated.

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

  1. Explain this lesson’s source line by line using the actual objective above.
  2. Help implement one small extension and define normal, boundary and failure tests.
  3. Review/debug the source against actual preview observations; verify standards and never claim rendering without evidence.

Continue to Lesson 98: Building a complete responsive website

Detailed learning and editor help · Standards reference