102: Introduction to Web Development
4–6 hours including practice, repair and a return task — a pilot estimate, not a measured duration or time requirement.
Do these real-file tasks in a practice folder you control. This readable/printable route does not create an interactive completion record. No account, purchase, publishing or certification is required.
Use the practice-pack assets and keep your own notes and source files. References are optional onward resources. Record help honestly.
Lesson 1 · 10–20 min
Find your workspace
Make a practice folder you can find again, and distinguish the editor from the browser.
Your challenge
If you close both apps, how will you find the file you were working on?
Learn
Three things, three jobs
The editor changes the source text. A file stores that text under a name in a folder. The browser reads an HTML file and draws a page. An app window is not the file itself. Opening the same file in two apps does not create two independent copies.
A suitable starting surface
This route uses a computer, a keyboard, a plain-text editor such as Notepad and a browser. You need permission to save a practice folder. Phone-only browsing can explore concepts, but does not demonstrate this local-file outcome. You do not need Codex, hosting, a domain, an account or paid software. If saving or finding files is unfamiliar, use PC Basics or ask for targeted help; you do not need to repeat skills you already have.
Keep a small safe workspace
Create a folder called my-first-page in an appropriate place you control, such as Documents. Keep the course folder separate from your own work so you do not accidentally edit the course. Use fictional information throughout. The supplied practice-pack contains original images and repair cases; keep sensitive business or personal files out of the file checker.
Try it
- Create my-first-page in a folder you can locate again. Write its location in your evidence note.
- Open Notepad using its normal app shortcut or Start search. Type one sentence about a hobby or fictional event. Save it as practice.txt in my-first-page.
- Close the document, find the folder again and reopen practice.txt in the editor. Change one word, save, close and reopen it.
- Identify which window is the editor, which item is the file and which folder contains it. If the save location is unclear, stop here and practise that action before continuing.
Evidence to record
- What I did and checked: Record the practice file name, the action you actually took and what you observed. Use non-sensitive practice content.
- What I understand now: Explain one choice or repair in your own words. A short honest explanation is enough.
- Help used
Review criteria
- I found and reopened the actual saved text file, not just a recent-window preview.
- I can identify the editor, file and folder and the permission boundary of my practice workspace.
Optional repair guidance
Return to the small working example. Check one thing at a time; record the help you used, then retry.
The interactive checker supplies limited source checks only; review the actual browser page too.
Continuing references
Back to topLesson 2 · 20–30 min
Turn plain text into an HTML page
Save a real .html file, open it in a browser and make one visible change.
Your challenge
Why can the same words look like source in Notepad and like a page in a browser?
Learn
HTML gives content a structure
HTML is a markup language, not a programming language. Tags identify parts of a document, such as a heading or paragraph. The browser interprets the markup. A plain text file containing HTML can be saved with .html so it is recognised as a web document. Renaming a Word .docx file does not turn its underlying contents into HTML.
A small original starting example
Type or carefully copy this skeleton into a new plain-text document. The head contains page information; the body contains what the visitor reads. The title appears on a browser tab. The h1 is the main heading inside the page. You do not need to memorise every line today.
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>My first page</title>
</head>
<body>
<main>
<h1>A page I made</h1>
<p>This is my first saved HTML page.</p>
</main>
</body>
</html>Save deliberately
In Notepad, use File → Save as. Choose my-first-page and name the file index.html. If a file-type option is shown, choose All files rather than a text-only suffix; use UTF-8. Notepad versions differ, so inspect the actual result rather than assuming the menu looked identical. In File Explorer show file-name extensions, then check the full ending. index.html.txt is not index.html. Never use an icon alone as evidence.
Choose which app opens it
Open the saved index.html with your browser using Open with if needed. Open that same file in Notepad to edit its source. Change the h1 wording, save in Notepad and refresh/reload the browser. Saving and refreshing are separate actions. A file:// address is a local preview, not a public website.
Try it
- Create index.html using the small example. Verify the full file name and UTF-8 save choice.
- Open it in the browser and find the tab title and visible heading.
- Return to the same source in Notepad, give the heading new words, save, and refresh the browser. Explain what changed and why.
- Close and reopen the saved file. If it opens as text or shows no change, use the hint instead of creating multiple mystery copies.
Evidence to record
- What I did and checked: Record the practice file name, the action you actually took and what you observed. Use non-sensitive practice content.
- What I understand now: Explain one choice or repair in your own words. A short honest explanation is enough.
Review criteria
- The actual saved filename ends .html without an extra .txt.
- I opened the same file in the editor and browser, and proved a saved edit appears after refresh.
- I can distinguish the tab title, page heading and local preview from publishing.
Optional repair guidance
Check the full filename first. Then confirm the editor and browser point to the same folder/file. Save the source before refreshing. If the default app is the editor, choose Open with → your browser; do not alter system-wide defaults just for this exercise.
The interactive checker supplies limited source checks only; review the actual browser page too.
Continuing references
Back to topLesson 3 · 20–30 min
Structure content for a reader
Use headings, paragraphs and a list for a small useful page.
Your challenge
Which parts of your page help a reader understand the content, rather than merely make it look large?
Learn
Meaning before decoration
An element usually combines an opening tag, content and a closing tag. Attributes give extra information. h1 names the page’s main subject; h2 introduces a section. Paragraphs belong in p elements and list items inside ul or ol. Use the element that fits the meaning, rather than many line breaks or a heading chosen only for its size.
Head and body have different jobs
The title in head labels the browser tab. The main heading and paragraphs sit in body, inside a main region. Keep one clear main h1 in this beginner project and use h2 for sections below it. Nest tags in a consistent order; indentation helps you see which content belongs together.
<main>
<h1>Community Garden Visit</h1>
<p>A short invitation to a fictional garden visit.</p>
<h2>What to expect</h2>
<p>We will look at herbs and share planting ideas.</p>
<ul>
<li>Bring a notebook</li>
<li>Wear comfortable shoes</li>
</ul>
</main>Explain a choice
Copying a valid example is a useful starting point. Now change its content and explain why a heading, paragraph or list belongs where it does. That explanation tells you more than whether the page happens to appear. You can use the fictional garden topic or another non-sensitive practice topic during this lesson; the final brief has specific requirements.
Try it
- Give the tab a useful title and the page one main h1. Add a useful h2, two paragraphs and a real list with at least two items.
- Use a main region and keep the document skeleton from the previous lesson.
- Save and refresh. Explain which content is metadata and which is visible body content.
- Without copying the example again, add another list item and explain the tag you chose.
Evidence to record
- What I did and checked: Record the practice file name, the action you actually took and what you observed. Use non-sensitive practice content.
- What I understand now: Explain one choice or repair in your own words. A short honest explanation is enough.
- Where does the tab title belong?
Review criteria
- Headings describe a useful hierarchy and paragraphs/lists use appropriate elements.
- I can explain title versus h1 and change the content without rebuilding the whole file.
Optional repair guidance
Return to the small working example. Check one thing at a time; record the help you used, then retry.
The interactive checker supplies limited source checks only; review the actual browser page too.
Continuing references
Back to topLesson 4 · 30–40 min
Links, images and paths
Connect a descriptive link and a local image, then repair a wrong path.
Your challenge
When an image goes missing, what tells the browser where to look?
Learn
A path is an instruction from a starting place
Relative paths start from the document containing them. In index.html, images/garden.svg means “enter the images folder beside this page, then find garden.svg”. Use forward slashes in HTML paths, even on Windows. File names and letter case should match consistently; a case mismatch that happens to work locally may fail on another system. For this course, use simple lowercase file names.
Links and images use different attributes
A link uses href. An image uses src and alt. A link to #visit jumps to the element with id="visit" in the same page. A useful link says what it leads to. The supplied garden illustration is informative: its alt text should briefly convey its purpose. Purely decorative images can use empty alt, but that is not the role of this practice image.
<a href="#visit">Read the visit details</a>
<h2 id="visit">Visit details</h2>
<img src="images/garden.svg" alt="Plants growing in a community garden">Keep the supplied assets local
Use practice-pack/images/garden.svg, an original Bhala practice illustration. Copy it into an images folder inside your own project. This is a normal file copy; do not move the course’s only copy. No online image account or download service is required. When you select files later, the course checks text and names locally but cannot prove their on-disk folder placement or that the browser rendered them.
Try it
- Inside my-first-page create images. Copy garden.svg from the supplied practice-pack/images into it.
- Add a descriptive same-page link to #visit, create that section id, and add the image using images/garden.svg plus useful alt text.
- Save, refresh, activate the link using Tab then Enter and check the image appears.
- Temporarily change the src to images/not-here.svg, observe the fault, then repair the path. Record the cause and fix, not just “it works”.
Evidence to record
- What I did and checked: Record the practice file name, the action you actually took and what you observed. Use non-sensitive practice content.
- What I understand now: Explain one choice or repair in your own words. A short honest explanation is enough.
- If images is beside index.html, which src fits?
Review criteria
- The link reaches the intended section and can be activated by keyboard.
- The supplied image really appears from a local relative path, with a purposeful text alternative.
- I caused and repaired a path error and can explain where the browser starts looking.
Optional repair guidance
Return to the small working example. Check one thing at a time; record the help you used, then retry.
The interactive checker supplies limited source checks only; review the actual browser page too.
Continuing references
Back to topLesson 5 · 30–40 min
Make a small stylesheet
Link CSS and make controlled changes to readability and spacing.
Your challenge
How can you tell whether CSS is connected, rather than guessing that the browser ignored your design?
Learn
Content and presentation
CSS describes presentation. A selector names what receives a rule; declarations give a property and a value inside braces. Start with a few rules you can explain. You do not need a framework, a complete layout system or a large stylesheet to make this first page readable.
A linked file you can inspect
Create styles.css beside index.html using plain text. Link it in head. Keep .css as the actual extension, without .txt. Begin with the small example below and vary one value at a time. Test a conspicuous temporary change to prove the link works, then choose readable final colours. Colour alone is not a sufficient accessibility check.
<!-- Put this link in the HTML head -->
<link rel="stylesheet" href="styles.css">
/* Put these rules in styles.css, not inside the HTML link */
body { font-family: Arial, sans-serif; line-height: 1.6; margin: 1rem; }
main { max-width: 48rem; margin: auto; padding: 1rem; }
h1 { color: #174b40; }
img { max-width: 100%; height: auto; }
a:focus-visible { outline: 3px solid #8a4600; }A page should fit its reader
A max-width on the content can prevent excessively long lines while still allowing a narrow window. max-width: 100% on the image helps it fit its container; height: auto preserves its shape. These are small starting checks, not a full responsive design or accessibility audit. Keep normal browser focus outlines visible.
Try it
- Create styles.css and add the link in the head of index.html. Keep only the CSS rules in the CSS file.
- Prove the link with one obvious temporary heading colour, saving the CSS before refreshing. Then choose a readable final colour.
- Change spacing or font, one property at a time, and explain the selector, property and value you changed.
- Narrow the browser window and check that the page remains readable and the image fits. If nothing changes, inspect the stylesheet filename, link path, saved state and braces.
Evidence to record
- What I did and checked: Record the practice file name, the action you actually took and what you observed. Use non-sensitive practice content.
- What I understand now: Explain one choice or repair in your own words. A short honest explanation is enough.
Review criteria
- My selected CSS file is really linked to the HTML and a controlled edit changes the page.
- I can identify one selector/property/value and explain the save-refresh cycle for a second file.
- The page and image fit a narrow window, and keyboard focus remains visible.
Optional repair guidance
Return to the small working example. Check one thing at a time; record the help you used, then retry.
The interactive checker supplies limited source checks only; review the actual browser page too.
Continuing references
Back to topLesson 6 · 25–35 min
Repair a page deliberately
Diagnose a filename/path/style fault and record the repair.
Your challenge
What will you check first when a page looks wrong, and why?
Learn
A five-question repair routine
Ask: Am I editing the right file? Did I save it? Is this browser showing that file? Do the names and relative paths match? Is the markup/CSS structure what I intended? Predict one cause, change one thing and check the result. Keep a copy of a working file before an experiment. A failed attempt is evidence about what to inspect next, not proof that you cannot do web development.
Use the supplied repair lab
practice-pack/repair-lab contains small fictional fault cases. Copy that folder to your own practice area before changing it. One HTML file has an extra .txt suffix. Another page points at the wrong stylesheet. The repair-lab README describes the intended behaviour. The Reveal guidance control is optional support; try observing and explaining a fault first.
A visible page can still hide a source mistake
Browsers often repair malformed HTML when drawing a page. Seeing something appear does not prove every tag or path is correct. Use the source and expected result together. You do not need advanced developer tools today; the reference explains how inspection can grow later.
Try it
- Copy repair-lab into your own folder. Pick one fault and write a prediction before changing it.
- Open the relevant source in Notepad and inspect its full name or link. Make one repair, save and refresh.
- Record the observed symptom, likely cause, change and result. If your first hypothesis failed, record the next check.
- Repeat on a second fault if the first repair became obvious from its filename; choose one you can explain rather than memorising the supplied fix.
Evidence to record
- What I did and checked: Record the practice file name, the action you actually took and what you observed. Use non-sensitive practice content.
- What I understand now: Explain one choice or repair in your own words. A short honest explanation is enough.
- My first useful check when a saved edit is not visible
Review criteria
- I recorded an actual symptom, a cause hypothesis, a repair and its checked result.
- I can distinguish “the browser drew something” from evidence that the intended source and files are correct.
Optional repair guidance
For first-page.html.txt, preserve a copy, open it in the text editor and Save As a real .html file; verify the full name. For wrong-style.html, inspect the href against the actual lab.css file in the same folder. Save the HTML link change, then refresh the right page. Record this guidance as support used.
The interactive checker supplies limited source checks only; review the actual browser page too.
Continuing references
Back to topLesson 7 · 40–60 min
Build and check your first page
Produce an independent local first-page project from a short brief.
Your challenge
Can a reader find the visit information, and can you prove the files you saved create that page?
Learn
Your project brief
Make a fictional Community Garden Visit page. Use Community Garden Visit in the tab title and main h1. Include two meaningful paragraphs explaining the activity and what visitors should know; a real list of at least two things to bring; a Visit details section using id="visit"; a descriptive link to #visit; and the supplied garden.svg image at images/garden.svg with meaningful alt text. Save the page as index.html and link styles.css. Use a language, UTF-8, main region and useful h2 headings.
Build from the brief
Create your own text and organise the page from the brief. You may consult references and earlier notes, but record support honestly. The aim is to put a small set of ideas together, not to reproduce a screenshot. No JavaScript, form, account, hosting or real contact data is needed. Your small stylesheet should cover a font, spacing and an image that fits its container.
Two kinds of checking
First open the real page and inspect what the visitor experiences. Test the link by keyboard and narrow the window. Then select your HTML, CSS and supplied image below for local source checks. The checker reads only the selected practice files in this browser. It never uploads or runs the HTML. Its checks are limited: it cannot verify visual layout, contrast, useful wording, actual directory placement or whether you worked independently. Review those yourself or ask a person to observe.
Try it
- Build the project in your own practice folder from the brief, using references only where needed.
- Open the saved page in your real browser; test the title/heading, link, image, narrow window and keyboard focus.
- Choose index.html, styles.css and garden.svg in the local file checker. Read each failed check, make a targeted repair outside this course, and select the saved files again.
- Record a short evidence note and explain one choice or fix. Confirm the review items only after checking the latest saved version.
Evidence to record
- What I did and checked: Record the practice file name, the action you actually took and what you observed. Use non-sensitive practice content.
- What I understand now: Explain one choice or repair in your own words. A short honest explanation is enough.
Review criteria
- I opened the actual saved project and made a fresh change that appeared after save/refresh.
- The page meets the brief and the link/image work from the actual folder structure.
- I tested keyboard access and a narrow window and judged the heading/alt wording myself.
- The local file checks refer to the latest selected saved version; I understand they are not a visual or independent competence assessment.
Optional repair guidance
Return to the small working example. Check one thing at a time; record the help you used, then retry.
The interactive checker supplies limited source checks only; review the actual browser page too.
Continuing references
Back to topLesson 8 · 20–30 min
Keep learning with W3Schools
Find, adapt and verify one relevant documentation example.
Your challenge
How will you answer the next small HTML/CSS question without starting another whole course?
Learn
A map, not another library to memorise
Use the guided links below. HTML Introduction orients you to markup. HTML Editors connects the explanation to your own files. Basic Examples and Try it Yourself let you change a small example and run it. CSS Introduction is a next reference for style. HTML Exercises can provide optional recall practice. You do not need to sign up, track progress, buy a certificate, start Spaces hosting or accept a paid plan to read the linked tutorial material.
A deliberate example workflow
Choose one small question, such as “How do I add another list item?” or “How do I change paragraph colour?” Find the relevant tutorial example. Predict a change, edit the example and run it. Explain what the example demonstrates, then apply one change to your local page. Success inside an online editor does not automatically update a local file.
Use the right kind of reference
Tutorials teach a sequence; a reference answers a focused syntax question; exercises can help you recall a concept. MDN is useful when you want a deeper explanation, and W3C/WAI supports accessibility decisions. You are learning how to use documentation, not outsourcing all decisions to an example. Leave unfamiliar JavaScript, frameworks and backend topics for later.
Try it
- Choose one small improvement you want to make to your page and write the question in your evidence note.
- Open the most relevant W3Schools link. Find a matching example, predict one change, use Try it Yourself if available and compare the result. If an external feature requires an account, skip it and use the readable example; no registration is required by this course.
- Apply the idea in your own local file, save and refresh. Explain the difference between the online example and your local source.
- Record the exact source URL, the change and what you checked. Choose one next topic rather than trying to finish every tutorial.
Evidence to record
- What I did and checked: Record the practice file name, the action you actually took and what you observed. Use non-sensitive practice content.
- What I understand now: Explain one choice or repair in your own words. A short honest explanation is enough.
- Reference URL I actually used: Paste the public tutorial/reference URL; never a private account or access-token link.
Review criteria
- I found an appropriate tutorial/example and can explain the change I made.
- I applied and checked a change in my own local page, not just in an online editor.
- I recorded the source and a sensible next learning question without needing a purchase or account.
Optional repair guidance
Return to the small working example. Check one thing at a time; record the help you used, then retry.
The interactive checker supplies limited source checks only; review the actual browser page too.
Continuing references
Back to topLesson 9 · 20–30 min return task
Transfer: make a different page
Reopen your work after a gap and adapt the skills to a new brief.
Your challenge
Can you use the method when the topic, filenames, image and destination section change?
Learn
A changed brief
When practical, return after a short gap, for example 3–7 days. That is a pilot scheduling suggestion, not a scientifically fixed interval or a date lock. You can preview this task now. Create a new folder so the garden project remains intact. Make a fictional Repair Cafe page in repair.html with repair.css, and copy repair-cafe.svg into its images folder. Use Repair Cafe in the title and main h1, two meaningful paragraphs about the event, a list of at least two items to bring, a section id="bring", and a descriptive link to #bring. Use the new image path images/repair-cafe.svg and appropriate alt text.
Remove the click-by-click guide
Work from this brief rather than replaying the original example line by line. References are allowed; record what you used. Include the same basic language/UTF-8/main structure, simple readable CSS and flexible image. Introduce one harmless path or filename mistake, then repair and explain it. The change in context should affect your content and checks, not just replace a single word.
An honest final result
Open and test the new page in your browser. Then select the transfer HTML, CSS and image for the local checker. Self-review and support records matter alongside the source checks. Completing this course means completing these beginner exercises, not becoming a professional developer or obtaining certification. Website Building with Codex remains a separate 201 proposal. Existing manual and AI collaboration skills can be demonstrated without buying duplicate foundations.
Try it
- Create the new repair-cafe project from the changed brief, preserving the garden folder.
- Make and repair one small deliberate fault. Record the symptom, cause, correction and test.
- Test the real page by keyboard and in a narrow window. Select repair.html, repair.css and repair-cafe.svg for transfer checks, then review the latest saved version.
- Record when you returned, what you could do without the original guide, any support used, and one next learning step.
Evidence to record
- What I did and checked: Record the practice file name, the action you actually took and what you observed. Use non-sensitive practice content.
- What I understand now: Explain one choice or repair in your own words. A short honest explanation is enough.
- When I attempted this transfer
- Support used on the changed task
Review criteria
- This is a separate changed project, and the original garden source is preserved.
- I completed and checked the changed brief, including the new files, image and section link.
- I explained an actual repair and recorded help and whether this was a delayed return or an immediate preview.
- I understand the beginner scope and have chosen a practical next documentation topic.
Optional repair guidance
Return to the small working example. Check one thing at a time; record the help you used, then retry.
The interactive checker supplies limited source checks only; review the actual browser page too.
