Responsive Web Design / HTML / Basic HTML
Debug Camperbot's Profile PageInspect the tag. Keep the content.
Watch Rob build the project, understand what each part is for, then work through the official freeCodeCamp lab at your own pace.
ORIGINAL WALKTHROUGH · 6:39
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 6:39 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
This first debugging lab is about reading what is already there. Camperbot’s profile has a main heading, two short paragraphs and section headings, but several tag names and one closing tag are wrong. You can repair the structure without redesigning the page or replacing the supplied words.
Make one focused repair at a time. Identify the element’s intended role, choose its standard name, compare its opening and closing tags, and rerun the checks. A page that displays text is not automatically a correctly structured page.
Read HTML as a structure
Distinguish a real heading or paragraph element from an invented tag that merely contains text.
Fix both ends of an element
Match the opening and closing names and place the closing slash correctly.
Keep a repair small
Preserve correct content and use a failing check to guide the next edit.

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.
Repair the section heading
Find the invented second-level heading and identify its intended role.
Check your understanding: Can you explain why a visible heading-like label is not enough?
Explore requirement 1Repair the paragraphs
Turn both text passages into genuine paragraphs while keeping their content.
Check your understanding: Are there exactly two paragraphs with their original words?
Explore requirement 2Close and verify
Correct the lower heading’s closing syntax, then review the five intended elements.
Check your understanding: Do the checks pass without adding extra markup to hide the problem?
Explore requirement 3SEE 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.
<h2>Meet the museum guide</h2>
<p>I help visitors explore the science museum.</p>
<h3>Favorite discoveries</h3>h1The existing page heading staysh2A real section headingpTwo independent paragraphsh3A correctly closed lower headingThree things to pay attention to
Unknown tags can still show text
A browser displaying the words does not make heading2 or pp standard elements. Check the element name itself.
Closing syntax changes the tree
A slash in the wrong place can leave the heading open and pull later content into it.
Do not replace a repair with a rewrite
The original main heading and text are part of the lab’s checks. Keep correct content while repairing the markup.
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 1Choose the real second-level heading element
UNDERSTAND THE IDEA
A browser can display text inside an unknown element without treating it as a heading. The element name is part of the meaning: a level-two heading introduces a section under the main page heading.
What you will do
Find the invented heading element in the lab. Replace both its opening and closing tag names with the standard second-level heading tag, keeping the existing heading text.
<h2>Meet the museum guide</h2>What to notice: The opening and closing names match. This example uses a different heading from Camperbot’s 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 2Put each paragraph inside a paragraph element
UNDERSTAND THE IDEA
Ordinary prose belongs in a paragraph rather than an invented tag. Fixing both ends of the element keeps the browser’s document tree predictable and makes the text a real paragraph for tools that inspect the page.
What you will do
Repair both invented paragraph elements without rewriting their text or adding extra paragraphs. Keep the main heading and section headings.
<p>I help visitors explore the science museum.</p>What to notice: Use one p element for one paragraph. The text in the official lab must remain the text the lab supplies.
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 3Repair the closing tag and review the whole profile
UNDERSTAND THE IDEA
A closing tag puts the slash before the element name. Moving it to the other end can leave the heading open and make later text appear inside the wrong element, even when the page looks partly readable.
What you will do
Inspect the lower heading’s closing syntax. Fix that syntax, then check that the page still contains its original main heading, one second-level heading, one third-level heading, and two paragraphs.
<h3>What I enjoy</h3>
<p>I like explaining how inventions work.</p>What to notice: The closing tag is </h3>, not an opening tag with a slash at the end. This is a separate museum-profile example.
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.