A multi-page website is simply a collection of HTML documents that live together in an organized folder and are connected to each other through links. Instead of putting everything on one long page, you separate content into purposeful pages — a home page, an about page, a contact page — and give visitors a consistent way to move between them. Before you write any HTML, though, you need a plan: what pages exist, what each page is for, what files and folders hold them, and how the navigation ties it all together.
In this course, this topic is the foundation for everything else in Module 2. HTML is the structural layer of the web: elements like header, nav, main, section, article, and footer describe what each part of a page means, not just how it looks. Semantic markup matters because it makes your pages easier for other developers to read, easier for search engines to interpret, and far more usable for people relying on screen readers. Internal links, written as relative paths, are what turn a pile of separate HTML files into a single coherent site.
The videos below focus on the planning and structuring habits that come before and around the code. As you watch, look for the ideas you can transfer directly to a website project: how to break a project into pages or components, how to decide on a folder and file organization, how to sketch structure before building, and how to keep naming and layout consistent. The specific tools and languages shown may differ from plain HTML, but the planning discipline is the same.
Tech With Tim walks through a nine-step process he uses to plan a coding project before writing code, from clarifying the goal to breaking the work into manageable pieces. Expect discussion of defining requirements, sketching out the pieces of the project, and sequencing the build. The emphasis is on thinking first so that the implementation stage goes smoothly.
This maps directly to the "Planning a Website Before Writing Code" subtopic and models the habit of deciding on pages, content, and structure before opening an editor.
This video covers practical ways to structure a programming project, including how to organize files and folders, name things consistently, and document the project so others can follow it. Tim presents the ideas as a checklist of simple, repeatable practices. The focus is on making a project readable and professional rather than on any one language.
File and folder organization is exactly what a multi-page website needs for relative links to work, and the video reinforces the consistency and naming discipline this topic introduces.
A working web designer condenses his end-to-end website process into about twelve minutes, moving from initial planning and content decisions through layout and delivery. The video includes a shared Trello template for tracking the stages of a site build. It is oriented toward real client websites rather than a single practice page.
It frames website creation as a multi-page, multi-stage process, which supports the conceptual subtopics on what a multi-page site is and how to plan one before coding.
These videos deliberately cover the planning and organizational side of building a site rather than HTML syntax, which you will practice in the hands-on portions of this module. The project-planning and project-structure videos support MO4 by showing how deliberate file and folder organization makes a consistent, working navigation possible, and they support MO1 by encouraging you to decide what each page contains before marking it up with semantic elements. The web design process video reinforces the multi-page mindset that underlies MO3 and MO5, since a site planned as a connected set of pages is one whose internal links, external links, and images can be systematically tested at the end. Pair these planning habits with the course readings and code demonstrations on semantic elements, image attributes, and link paths to meet MO1 through MO5 in full.
These videos were chosen from YouTube on October 3, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.