Intermediate project: build a small business website
Build a three-page business site with semantic structure, a menu table, a validated contact form and a map.
In this lesson you will
- Plan and build a three-page site
- Combine semantic layout, tables and forms
- Add a validated, accessible contact form
- Test and prepare the site to publish
About 20 minutes
Your second project: a business site
In lesson 10 you built a personal page. Now you will build something clients actually pay for: a small business website with a homepage, a menu page and a contact page with a working form layout. We will use Priya’s Bakery again, but you can swap in a business that matters to you, such as a gym, a tutoring service or a photography studio. Choose something real. It makes the work easier to finish and gives you something to show.
What the finished site contains
- Three pages that link to each other:
index.html,menu.htmlandcontact.html. - Semantic structure on every page: header with nav, main, footer.
- A hero section, three feature articles and an image with a caption on the homepage.
- A menu page with a table of items and prices.
- A contact page with a validated form, a map embed and an accessible layout.
Step 1: Create the folder and plan
- Create a folder named
bakery. Inside it make a folderimages. - Create three empty files:
index.html,menu.htmlandcontact.html. - On paper, list what goes on each page and which words the navigation links will use.
- Gather two or three images and save them in the images folder with short lower-case names.
Step 2: Build the shared skeleton
All three pages share the same header, navigation and footer. Start with the homepage and copy the skeleton into the other two later.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Priya's Bakery | Fresh bread and cakes</title>
<meta name="description" content="Handmade sourdough, cakes and pastries baked every morning.">
</head>
<body>
<a class="skip" href="#content">Skip to main content</a>
<header>
<a href="index.html">Priya's Bakery</a>
<nav aria-label="Main">
<a href="index.html" aria-current="page">Home</a>
<a href="menu.html">Menu</a>
<a href="contact.html">Contact</a>
</nav>
</header>
<main id="content">
<!-- page content -->
</main>
<footer>
<p>© 2026 Priya's Bakery. 12 Mall Road, Lahore.</p>
</footer>
</body>
</html>
Step 3: The homepage content
<section>
<h1>Bread worth waking up for</h1>
<p>Handmade sourdough, celebration cakes and pastries, baked fresh every morning.</p>
<a href="menu.html">See the menu</a>
</section>
<section>
<h2>What we bake</h2>
<article>
<h3>Sourdough</h3>
<p>Slow-fermented for two days.</p>
</article>
<article>
<h3>Celebration cakes</h3>
<p>Made to order and decorated by hand.</p>
</article>
<article>
<h3>Pastries</h3>
<p>Buttery, flaky and gone by noon.</p>
</article>
</section>
<figure>
<img src="images/loaf.jpg" alt="Golden sourdough loaf on a wooden board" width="800" height="500">
<figcaption>Our signature loaf, out of the oven at 5 a.m.</figcaption>
</figure>
Step 4: The menu page
A menu is real tabular data: items, sizes and prices. That is exactly what tables are for, so use the table skills from lesson 8, with a caption and header cells.
<h1>Our menu</h1>
<table>
<caption>Prices in Pakistani rupees</caption>
<thead>
<tr><th scope="col">Item</th><th scope="col">Size</th><th scope="col">Price</th></tr>
</thead>
<tbody>
<tr><th scope="row">Sourdough loaf</th><td>Regular</td><td>450</td></tr>
<tr><th scope="row">Chocolate cake</th><td>1 kg</td><td>2,400</td></tr>
<tr><th scope="row">Almond croissant</th><td>Single</td><td>220</td></tr>
</tbody>
</table>
Step 5: The contact page
This is where forms, validation, embeds and accessibility meet.
<h1>Order a cake or say hello</h1>
<form action="/contact" method="post">
<fieldset>
<legend>Your details</legend>
<label for="name">Name (required)</label>
<input type="text" id="name" name="name" autocomplete="name" required>
<label for="mail">Email (required)</label>
<input type="email" id="mail" name="mail" autocomplete="email" required>
<label for="phone">Phone</label>
<input type="tel" id="phone" name="phone" autocomplete="tel">
</fieldset>
<fieldset>
<legend>Your request</legend>
<label for="type">What are you after?</label>
<select id="type" name="type">
<option value="cake">A custom cake</option>
<option value="bread">Regular bread order</option>
<option value="other">Something else</option>
</select>
<label for="date">Date needed</label>
<input type="date" id="date" name="date">
<label for="msg">Message</label>
<textarea id="msg" name="message" rows="5" maxlength="500"></textarea>
</fieldset>
<button type="submit">Send message</button>
</form>
<h2>Find us</h2>
<iframe title="Map showing Priya's Bakery" src="https://www.openstreetmap.org/export/embed.html" width="600" height="350" loading="lazy"></iframe>
Step 6: Test like a professional
- Open each page in the browser and click every link, including the back and forth between pages.
- Check that every image loads and has the right alt text.
- Submit the form with fields empty, then with a bad email, to confirm validation.
- Press Tab from the top of each page and confirm the order makes sense.
- Paste the code into the W3C validator and fix the errors.
- Resize the window narrow to see how it behaves on a phone.
Practise the heart of the project. Build a small contact form with a required name, a required email, a select with two options and a submit button. Keep all labels connected.
<form>
<!-- the contact form -->
</form>
Follow the fieldset pattern: label, input with id and name, then required where needed.
<form>
<label for="n">Name</label>
<input type="text" id="n" name="name" required>
<label for="e">Email</label>
<input type="email" id="e" name="email" required>
<label for="t">Topic</label>
<select id="t" name="topic">
<option>Order</option>
<option>Question</option>
</select>
<button type="submit">Send</button>
</form>
Replace the bakery with a real business, add your own photos, then publish the site for free on a service such as GitHub Pages or Netlify. A live link is far more convincing on a profile or CV than a folder on your computer.
Stretch goals to make the project yours
- Add a fourth page called
about.htmlwith a photo of the owner and a short story, usingfigureandfigcaption. - Add a testimonials section to the homepage built from
blockquoteelements with the customer’s name insidecite. - Add an
asideto the menu page that lists allergy information. - Add a downloadable PDF menu with a clear link such as “Download the menu (PDF, 200 KB)”.
- Check the page title and meta description of all three pages. Each should be unique and describe its own page.
When you finish, read through your code one more time as if you were a stranger. Could they understand the structure in a minute? If so, you have built something professional. The advanced lessons next will take it further with data attributes, SEO tags, performance and modern HTML features.
Check what you learned
Five quick questions. Pick an answer and you will see straight away whether it is right and why.
Which elements should repeat on every page of the site?
- A header with navigation and a footer
- Only the title
- Nothing
- The same h1 on every page
Shared navigation and footer give the site a consistent structure.
Why use a table for the menu?
- Tables make it look good
- A menu is real tabular data of items and prices
- Tables are required for prices
- They load faster
Tables are meant for data arranged in rows and columns.
What does aria-current="page" on a nav link do?
- Hides the link
- Tells assistive technology it is the current page
- Opens a new tab
- Adds colour
It marks the link for the page the visitor is on.
Which fields on the contact form should be required?
- All of them
- Name and email
- None
- Only the message
Ask for what you need to reply, and keep optional things optional.
What is the best way to check the finished site?
- Trust it works
- Click every link, test the form, use the keyboard and run the validator
- Only look at the homepage
- Ask a friend to guess
Careful testing finds the problems before your visitors do.
Summary
- Plan, build the skeleton, add content, then test.
- Share one header, nav and footer across pages.
- Combine tables, forms, figures and embeds in one project.
- Publishing the site gives you a real link to show.
Questions
Can I use a different business for this project?
Yes. Any business works, as long as it has about three pages of real content.
Where does the form data go?
The form needs a receiver. For a real site use a form service, a plugin or a server script. The HTML itself is complete either way.
How do I publish the finished site?
Free hosts such as GitHub Pages or Netlify accept a folder of HTML files and give you a public address.
