Responsive Web Design / HTML / Basic HTML
Build a Travel Agency PageEvery destination needs a clear connection.
Watch Rob build the project, understand what each part is for, then work through the official freeCodeCamp lab at your own pace.
ORIGINAL WALKTHROUGH · 26:16
Watch with Rob.
Pause whenever you want to try a change. You can return to the lesson at any time.
You are signed in, but video access needs attention. Check your account access. Your saved work is kept.
Video walkthroughs are included with an active Code Zone membership. The written lesson and practice are free.
Rob’s 26:16 recording is paired with the current official lab. The requirement groups below are reading guidance, not video timestamps; your official tests and completion stay on freeCodeCamp.
THE IDEA BEHIND THE BUILD
What this lab teaches
A travel page combines several HTML ideas into one readable document. Metadata describes the site to the browser, headings organize what visitors see, two package links offer choices, and three linked destination images belong with their captions. The challenge is keeping those relationships clear as the page grows.
Plan the document in layers: browser information first, a visible introduction next, then package choices and destination figures. Finish by auditing all five anchors. Use the current official text for the exact headings, option labels, title and destinations that its tests require.
Build the document in layers
Keep metadata in head and visible travel information in body.
Group images with their captions
Use figure and figcaption to keep each destination’s visual explanation together.
Audit repeated links
Check both package links and all three destination links for the required destination and new-tab behavior.

