DiscoveryVIP / HTML & CSS AcademyHelp

1. Understanding websites and web browsers

Module 1 · About 20 minutes · No previous experience

Open Interactive Lesson

Discover

What changes when you use understanding websites and web browsers, 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 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.

Important source lines

index.html:1 <h1>My First Website</h1>
The highest-level heading for a page topic. Attribute guidance: global attributes.
index.html:2 <p>I am learning HTML and CSS.</p>
A paragraph of prose. Attribute guidance: global attributes.

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: Understanding websites and web browsers

One main heading appears above a paragraph. The heading is semantic content, not merely a large font.

index.html

<h1>My First Website</h1>
<p>I am learning HTML and CSS.</p>

styles.css

script.js

Expected: One main heading appears above a paragraph. The heading is semantic content, not merely a large font.

Edit and Render This Example
Example 2: 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 Example
Example 3: 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 Example
Example 4: 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 Example
Example 5: 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 Example

Build and test

One main heading appears above a paragraph. The heading is semantic content, not merely a large font. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.

Starter index.html

<p>My First Website</p>
<p>I am learning HTML and CSS.</p>

Starter styles.css

Objective contract

[
  {
    "type": "count",
    "selector": "h1",
    "value": 1,
    "label": "Include 1 matching h1 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 <h1>My First Website</h1>. The exercise instead uses <p>My First Website</p>. Identify its effect before changing it.

Hint 3

Restore the intended <h1>My First Website</h1> operation or implement an equivalent structure/style. Run the actual checks and explain why it works.

Complete reference solution

index.html

<h1>My First Website</h1>
<p>I am learning HTML and CSS.</p>

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. One main heading appears above a paragraph. The heading is semantic content, not merely a large font.

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 2: How HTML, CSS and JavaScript work together

Detailed learning and editor help · Standards reference