Responsive Web Design / HTML / Basic HTML
Build a Recipe PageA collection to gather. A sequence to follow.
Watch Rob build the project, understand what each part is for, then work through the official freeCodeCamp lab at your own pace.
Think Like a Developer Guided Practice
Think like a programmer: build a craft-workshop guide in eight checked stages. Practice the same document, heading, list and image patterns in a different scenario, then apply your plan to the official recipe lab. Completing this practice does not complete the official lab.
The mini-lesson opens in a new tab. Your own code carries forward; each step has a focused check and an optional hint.
Think Like a Developer Guided Practice(opens in a new tab)8 steps · Saved work · Instant feedback
ORIGINAL WALKTHROUGH · 18:31
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 Recipe Page recording accompanies this lab. Use the current freeCodeCamp instructions for the exact requirements. The reading-guide groups below are not video timestamps.
THE IDEA BEHIND THE BUILD
What this lab teaches
A recipe gives a beginner a practical reason to choose different HTML elements. The dish needs a name and a short introduction. Ingredients tell readers what to gather, while instructions tell them what to do and in what order. An image adds context when its source and description are useful.
Build the document in layers rather than treating the recipe as one long paragraph. Separate browser metadata from visible content, give the page and its sections appropriate headings, then choose a list type for each kind of information. Write your own recipe and use the official checks to review the required structure.
Separate metadata from content
Keep the tab title and character encoding in head, and put the visible recipe in body.
Choose lists for their meaning
Use bullets for ingredients and an ordered list for a method whose sequence matters.
Make the page understandable
Use a clear heading hierarchy, an introductory paragraph and descriptive alternative text.

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.
Set up the document
Check the doctype, document language, metadata and body before filling the page.
Check your understanding: You can distinguish the browser-tab title from the visible recipe heading.
Explore requirement 1Introduce the recipe and ingredients
Name the dish once, write an introduction, and group the ingredients beneath their heading.
Check your understanding: The ingredient list has at least four separate list items under the correct heading.
Explore requirement 5Explain the method and add an image
Write the ordered method under its own heading, then connect an image with useful alternative text.
Check your understanding: The method has at least four steps in order, and the image has a real source and a meaningful description.
Explore requirement 9SEE HOW THE PARTS FIT
A page with a clear structure
This short workshop-setup example compares a collection of supplies with a sequence of actions. It is intentionally incomplete and uses another subject so you can understand the pattern without copying a finished recipe solution.
<!-- A collection: the order is not a procedure. -->
<ul>
<li>Work gloves</li>
<li>Safety glasses</li>
</ul>
<!-- A sequence: the actions have an order. -->
<ol>
<li>Clear the work surface.</li>
<li>Check the tools.</li>
</ol>headBrowser metadata and character encodingh1 + pThe dish name and introductionh2 + ulIngredients to gatherh2 + olInstructions to followimg + altA useful visual and its descriptionThree things to pay attention to
The two lists have different jobs
A numbered ingredient list or bulleted procedure can still render, but it misses the intended structure and may fail the lab checks.
Exact headings and minimums matter
The lab asks for Ingredients and Instructions, at least four items in each list, and exactly one h1. Check these details against the current official instructions.
An image needs more than an appearance
Confirm that the source loads and the alternative text describes the image. A filename alone rarely gives readers enough context.
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 1Use modern HTML document mode
UNDERSTAND THE IDEA
A doctype tells the browser how to interpret the document. The modern HTML declaration selects standards mode, which makes later layout behavior more predictable. It is a declaration, not a visible heading.
What you will do
Start your document with the HTML doctype before the root element.
<!DOCTYPE html>
<!-- Document content follows the declaration. -->What to notice: The declaration begins with an exclamation mark and has no closing tag. It does not display text in the 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 2Identify the document language
UNDERSTAND THE IDEA
The root element wraps the page. Its language attribute describes the language of the text to browsers, screen readers and translation tools. This is about human language, not the programming language.
What you will do
Use an html root element with its lang attribute set to en.
<html lang="fr">
<!-- Content written in French belongs in this example. -->
</html>What to notice: This French-language example illustrates the attribute. Your lab requires English, so use the value specified by the official instructions.
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 3Describe the page in its head
UNDERSTAND THE IDEA
The head holds metadata rather than the visible recipe. A useful title helps a reader identify the browser tab, while the UTF-8 declaration tells the browser how the document text is encoded.
What you will do
Inside head, include a title naming your recipe and a meta declaration with charset set to UTF-8.
<head>
<meta charset="UTF-8">
<title>Community workshop schedule</title>
</head>What to notice: The browser-tab title and the visible page heading have separate locations and jobs. The schedule title is an analogy, not recipe content to copy.
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 4Give visible content a body
UNDERSTAND THE IDEA
The body contains the material a visitor reads and interacts with. Keeping metadata in head and visible content in body gives the browser a clear document structure to work with.
What you will do
Include a body element and put the visible recipe content inside it.
<body>
<!-- Visible workshop information would go here. -->
</body>What to notice: Body belongs inside html, after head. Putting visible content inside head does not make it page metadata.
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 5Name the recipe once
UNDERSTAND THE IDEA
A main heading tells a visitor what the page is about. In this lab, one h1 names the dish; later h2 headings organize its parts. Heading levels express a hierarchy rather than a font-size preference.
What you will do
Use exactly one h1 containing the name of your recipe.
<h1>Weekend repair workshop</h1>What to notice: This example names a different kind of page. Your h1 should name your own recipe, and the lab expects just one h1.
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 what the reader will make
UNDERSTAND THE IDEA
A short introduction gives the recipe context before the lists begin. A paragraph is appropriate for a complete thought; a heading is appropriate for a section name. These elements convey different kinds of content.
What you will do
Put a paragraph introducing your recipe below the main heading.
<h1>Weekend repair workshop</h1>
<p>Bring one small household item and learn a safe repair process.</p>What to notice: The paragraph follows the heading in document order. Write an introduction for your own dish rather than copying the workshop text.
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 ingredients section
UNDERSTAND THE IDEA
A section heading lets readers scan for the information they need. The lab uses a second-level heading for the ingredient list, beneath the single main page heading. Its exact wording is part of the lab checks.
What you will do
Add an h2 with the exact text Ingredients before the first list.
<h2>Supplies</h2>
<!-- A supply list would follow this heading. -->What to notice: Supplies illustrates the role of a section heading. Use Ingredients for the actual lab requirement, including its spelling.
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 8Group ingredients in an unordered list
UNDERSTAND THE IDEA
Ingredients are a collection of things to gather, so their list order does not describe a sequence of actions. An unordered list contains list-item elements, keeping each ingredient a distinct item.
What you will do
Under the first h2, add a ul with at least four li elements describing the ingredients.
<ul>
<li>Safety glasses</li>
<li>Work gloves</li>
</ul>What to notice: This two-item equipment list demonstrates nesting only. Your ingredient list needs at least four items, and each needs its own li.
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 9Introduce the instructions section
UNDERSTAND THE IDEA
The method is a second section alongside the ingredients, so both section headings use h2. Consistent heading levels help a reader understand that neither section is a subtopic of the other.
What you will do
Add the second h2 with the exact text Instructions before the ordered list.
<h2>Setup procedure</h2>
<!-- The numbered procedure would follow. -->What to notice: Setup procedure is an analogous heading. The actual recipe lab checks for Instructions as the second h2.
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 10Put the method in a meaningful order
UNDERSTAND THE IDEA
A procedure depends on sequence: preparing equipment usually comes before using it. An ordered list expresses that sequence, while the browser generates the item numbering for you.
What you will do
Under the second h2, use an ol containing at least four li elements with the recipe steps in order.
<ol>
<li>Clear the work surface.</li>
<li>Put on the safety equipment.</li>
</ol>What to notice: Do not type list numbers into a paragraph. This short setup example shows the pattern; your recipe needs at least four actual method items.
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 11Connect a useful image and description
UNDERSTAND THE IDEA
An image source locates the file, while alternative text describes the useful information the image contributes. Readers who cannot see or load the image still need to understand its role in the recipe.
What you will do
Include an img with a valid src and alt text describing the image. You may use the optional image supplied in the official lab.
<img src="/images/workbench.jpg"
alt="Safety glasses and gloves laid out on a clear workbench">What to notice: This fictional local image path illustrates the attributes and will not load unless that file exists. Use an actual image URL for your recipe and describe what it shows.
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.