REVIEW THE REQUIREMENTS · THREE CLEAR GOALS
Your route through the lab
These groups are a reading guide to the lab, rather than timestamped chapters of the video.
Describe the document
Set up HTML, language, encoding, browser title and a short metadata description.
Check your understanding: Can you distinguish the description meta element from a visible paragraph?
Explore requirement 1Introduce destinations and packages
Give visitors a page heading, context and two linked package options.
Check your understanding: Are both option labels enclosed by their own anchors inside list items?
Explore requirement 5Build the destination gallery
Group three linked pictures with captions, then inspect all five anchors.
Check your understanding: Does each destination have an image, an alternative description and its own caption?
Explore requirement 10SEE HOW THE PARTS FIT
A page with a clear structure
This small example uses a different subject to demonstrate the underlying pattern. It is intentionally incomplete and does not provide the official lab’s finished page.
<figure>
<a href="/studios/ceramics">
<img src="/images/studio.webp" alt="Pottery wheels around a bright studio">
</a>
<figcaption>A place to try your first clay project.</figcaption>
</figure>headEncoding, browser title and page descriptionh1 + pTravel destinations and an introductionh2 + ulTwo linked package optionsfigure + a + imgA clickable destination imagefigcaptionContext for that particular destinationThree things to pay attention to
A caption belongs to its figure
Keep each caption with its own picture rather than grouping all captions after the gallery.
Metadata is not visible page copy
The description meta element belongs in head; the introduction paragraph belongs in body.
Repeated anchors need a final audit
The lab checks all five destinations and target attributes. One correctly configured card is not sufficient.
UNDERSTAND IT HERE · PRACTICE IT THERE
Explore each requirement
Choose a requirement for a plain-English explanation, a separate code example and resources to explore. When you are ready, its button opens the official freeCodeCamp lab. Your official tests and completion stay on freeCodeCamp.
Requirement 1Select modern HTML document mode
UNDERSTAND THE IDEA
The document declaration tells the browser to interpret the page as modern HTML. It belongs before the root element and is not a visible heading, paragraph, or comment that should appear in the travel page.
What you will do
Start the official lab with the modern HTML declaration before the root element.
<!DOCTYPE html>What to notice: The doctype is a declaration and has no closing tag.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
Requirement 2Identify the document language
UNDERSTAND THE IDEA
A document language helps browsers and assistive technology interpret the page’s text. The lang attribute belongs on the html root, so the information applies to the document rather than just one heading.
What you will do
Create the html root with English as its language, and close it after the page’s content.
<html lang="en">
<!-- Document information and content belong here. -->
</html>What to notice: The language value is an attribute of html. This outline deliberately omits the finished travel page.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
Requirement 3Separate character encoding and browser-tab title
UNDERSTAND THE IDEA
Head metadata describes the document to the browser. UTF-8 supplies the character encoding, while title names the browser tab. Neither item replaces the visible destination heading that will go in the body.
What you will do
Inside head, add the required UTF-8 declaration and the exact browser-tab title specified in the lab. Keep the visible page content outside head.
<head>
<meta charset="utf-8">
<title>Neighborhood Workshop Directory</title>
</head>What to notice: This directory title is an analogous example. Use the travel lab’s required title for its tests.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
Requirement 4Write a useful page description
UNDERSTAND THE IDEA
A metadata description summarizes what someone will find on the page. It uses a meta element with name and content attributes, rather than visible paragraph text or a made-up description element.
What you will do
Add a second meta element in head with name="description" and a short, nonempty summary of your travel website in content.
<meta name="description" content="Find friendly weekend craft workshops and local group sessions.">What to notice: The summary belongs in content. This example describes a different directory.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
Requirement 5Give the visible page one main heading
UNDERSTAND THE IDEA
The visible h1 tells visitors what the page is about. Keeping one main heading establishes a clear starting point for the later package and itinerary sections, rather than treating every section as another page title.
What you will do
Inside body, add one h1 that introduces your travel destinations. Do not create extra h1 elements for the later sections.
<h1>Find your next creative workshop</h1>What to notice: The browser-tab title and the visible main heading serve different audiences and can use different wording.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
Requirement 6Introduce the opportunities below the heading
UNDERSTAND THE IDEA
An introductory paragraph gives the main heading context. Placing it immediately below h1 makes the page read as a title followed by a useful explanation before visitors reach lists or destination images.
What you will do
Put a nonempty paragraph directly below your main heading, introducing the travel opportunities you offer.
<h1>Find your next creative workshop</h1>
<p>Explore welcoming sessions for first-time makers.</p>What to notice: The paragraph follows the heading as its sibling, rather than being placed inside the heading.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
Requirement 7Introduce the package section with a second-level heading
UNDERSTAND THE IDEA
A second-level heading identifies a major section beneath the page’s single main heading. A heading’s visible text can also be an explicit lab requirement, so selecting the right element alone is not always enough.
What you will do
Add an h2 with the exact package-section text required by the lab. Keep the main heading and introduction above it.
<h2>Choose a session style</h2>What to notice: This workshop-directory heading shows the level and shape. The official lab requires its own section wording.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
Requirement 8Explain the choices before listing them
UNDERSTAND THE IDEA
A short paragraph can explain how a section’s choices differ before readers select a link. Its location matters: it belongs after that section heading and before the list of package options.
What you will do
Below the package heading, add a brief paragraph introducing the different travel packages.
<h2>Choose a session style</h2>
<p>Join a shared table or book an individual introduction.</p>What to notice: Heading, explanation and choices are separate elements in a deliberate reading order.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
Requirement 9Make the two package labels into list links
UNDERSTAND THE IDEA
A list groups related options, while an anchor makes each option actionable. The link should wrap the visible label inside its list item, rather than wrapping the whole unordered list or sitting outside the item.
What you will do
Create the required two-item unordered list. Use the exact option labels from the lab, and enclose each label in an anchor.
<ul>
<li><a href="/sessions/group">Shared craft table</a></li>
<li><a href="/sessions/solo">Individual introduction</a></li>
</ul>What to notice: Each li contains its own a element. These session labels and destinations are intentionally different from the travel lab.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
Requirement 10Name the itinerary section separately
UNDERSTAND THE IDEA
The destination gallery is a new major section, not another package item. Giving it a sibling h2 keeps the hierarchy clear and makes it easier to find when reading or navigating by headings.
What you will do
After the package list, add the second h2 using the itinerary-section text specified by the official lab.
<h2>Explore the studios</h2>What to notice: Place this heading after the closing ul tag so it is not accidentally another list item.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
Requirement 11Group every destination image with its caption
UNDERSTAND THE IDEA
A figure groups a self-contained visual with its caption. The caption describes the particular image, while the anchor makes that image clickable. Repeating that structure keeps three different destinations understandable.
What you will do
Create at least three figure elements. Each needs an anchor and a descriptive figcaption; keep each caption with its own destination image.
<figure>
<a href="/studios/ceramics"><!-- Studio image goes here. --></a>
<figcaption>A sunny ceramics studio with shared worktables.</figcaption>
</figure>What to notice: This is one incomplete studio-card pattern, not the lab’s completed three-destination gallery.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
Requirement 12Put a real, described image inside each destination link
UNDERSTAND THE IDEA
The image is the clickable content of the destination anchor. A valid src lets it load, while useful alt text describes its visual information. The figure caption and alternative text can complement each other without becoming a filename dump.
What you will do
Inside each of the three destination anchors, place an img with a valid image source and an appropriate alternative description. Use your own images or the optional sources from the lab.
<a href="/studios/ceramics">
<img src="/images/studio.webp" alt="Pottery wheels arranged around a bright studio">
</a>What to notice: The img is nested inside a. The caption remains in the figure, outside the link.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
Requirement 13Audit all five link destinations and new-tab behavior
UNDERSTAND THE IDEA
Repeated elements are easy to fix incompletely: two package links and three image links make five anchors to check. The official lab sets a common destination and new-tab requirement, so inspect all five rather than testing only the first card.
What you will do
Give every required anchor the destination and target value specified by freeCodeCamp. Open the preview links and check the official tests without replacing your original content with the example below.
<a href="https://example.org/workshops" target="_blank" rel="noopener noreferrer">Browse independent workshops</a>What to notice: This unrelated destination demonstrates the attributes. It is not the travel lab’s required URL.
Resources to explore
Read another explanation or experiment with examples before trying the official lab.
Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.
READY TO BUILD?
Keep the instructions beside the video.
Start the official lab in a new tab, play the walkthrough here, and pause to make each change yourself. Run freeCodeCamp’s checks before moving on. Write and check your project in the official freeCodeCamp editor.
An independent walkthrough by The Code Zone. Not affiliated with or endorsed by freeCodeCamp. The project and official tests belong to freeCodeCamp; the explanations and visual guide on this page are our companion material.