Html projects

Summarize this post with AI ChatGPT OR

10 HTML Projects for Beginners That Actually Teach You

HTML projects are the fastest way to turn HTML from something you have read about into something you can actually do. Reading about headings, lists, forms, and tables gives you the vocabulary; building ten small, finished pages gives you the instinct. After the first project you will know how a page is put together. After the fifth you will stop looking up the basic tags. After the tenth you will have a small portfolio of real pages — and, more importantly, the confidence to start the eleventh without a tutorial holding your hand.

This guide gives you ten HTML projects for beginners in learning order, from a one-page profile you can finish in twenty minutes to a multi-page documentation site that ties everything together. Every project is a complete, runnable HTML document: copy it into a file, open it in your browser, and it works. No build tools, no frameworks, no JavaScript required — a small amount of CSS is included inside each document so the page looks finished, and every line of it is explained where it matters. Each project ends with “make it yours” ideas so the same starter becomes your page, not a copy of mine.

Quick Takeaways

  • Build in order. Each of the ten HTML projects adds one or two new ideas to the ones before it — headings and links first, forms and tables in the middle, navigation and multi-page structure at the end.
  • Every project in this guide is a complete HTML document. Save it as an .html file, double-click it, and it opens in your browser. You never need a server while you are learning.
  • A project is finished when it works in the browser and you can explain every tag in it. If you cannot explain a tag, that is the one to look up — not a reason to skip the project.
  • The skills that repeat across all ten projects — semantic structure, headings in order, labelled forms, descriptive link text, and alt text on every image — are the same skills that professional developers are paid for.
  • Keep every finished project in one folder. By project ten you will have a portfolio folder you can show to anyone, and a personal library of patterns you will reuse for years.
  • HTML projects teach you faster than HTML exercises because a finished page has a purpose. A tribute page has a person to honour; a landing page has a visitor to convince. Purpose is what makes the tags stick.

Before You Start: Your Two Tools

You need exactly two things to build every project in this guide, and you already have both of them.

A text editor. Any plain-text editor works: Notepad on Windows, TextEdit on a Mac (switch it to plain-text mode first), or a code editor such as Visual Studio Code, which is free and the one most beginners settle on. Do not use a word processor such as Microsoft Word or Google Docs — they add invisible formatting that breaks HTML. A code editor helps because it colours the tags and highlights mistakes, but it is a convenience, not a requirement.

A web browser. Chrome, Firefox, Edge, or Safari — whichever you already use. To run a project, save the code in a file ending in .html (for example profile.html), then double-click the file. It opens in your browser as a real web page. When you change the code, save the file and refresh the browser tab. That save-and-refresh loop is the whole development workflow for everything in this guide.

One habit that will save you hours: save each project in its own file, in one folder called html-projects, with names that match the project — profile.html, tribute.html, recipe.html, and so on. Name images the same way (profile-photo.jpg), and keep them in the same folder so the file paths in the code stay simple. When a page later links to another page, the link is just the file name, because the files sit side by side.

How to read the code in this guide: every project is printed as one complete document, from <!DOCTYPE html> to </html>. The <style> block near the top is ordinary CSS that makes the page look decent — you do not need to understand every CSS rule to build the HTML, and the guide says so wherever a rule does something worth noticing. The HTML itself is the lesson. If a tag is new, the text before the code block introduces it; if a tag repeats from an earlier project, it is used without comment, because by then you already know it.

1. Personal Profile Page

Your first HTML project is a page about you. It is the simplest page on the list, and it is also the most useful: it teaches the skeleton every other project is built on — the document structure, a heading hierarchy, paragraphs, a list, a link, and an image. Everything else in this guide is this page with more ideas added.

What you will practise: the <!DOCTYPE html>, <html>, <head>, and <body> structure; headings from <h1> to <h3> in order; paragraphs; an unordered list; a link that opens in a new tab; and an image with alt text. You will also write your first <title> and your first meta description — the two tags every page needs before it can be found or shared.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="description" content="A short personal profile page built with plain HTML — headings, a list, a link, and a photo.">
  <title>Aisha Khan — Aspiring Web Developer</title>
  <style>
    body { font-family: Georgia, serif; max-width: 640px; margin: 2rem auto; padding: 0 1rem; line-height: 1.6; color: #222; }
    img { max-width: 180px; border-radius: 50%; display: block; }
    h1 { margin-bottom: 0.2rem; }
    .tagline { color: #555; margin-top: 0; }
  </style>
</head>
<body>
  <img src="aisha-photo.jpg" alt="Portrait of Aisha Khan smiling in front of a bookshelf">
  <h1>Aisha Khan</h1>
  <p class="tagline">Aspiring web developer, tea drinker, and beginner photographer.</p>

  <h2>About Me</h2>
  <p>Hi, I am Aisha. I started learning HTML in November 2026 because I wanted to build
  my own corner of the internet instead of renting space on someone else's platform.
  This page is my first project, and I built it entirely by hand.</p>

  <h2>Three Things I Am Learning</h2>
  <ul>
    <li>HTML — the structure of every web page</li>
    <li>CSS — the styling that makes structure beautiful</li>
    <li>Git — so I never lose a working version again</li>
  </ul>

  <h2>Find Me Online</h2>
  <p>See what I am reading on
  <a href="https://developer.mozilla.org/en-US/docs/Web/HTML" target="_blank" rel="noopener">MDN Web Docs</a>,
  the reference I check whenever a tag surprises me.</p>

  <p><small>Built with plain HTML. Last updated November 2026.</small></p>
</body>
</html>

Notice three details that are easy to miss on a first page. First, the headings run in order — one <h1> for the name, then <h2> for each section — and there is never a jump from <h1> straight to <h3>. Second, the link carries rel="noopener" because it opens in a new tab, which is the security attribute that stops the destination page reaching back into yours. Third, the image has real alt text that describes the photo, not a file name: a screen reader reads that text aloud, and a search engine uses it to understand the image.

Make it yours: replace Aisha with yourself and write the About section in your own words. Add a second page section — a short list of books you have read, or the three tools you use every day. Swap the photo for your own, and change the tagline until it sounds like you. When you are done, this file is the seed of project 6, your portfolio.

2. Tribute Page

A tribute page is the classic second project for a reason: it forces you to organise a longer page with semantic tags, and it gives you a subject worth writing about. Pick a person you admire — a scientist, an artist, a family member, a historical figure — and build the page their story deserves.

What you will practise: semantic sectioning with <main>, <section>, and <figure>; a captioned image with <figcaption>; a <blockquote> for a quotation; a timeline built from a description list or an ordered list; and a <footer> with a source link. This is also the project where heading order starts to matter for real, because a tribute page has enough sections for a broken hierarchy to show.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="description" content="A tribute to Dr. Fe del Mundo, the Filipino paediatrician who built a children's hospital from a bamboo hut.">
  <title>Tribute to Dr. Fe del Mundo</title>
  <style>
    body { font-family: Georgia, serif; max-width: 680px; margin: 2rem auto; padding: 0 1rem; line-height: 1.7; color: #222; }
    figure { margin: 1.5rem 0; text-align: center; }
    img { max-width: 100%; height: auto; }
    figcaption { font-size: 0.9rem; color: #555; margin-top: 0.5rem; }
    blockquote { border-left: 4px solid #c0392b; margin: 1.5rem 0; padding-left: 1rem; font-style: italic; }
  </style>
</head>
<body>
  <main>
    <h1>Dr. Fe del Mundo</h1>
    <p>The doctor who built a children's hospital out of a bamboo hut.</p>

    <figure>
      <img src="fe-del-mundo.jpg" alt="Black and white portrait of Dr. Fe del Mundo in a white coat">
      <figcaption>Dr. Fe del Mundo (1911–2011), founder of the Children's Medical Center in Quezon City.</figcaption>
    </figure>

    <section>
      <h2>Her Life in Brief</h2>
      <p>Fe del Mundo was a Filipino paediatrician who became the first woman admitted to Harvard Medical School.
      She returned to the Philippines during the Second World War, set up a hospice for children in a bamboo hut
      in the hills, and spent the next sixty years building it into a full children's hospital — while inventing
      the bamboo incubator that is still used in rural clinics today.</p>
    </section>

    <section>
      <h2>Timeline</h2>
      <ol>
        <li><strong>1911</strong> — Born in Manila, Philippines.</li>
        <li><strong>1933</strong> — Graduates from the University of the Philippines College of Medicine.</li>
        <li><strong>1936</strong> — Admitted to Harvard Medical School, the first woman and first Asian to be accepted.</li>
        <li><strong>1941</strong> — Opens a children's hospice in a bamboo hut during the war.</li>
        <li><strong>1957</strong> — Founds the Children's Medical Center in Quezon City.</li>
        <li><strong>2011</strong> — Dies aged 99, still seeing patients in her nineties.</li>
      </ol>
    </section>

    <section>
      <h2>In Her Own Words</h2>
      <blockquote>
        <p>"I am not afraid of hard work. I am afraid of a life where I did nothing for others."</p>
      </blockquote>
    </section>

    <footer>
      <p>Read more on
      <a href="https://en.wikipedia.org/wiki/Fe_del_Mundo" target="_blank" rel="noopener">Wikipedia</a>.
      Built as a learning project with plain HTML.</p>
    </footer>
  </main>
</body>
</html>

The new ideas here are structural. <main> marks the page’s central content so assistive technology can jump straight to it. <figure> groups an image with its caption, which is the correct way to pair the two — a paragraph underneath an image is not the same thing. The timeline is an ordered list because the order matters: the dates only make sense in sequence. And the <blockquote> is a real quotation, not just italic text — browsers and search engines treat it as quoted material, which is exactly what it is.

Make it yours: choose your own person and write the timeline from real research, not from memory — checking three dates teaches you more about the subject than copying a paragraph does. Add a second image, or a “Why I admire her” section in your own words. If your subject is a living person, keep the facts verifiable and the tone respectful; a tribute page is a public document, even when only you read it.

3. Recipe Page

A recipe page looks simple, and that is the point: it is the project that teaches lists and tables properly, because a recipe is nothing but lists and a table. Ingredients are an unordered list (order does not matter), steps are an ordered list (order is everything), and the nutrition facts are a table (rows and columns, not a list pretending to be one).

What you will practise: <ul> and <ol> used for their real meanings; a <table> with <thead>, <tbody>, <th>, and <td>; the <time> element for cooking times; and a definition-style layout for the recipe facts at the top. You will also write your first page where the same information appears in two forms — the ingredients list and the nutrition table — and keeping both accurate is a real-world skill.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="description" content="A simple lentil soup recipe page: ingredients, step-by-step method, and nutrition facts in a table.">
  <title>Simple Red Lentil Soup — Recipe</title>
  <style>
    body { font-family: Georgia, serif; max-width: 640px; margin: 2rem auto; padding: 0 1rem; line-height: 1.6; color: #222; }
    table { border-collapse: collapse; width: 100%; margin: 1rem 0; }
    th, td { border: 1px solid #999; padding: 0.5rem 0.75rem; text-align: left; }
    th { background: #f4f4f4; }
    img { max-width: 100%; height: auto; }
  </style>
</head>
<body>
  <h1>Simple Red Lentil Soup</h1>
  <p>A one-pot soup that takes 35 minutes, costs almost nothing, and freezes beautifully.
  Prep <time datetime="PT10M">10 minutes</time>, cook <time datetime="PT25M">25 minutes</time>,
  serves 4.</p>
  <img src="lentil-soup.jpg" alt="A bowl of red lentil soup with a swirl of yoghurt and fresh herbs">

  <h2>Ingredients</h2>
  <ul>
    <li>200 g red lentils, rinsed</li>
    <li>1 onion, finely chopped</li>
    <li>2 carrots, diced</li>
    <li>2 garlic cloves, crushed</li>
    <li>1 tsp ground cumin</li>
    <li>1 litre vegetable stock</li>
    <li>Juice of half a lemon</li>
    <li>Salt and black pepper, to taste</li>
  </ul>

  <h2>Method</h2>
  <ol>
    <li>Heat a little oil in a large pot over medium heat. Soften the onion and carrots for 5 minutes.</li>
    <li>Add the garlic and cumin and stir for 1 minute, until fragrant.</li>
    <li>Add the lentils and stock. Bring to the boil, then simmer for 20–25 minutes until the lentils are soft.</li>
    <li>Blend half the soup for a thick, creamy texture, then stir it back into the pot.</li>
    <li>Stir in the lemon juice, season with salt and pepper, and serve hot.</li>
  </ol>

  <h2>Nutrition (per serving)</h2>
  <table>
    <thead>
      <tr><th scope="col">Nutrient</th><th scope="col">Amount</th></tr>
    </thead>
    <tbody>
      <tr><td>Energy</td><td>285 kcal</td></tr>
      <tr><td>Protein</td><td>14 g</td></tr>
      <tr><td>Carbohydrate</td><td>42 g</td></tr>
      <tr><td>Fibre</td><td>9 g</td></tr>
      <tr><td>Fat</td><td>3 g</td></tr>
    </tbody>
  </table>

  <p><small>Recipe by Aisha Khan. Nutrition values are estimates for one serving of four.</small></p>
</body>
</html>

Two details deserve attention. The <time> element carries a machine-readable datetime attribute (PT25M means a period of 25 minutes) while showing human words on the page — search engines read the attribute and can show the cooking time in results. And the table headers use scope="col", which tells a screen reader that “Nutrient” labels the column below it. A table without scope is still a table, but a table with it is a table a blind visitor can actually navigate.

Make it yours: publish a recipe you actually cook. Add a “Tips” section with one thing that went wrong the first time you made it — that honesty is what makes a recipe page worth reading. Then build a second recipe page and link the two together with a “More recipes” list; you have just taken the first step toward project 10.

4. Contact and Survey Form

Every website eventually needs a form, and forms are where beginners discover that HTML is not just about displaying information — it is about collecting it. This project builds a contact form with the built-in validation browsers already provide, so you learn the form elements before you ever write a line of JavaScript.

What you will practise: the <form> element and its action and method attributes; <label> elements correctly tied to inputs with for and id; the input types that matter most — text, email, tel, radio, checkbox, select, and textarea; the required attribute; and the autocomplete tokens that let browsers fill fields correctly. You will also learn why a label is not optional decoration: clicking a label focuses its field, and a screen reader announces the label when the field is reached.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="description" content="A contact and reader survey form built with plain HTML — labelled fields, built-in validation, and accessible controls.">
  <title>Contact Me — Reader Survey</title>
  <style>
    body { font-family: Georgia, serif; max-width: 600px; margin: 2rem auto; padding: 0 1rem; line-height: 1.6; color: #222; }
    label { display: block; font-weight: bold; margin-top: 1rem; }
    input, select, textarea { width: 100%; padding: 0.5rem; margin-top: 0.25rem; font: inherit; box-sizing: border-box; }
    input[type="radio"], input[type="checkbox"] { width: auto; }
    fieldset { margin-top: 1rem; padding: 1rem; }
    button { margin-top: 1.5rem; padding: 0.75rem 1.5rem; font: inherit; cursor: pointer; }
  </style>
</head>
<body>
  <h1>Contact Me</h1>
  <p>Questions about these HTML projects, or a project of your own to show me? Fill in the form —
  every field with a star is required, and your browser checks the answers before sending.</p>

  <form action="/contact-thanks.html" method="post">
    <label for="name">Your name *</label>
    <input type="text" id="name" name="name" autocomplete="name" required>

    <label for="email">Email address *</label>
    <input type="email" id="email" name="email" autocomplete="email" required>

    <label for="topic">What is this about?</label>
    <select id="topic" name="topic">
      <option value="question">A question about a project</option>
      <option value="feedback">Feedback on this guide</option>
      <option value="showcase">I built something and want to share it</option>
      <option value="other">Something else</option>
    </select>

    <fieldset>
      <legend>How did you find this guide? *</legend>
      <label><input type="radio" name="source" value="search" required> Search engine</label>
      <label><input type="radio" name="source" value="friend"> A friend recommended it</label>
      <label><input type="radio" name="source" value="social"> Social media</label>
      <label><input type="radio" name="source" value="other"> Somewhere else</label>
    </fieldset>

    <label for="message">Your message *</label>
    <textarea id="message" name="message" rows="6" required></textarea>

    <label><input type="checkbox" name="newsletter" value="yes">
    Email me when a new project guide is published (about once a month).</label>

    <button type="submit">Send Message</button>
  </form>

  <p><small>This form is a learning exercise: the action points at a thank-you page that does
  not exist yet. In a real site it would point at your form handler or a form service.</small></p>
</body>
</html>

The most common beginner mistake with forms is writing inputs without labels — a placeholder is not a label, because it disappears the moment the user starts typing. Here every control has a real <label>, and the radio buttons are grouped inside a <fieldset> with a <legend>, which is how a screen reader announces “How did you find this guide?” before reading the four options. The type="email" input is doing quiet work too: the browser refuses to submit an address without an @, and a phone keyboard offers the @ key first. That is free validation, built into the tag.

Make it yours: point the form at a real destination. The simplest honest option for a beginner is a free form service (such as Formspree or Netlify Forms), which gives you an action URL to paste in — no server code needed. Then add one field of your own: a number input for “how many projects have you finished?” with min="0" and max="10", and watch the browser enforce the range for you.

5. Photo Gallery

A photo gallery is the project that teaches images properly. It looks like a simple page of pictures, but it is really an exercise in three skills: choosing the right image format and size, writing alt text that is genuinely useful, and letting the browser pick the right image for the visitor’s screen instead of forcing one huge file on everyone.

What you will practise: <figure> and <figcaption> again, this time as the repeating unit of the page; the srcset and sizes attributes so the browser can choose a smaller image on a phone; loading="lazy" so images below the fold do not slow down the first view; and descriptive alt text that says what is in the photo, not “image” or the file name. A little CSS grid turns the figures into a gallery; the CSS is five lines, and the guide explains each one.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="description" content="A simple HTML photo gallery: captioned photos, responsive images with srcset, and lazy loading.">
  <title>Street Corners — A Photo Gallery</title>
  <style>
    body { font-family: Georgia, serif; max-width: 900px; margin: 2rem auto; padding: 0 1rem; line-height: 1.6; color: #222; }
    .gallery { display: grid; grid-template-columns: repeat(auto-fill, minmax(260px, 1fr)); gap: 1.5rem; }
    figure { margin: 0; }
    img { width: 100%; height: auto; display: block; }
    figcaption { font-size: 0.9rem; color: #555; margin-top: 0.5rem; }
  </style>
</head>
<body>
  <h1>Street Corners</h1>
  <p>Twelve photographs from morning walks around my neighbourhood, taken between
  November 2025 and November 2026. Click any photo to see it full-size — the small
  version loads first, and the large version waits until you ask for it.</p>

  <div class="gallery">
    <figure>
      <a href="photos/market-large.jpg">
        <img src="photos/market-600.jpg"
             srcset="photos/market-600.jpg 600w, photos/market-1200.jpg 1200w"
             sizes="(max-width: 700px) 100vw, 300px"
             alt="Vegetable sellers arranging bright red tomatoes at a morning market stall"
             loading="lazy">
      </a>
      <figcaption>Morning market — the tomato stall sets up before sunrise.</figcaption>
    </figure>

    <figure>
      <a href="photos/baker-large.jpg">
        <img src="photos/baker-600.jpg"
             srcset="photos/baker-600.jpg 600w, photos/baker-1200.jpg 1200w"
             sizes="(max-width: 700px) 100vw, 300px"
             alt="A baker sliding a tray of flatbread into a clay oven"
             loading="lazy">
      </a>
      <figcaption>The bakery on Chestnut Street — flatbread at 6 a.m.</figcaption>
    </figure>

    <figure>
      <a href="photos/rain-large.jpg">
        <img src="photos/rain-600.jpg"
             srcset="photos/rain-600.jpg 600w, photos/rain-1200.jpg 1200w"
             sizes="(max-width: 700px) 100vw, 300px"
             alt="Rain on an empty street, reflections of shop signs in the wet pavement"
             loading="lazy">
      </a>
      <figcaption>Rain on Elm Street — the whole road becomes a mirror.</figcaption>
    </figure>
  </div>

  <p><small>All photographs by Aisha Khan. The gallery pattern repeats: add a new
  <code><figure></code> block for each photo, and the grid makes room for it.</small></p>
</body>
</html>

Three ideas in this project are worth understanding properly. First, srcset gives the browser two files — a 600-pixel version and a 1200-pixel version — and sizes tells it how wide the image will display; the browser then picks the smallest file that still looks sharp, which is the single biggest performance win on any image-heavy page. Second, loading="lazy" tells the browser not to download an image until the visitor scrolls near it, so a gallery of fifty photos loads as fast as a gallery of three. Third, each image sits inside a link to its full-size version, so the gallery works without JavaScript: click a photo, see it large, press back, and you are exactly where you left off.

Make it yours: build the gallery from your own photos — a holiday, your street, your cooking, your cat. Resize each photo to two widths (600 and 1200 pixels) with any free tool, and use the same file names as the example so the pattern is obvious. Then try removing loading="lazy" from one image and refreshing with your browser’s developer tools open: the difference in what loads first is the lesson.

6. Personal Portfolio

The portfolio pulls the first five projects together. It reuses the profile page as its introduction, the gallery’s grid for the work samples, and the contact form as its closing section — and it adds the one idea none of the earlier projects needed: navigation. A portfolio is a page a stranger judges in seconds, so structure and clarity matter more here than in any project so far.

What you will practise: a <header> with site navigation built from <nav> and an anchor list; in-page links that jump to sections by id; <section> elements with clear headings so the page reads as an outline; an <article> or two for individual projects; and a <footer> with contact details. You will also practise the discipline of linking to your own work: each portfolio item links to the project file you already built.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="description" content="Portfolio of Aisha Khan, beginner web developer — profile, selected HTML projects, and contact details.">
  <title>Aisha Khan — Portfolio</title>
  <style>
    body { font-family: Georgia, serif; max-width: 800px; margin: 0 auto; padding: 0 1rem; line-height: 1.6; color: #222; }
    header { border-bottom: 2px solid #c0392b; padding: 1rem 0; }
    nav ul { list-style: none; padding: 0; display: flex; gap: 1.5rem; }
    nav a { text-decoration: none; color: #c0392b; font-weight: bold; }
    .work { display: grid; grid-template-columns: repeat(auto-fill, minmax(220px, 1fr)); gap: 1.5rem; }
    .work article { border: 1px solid #ccc; padding: 1rem; }
    footer { border-top: 2px solid #c0392b; margin-top: 2rem; padding: 1rem 0; }
  </style>
</head>
<body>
  <header>
    <h1>Aisha Khan</h1>
    <p>Beginner web developer — learning in public, one project at a time.</p>
    <nav aria-label="Main navigation">
      <ul>
        <li><a href="#about">About</a></li>
        <li><a href="#work">Work</a></li>
        <li><a href="#contact">Contact</a></li>
      </ul>
    </nav>
  </header>

  <main>
    <section id="about">
      <h2>About Me</h2>
      <p>I started learning HTML in November 2026 and I have built ten projects since.
      I like pages that are fast, honest, and useful — and I am learning CSS next so
      the pages I build can be beautiful as well as correct.</p>
    </section>

    <section id="work">
      <h2>Selected Work</h2>
      <div class="work">
        <article>
          <h3><a href="tribute.html">Tribute Page</a></h3>
          <p>A tribute to Dr. Fe del Mundo — semantic HTML, timeline, and quoted text.</p>
        </article>
        <article>
          <h3><a href="recipe.html">Recipe Page</a></h3>
          <p>Red lentil soup — lists, a nutrition table, and machine-readable cooking times.</p>
        </article>
        <article>
          <h3><a href="gallery.html">Photo Gallery</a></h3>
          <p>Street Corners — responsive images with srcset and lazy loading.</p>
        </article>
      </div>
    </section>

    <section id="contact">
      <h2>Contact</h2>
      <p>The fastest way to reach me is the
      <a href="contact.html">contact form</a>, or email me directly at
      <a href="mailto:aisha@example.com">aisha@example.com</a>.</p>
    </section>
  </main>

  <footer>
    <p>© 2026 Aisha Khan. Built with plain HTML — no frameworks, no trackers.</p>
  </footer>
</body>
</html>

The navigation is the new skill, and it is simpler than it looks. Each menu link points at an id on the page — href="#work" jumps to the element with id="work" — which is the same mechanism that powers “back to top” links and table-of-contents links on long articles. The aria-label="Main navigation" on the <nav> element exists for screen-reader users: when a page has more than one navigation block, the label is how they tell them apart. And the portfolio items link to your real project files, which is the whole point of building in one folder — the links just work, because the files sit side by side.

Make it yours: this is the page to polish. Write the About section as if a hiring manager will read it, because one day one will. Replace the three sample projects with your three best, and write one honest sentence about what each one taught you — that sentence is what separates a portfolio from a file list. Then link this page from your profile page, and link back: two pages that link to each other are the beginning of a real website.

7. Product Landing Page

A landing page is a sales page with one job: convince a visitor to do one thing. It is the project that teaches you how HTML structure serves a goal, because every section exists to answer the next doubt in the visitor’s mind — what is this, why should I care, what does it cost, what do other people say, what happens if I am not sure. It is also the project where a pricing table earns its keep.

What you will practise: a hero section with a clear headline and a call to action; a features section built from a list of short, honest benefits; a <table> used for pricing, where rows and columns are the right shape for the data; testimonials in <blockquote>; and a <details> and <summary> FAQ that opens and closes without any JavaScript. You will also write your first call-to-action link that looks like a button, and learn why it should still be a link.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="description" content="Landing page for the Weekly HTML Practice Kit — 52 small projects, one per week, with solutions and checklists.">
  <title>Weekly HTML Practice Kit — Build One Small Page Every Week</title>
  <style>
    body { font-family: Georgia, serif; max-width: 720px; margin: 0 auto; padding: 0 1rem; line-height: 1.6; color: #222; }
    .hero { text-align: center; padding: 3rem 0 2rem; }
    .cta { display: inline-block; background: #c0392b; color: #fff; padding: 0.75rem 1.5rem; text-decoration: none; font-weight: bold; border-radius: 4px; }
    table { border-collapse: collapse; width: 100%; margin: 1rem 0; }
    th, td { border: 1px solid #999; padding: 0.75rem; text-align: left; }
    th { background: #f4f4f4; }
    blockquote { border-left: 4px solid #c0392b; margin: 1.5rem 0; padding-left: 1rem; font-style: italic; }
    details { border: 1px solid #ccc; padding: 0.75rem 1rem; margin-bottom: 0.5rem; }
    summary { font-weight: bold; cursor: pointer; }
  </style>
</head>
<body>
  <header class="hero">
    <h1>Build One Small Page Every Week</h1>
    <p>The Weekly HTML Practice Kit: 52 beginner projects, one per week, each with
    starter code, a solution, and a checklist — so you never stare at a blank file again.</p>
    <p><a class="cta" href="#pricing">Get the Kit — $19</a></p>
  </header>

  <main>
    <section>
      <h2>What You Get</h2>
      <ul>
        <li>52 projects, from a profile page to a full mini-site</li>
        <li>Starter code and a finished solution for every project</li>
        <li>A one-page checklist per project, so you know when it is done</li>
        <li>Lifetime updates — new projects added every quarter</li>
      </ul>
    </section>

    <section id="pricing">
      <h2>Pricing</h2>
      <table>
        <thead>
          <tr><th scope="col">Plan</th><th scope="col">Price</th><th scope="col">What is included</th></tr>
        </thead>
        <tbody>
          <tr><td>Starter</td><td>Free</td><td>First 5 projects, no solutions</td></tr>
          <tr><td>Full Kit</td><td>$19 once</td><td>All 52 projects, solutions, checklists, lifetime updates</td></tr>
          <tr><td>Classroom</td><td>$49 once</td><td>Everything in Full Kit, plus a licence for up to 30 students</td></tr>
        </tbody>
      </table>
    </section>

    <section>
      <h2>What Builders Say</h2>
      <blockquote>
        <p>"I finished the first five projects in a weekend. The checklists are the best
        part — I always knew exactly when a page was done."</p>
        <p>— Sara M., student, Lahore</p>
      </blockquote>
      <blockquote>
        <p>"I use the kit with my class. The projects are small enough to finish in one
        lesson and real enough that students show them to their families."</p>
        <p>— David O., teacher, Nairobi</p>
      </blockquote>
    </section>

    <section>
      <h2>Questions</h2>
      <details>
        <summary>Do I need to know any CSS or JavaScript?</summary>
        <p>No. Every project is plain HTML, and the small amount of CSS is included and explained.
        JavaScript appears only in the final five projects, and only as an optional extra.</p>
      </details>
      <details>
        <summary>What if I fall behind?</summary>
        <p>Nothing expires. The kit is yours forever, so a missed week is just a week you
        catch up on later. Most builders finish in six to nine months, not one year.</p>
      </details>
      <details>
        <summary>Can I get a refund?</summary>
        <p>Yes — within 30 days, no questions asked. Email us and we refund the full price.</p>
      </details>
    </section>
  </main>

  <footer>
    <p><a class="cta" href="#pricing">Get the Kit — $19</a></p>
    <p><small>Questions? Email <a href="mailto:hello@example.com">hello@example.com</a>.</small></p>
  </footer>
</body>
</html>

The <details> element is the quiet star of this project. It gives you a working FAQ accordion with zero JavaScript — the browser handles opening, closing, keyboard access, and screen-reader announcements for free. If you ever catch yourself reaching for a script to show and hide content, check first whether <details> already does it. And notice the pricing table: three plans, three prices, three feature lists — a table is the right element here because a visitor compares across rows, which is exactly what tables are for. A list of three “cards” would hide that comparison.

Make it yours: invent your own product — a recipe book, a study planner, a photo preset pack — and write the landing page for it. The exercise is in the writing, not the product: can you explain in one sentence what it is, in three bullets why it helps, and in one table what it costs? If you can, you have learned more about web writing than most working developers ever do.

8. Blog Article Page

A blog article page is the project that teaches semantic HTML at full strength. Headings, paragraphs, lists, and images you already know; this project adds the tags that say what each part of the page is — the article itself, the author byline, the publication date, the sidebar of related reading, and the footer with the copyright. Search engines and screen readers both use these tags to understand the page, which is why they matter far beyond appearance.

What you will practise: the <article> element for the post itself; the <time> element with a datetime attribute for the publication date; an <address> for the author; an <aside> for related articles; internal links that connect the article to other pages on your site; and a heading outline that reads like a table of contents. This is also the project where you first write a page that other pages link to, which is how a real site grows.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="description" content="Why I stopped copying code I did not understand — and what I do instead when a tutorial moves too fast.">
  <title>Stop Copying Code You Do Not Understand</title>
  <style>
    body { font-family: Georgia, serif; max-width: 680px; margin: 2rem auto; padding: 0 1rem; line-height: 1.7; color: #222; }
    .byline { color: #555; font-size: 0.95rem; }
    aside { border: 1px solid #ccc; padding: 1rem 1.25rem; margin: 2rem 0; background: #fafafa; }
    img { max-width: 100%; height: auto; }
  </style>
</head>
<body>
  <article>
    <header>
      <h1>Stop Copying Code You Do Not Understand</h1>
      <p class="byline">By <address style="display:inline;">Aisha Khan</address> ·
      <time datetime="2026-11-17">17 November 2026</time> · 5-minute read</p>
    </header>

    <img src="notebook.jpg" alt="An open notebook with handwritten HTML tags and arrows drawn in the margins">

    <p>For my first month of learning HTML, I copied every tutorial line by line. My pages worked,
    and I understood almost none of them. The day a copied page broke, I had no idea where to look —
    because I had never made a single decision about that page myself.</p>

    <h2>Copying Is Not Learning (But Typing Is)</h2>
    <p>Typing code you do not understand yet is still useful: your hands learn the shapes of tags,
    and your eyes learn what a complete document looks like. The mistake is stopping there. The
    learning starts in the minute after the copy works, when you change one thing and watch what
    happens.</p>

    <h2>The Three-Change Rule</h2>
    <p>After any tutorial, before moving on, make three changes of your own:</p>
    <ol>
      <li>Change the words — every heading and paragraph becomes yours.</li>
      <li>Change one piece of structure — add a section, or reorder two of them.</li>
      <li>Break one thing on purpose, then fix it — delete a closing tag and read the error.</li>
    </ol>
    <p>If you can do all three and the page still works, you did not copy the tutorial. You learned it.</p>

    <h2>What I Do Now</h2>
    <p>I still follow tutorials. But I build the project twice: once following along, and once from
    memory the next morning, with the tutorial closed. The second version is always messier — and
    it is the one I actually remember a week later.</p>

    <footer>
      <p>Filed under <a href="learning.html">Learning in Public</a>. Next in this series:
      <a href="interview-questions.html">the 30 HTML interview questions I am practising</a>.</p>
    </footer>
  </article>

  <aside>
    <h2>Keep Reading</h2>
    <ul>
      <li><a href="profile.html">My first project: a personal profile page</a></li>
      <li><a href="portfolio.html">All ten beginner HTML projects</a></li>
      <li><a href="https://allabouthtml.com/html-headings-hierarchy-seo/">HTML Headings H1 to H6: Hierarchy, SEO Rules, and Common Mistakes</a></li>
    </ul>
  </aside>
</body>
</html>

The <article> element tells a browser — and a search engine — that everything inside it is one self-contained piece of writing, which is why it also gets its own <header> and <footer>: a header and footer inside an article belong to the article, not to the page. The <time datetime="2026-11-17"> element is the same idea as the recipe’s cooking time: humans read “17 November 2026” and machines read the exact date. And the <aside> is deliberately outside the article, because related reading is related to the article, not part of it — that distinction is the whole reason the tag exists.

Make it yours: write one real article about your own learning — the tutorial that confused you, the bug that took an hour, the tag you finally understood. Publish it as a file next to your other projects and link it from your portfolio. A blog with one honest post beats a blog with ten copied ones, and this file is the template for every post that follows.

9. Event Invitation Page

An event page is a deadline-driven project: the information has to be findable in seconds, because the visitor is deciding whether to come. That pressure is the lesson. It teaches you to put the essential facts first — what, when, where — and to use a table for the schedule, because a schedule is the most table-shaped information a beginner will ever meet.

What you will practise: the <address> element for a real place; a schedule table with <th scope="row"> labelling the rows as well as the columns; a <details> element for the “what to bring” list so the page stays short; a mailto link for RSVPs; and an embedded map link that opens in a new tab. You will also practise writing for a scanner: short lines, clear headings, and no paragraph longer than three sentences.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="description" content="You are invited: a neighbourhood coding morning on Saturday 6 December 2026 — schedule, venue, and RSVP.">
  <title>Neighbourhood Coding Morning — 6 December 2026</title>
  <style>
    body { font-family: Georgia, serif; max-width: 640px; margin: 2rem auto; padding: 0 1rem; line-height: 1.6; color: #222; }
    .hero { text-align: center; padding: 2rem 0; border-bottom: 2px solid #c0392b; }
    table { border-collapse: collapse; width: 100%; margin: 1rem 0; }
    th, td { border: 1px solid #999; padding: 0.6rem 0.75rem; text-align: left; }
    th { background: #f4f4f4; }
    .cta { display: inline-block; background: #c0392b; color: #fff; padding: 0.75rem 1.5rem; text-decoration: none; font-weight: bold; border-radius: 4px; }
    details { border: 1px solid #ccc; padding: 0.75rem 1rem; margin: 1rem 0; }
    summary { font-weight: bold; cursor: pointer; }
  </style>
</head>
<body>
  <header class="hero">
    <h1>Neighbourhood Coding Morning</h1>
    <p>Three hours, one laptop each, and ten small web pages built before lunch.</p>
    <p><time datetime="2026-12-06T09:00">Saturday 6 December 2026, 9:00 a.m. – 12:00 p.m.</time></p>
    <p><a class="cta" href="mailto:hello@example.com?subject=RSVP%20Coding%20Morning">RSVP by Email</a></p>
  </header>

  <main>
    <section>
      <h2>Where</h2>
      <address>
        Riverside Community Hall<br>
        14 Willow Lane<br>
        <a href="https://maps.google.com/?q=Riverside+Community+Hall" target="_blank" rel="noopener">Open in Google Maps</a>
      </address>
      <p>Entry is free. Bring a laptop if you have one; we have five spare laptops for
      anyone who does not.</p>
    </section>

    <section>
      <h2>Schedule</h2>
      <table>
        <thead>
          <tr><th scope="col">Time</th><th scope="col">What happens</th></tr>
        </thead>
        <tbody>
          <tr><th scope="row">9:00</th><td>Doors open, tea and introductions</td></tr>
          <tr><th scope="row">9:30</th><td>Build your profile page (project 1 from this guide)</td></tr>
          <tr><th scope="row">10:30</th><td>Break — show your neighbour what you built</td></tr>
          <tr><th scope="row">10:45</th><td>Build a tribute page in pairs</td></tr>
          <tr><th scope="row">11:45</th><td>Show and tell: three volunteers present their pages</td></tr>
        </tbody>
      </table>
    </section>

    <details>
      <summary>What should I bring?</summary>
      <ul>
        <li>A laptop and charger, if you have one</li>
        <li>Nothing else — paper, pens, and Wi-Fi are provided</li>
        <li>Children are welcome; under-12s build with a parent</li>
      </ul>
    </details>

    <p><small>Organised by Aisha Khan. If you cannot come, please email so your seat
    (and your spare laptop) can go to someone on the waiting list.</small></p>
  </main>
</body>
</html>

The schedule table introduces scope="row": the time in the first cell labels the whole row, just as scope="col" labels a column. A screen-reader user moving across the “10:45” row hears “Time: 10:45, What happens: Build a tribute page in pairs” — without that attribute, they hear the time and the activity with no connection between them. And the RSVP link is a mailto: link with a pre-filled subject, which is a small courtesy that doubles your response rate: the visitor only has to write their name.

Make it yours: use this page for a real event — a study group, a birthday, a book club, a family dinner. Real dates and real addresses force you to get the details right, which is a different skill from writing placeholder text. Then, the day after the event, update the page with two photos and one sentence about how it went: a page that changes after the event is a page that teaches you maintenance, the skill every real website needs.

10. Multi-Page Documentation Site

The final project is not one page — it is five, and that is the whole lesson. Everything before this lived in a single file; a documentation site teaches you how pages relate to each other. The navigation you built in the portfolio becomes the spine of the site, the links become a real structure, and you learn the habit that separates a website from a pile of pages: every page links back to the home page, and every page links onward to the next one.

What you will practise: planning a small site before writing it — a list of pages and what each one covers; a shared navigation block copied onto every page; relative links between your own files; a home page that acts as a table of contents; and “previous / next” links at the bottom of each page, which are the simplest navigation pattern on the web and the one documentation sites have used for thirty years.

Start with the home page. The other four pages follow the same document pattern — one for each topic — so the guide shows the home page in full and the exact pattern for the rest.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta name="description" content="HTML Basics — a five-page documentation site for absolute beginners: tags, attributes, links, images, and forms.">
  <title>HTML Basics — Documentation for Beginners</title>
  <style>
    body { font-family: Georgia, serif; max-width: 680px; margin: 0 auto; padding: 0 1rem; line-height: 1.7; color: #222; }
    header { border-bottom: 2px solid #c0392b; padding: 1rem 0; }
    nav ul { list-style: none; padding: 0; display: flex; flex-wrap: wrap; gap: 1.25rem; }
    nav a { color: #c0392b; font-weight: bold; text-decoration: none; }
    nav a[aria-current="page"] { text-decoration: underline; }
    footer { border-top: 2px solid #c0392b; margin-top: 2rem; padding: 1rem 0; }
  </style>
</head>
<body>
  <header>
    <h1>HTML Basics</h1>
    <p>Five short pages that take you from your first tag to your first form.</p>
    <nav aria-label="Documentation pages">
      <ul>
        <li><a href="index.html" aria-current="page">Home</a></li>
        <li><a href="tags.html">Tags</a></li>
        <li><a href="attributes.html">Attributes</a></li>
        <li><a href="links-images.html">Links & Images</a></li>
        <li><a href="forms.html">Forms</a></li>
      </ul>
    </nav>
  </header>

  <main>
    <h2>Start Here</h2>
    <p>This is a documentation site in miniature — the same shape as the official
    documentation for every tool you will ever learn. Each page covers one idea,
    each page links to the next, and this page is the map.</p>

    <ol>
      <li><a href="tags.html"><strong>Tags</strong></a> — what a tag is, and the ten tags every page needs.</li>
      <li><a href="attributes.html"><strong>Attributes</strong></a> — the extra words inside a tag that change what it does.</li>
      <li><a href="links-images.html"><strong>Links & Images</strong></a> — connecting pages, and showing pictures properly.</li>
      <li><a href="forms.html"><strong>Forms</strong></a> — collecting information with labels, inputs, and buttons.</li>
    </ol>

    <h2>How to Use This Site</h2>
    <p>Read the pages in order the first time. After that, use the navigation at the top
    of every page to jump to the page you need — that is what it is for. Each page ends
    with a link to the next page, so you can also just keep reading forward.</p>
  </main>

  <footer>
    <p>HTML Basics — written by Aisha Khan, November 2026. Next page:
    <a href="tags.html">Tags →</a></p>
  </footer>
</body>
</html>

Each of the four content pages — tags.html, attributes.html, links-images.html, forms.html — copies the same <header> and navigation, changes the aria-current="page" marker to its own link, writes its one topic in the <main> element, and ends with a footer that links back to the home page and forward to the next page:

<footer>
  <p><a href="index.html">← Home</a> · Next page:
  <a href="attributes.html">Attributes →</a></p>
</footer>

The aria-current="page" attribute is a small thing with a big effect: it tells a screen reader “this is the page you are already on”, so the navigation is never a guessing game. And the discipline of copying the navigation onto every page — identical except for that one marker — is the discipline that, on a bigger site, becomes a template. When you eventually learn a static site generator or a server-side include, you will recognise this exact problem: one navigation, many pages, one source of truth.

Make it yours: document something you know — your grandmother’s recipes, the rules of a game you play, the bus routes in your town. Five pages is enough to feel like a real site and small enough to finish in a weekend. Then open the site’s home page, click every link, and fix anything that 404s: that link-checking pass is the last skill in this guide, and it is the one you will use on every site you ever build.

All Ten Projects at a Glance

#ProjectNew skillsTimeKeep building it by…
1Personal profile pageDocument structure, headings, lists, links, images20 minAdding sections about your reading and your tools
2Tribute pageSemantic sections, figure, blockquote, timeline45 minChoosing your own person and researching real dates
3Recipe pageLists with real meaning, tables, time element40 minPublishing a recipe you actually cook
4Contact and survey formLabels, input types, validation, autocomplete1 hourConnecting it to a real form service
5Photo gallerysrcset, sizes, lazy loading, figure captions1 hourPhotographing your own street or your own cooking
6Personal portfolioNavigation, anchor links, linking your own work1.5 hoursRewriting About for a hiring manager
7Product landing pageHero and CTA, pricing table, details FAQ2 hoursInventing your own product and selling it in words
8Blog article pageArticle, aside, byline, internal links1 hourWriting one honest post about your learning
9Event invitation pageSchedule table, address, mailto RSVP45 minInviting real people to a real event
10Multi-page documentation siteSite planning, shared navigation, prev/next links2–3 hoursDocumenting something you actually know

The times are honest estimates for a beginner working carefully, including the time spent reading the explanations — not racing. If a project takes you twice as long, that is not failure; that is the project doing its job. The only deadline that matters is finishing all ten, because the tenth project is where the first nine stop being separate exercises and start being one skill.

Frequently Asked Questions

1. Do I need to know CSS before starting these HTML projects?

No. Every project in this guide is complete in plain HTML, and the small amount of CSS inside each document is included for you — you can copy it without understanding every rule. That said, you will enjoy the projects more if you learn a little CSS alongside them: even ten rules (fonts, colours, spacing, a max-width) transform a plain page into one you are proud to show. The honest order is HTML first, CSS second, and this guide is built for exactly that order. If a CSS rule in a project puzzles you, leave it alone for now and come back to it after your first CSS lesson — the HTML will still work without it.

2. What is the best first HTML project for a complete beginner?

The personal profile page, project 1. It is the shortest project in this guide, it uses only the tags you will use on every page you ever build, and it produces something personal — a page about you — which is more motivating than a page about a made-up company. If you have never written a line of HTML, start there, finish it in one sitting, and open it in your browser. The feeling of a page you built appearing on screen is the fuel for the other nine. Do not start with the portfolio or the documentation site: both of them assume you have already built the smaller pages they link to.

3. How long does it take to finish all 10 HTML projects?

About ten to twelve hours of focused work, spread over two to four weeks at a comfortable pace — roughly one project every two or three days. The table above gives an honest estimate per project, from twenty minutes for the profile page to two or three hours for the documentation site. The time that matters is not the typing time but the thinking time: reading a section twice, breaking something and fixing it, and rewriting a paragraph until it sounds like you. A project you rush through in half the estimated time teaches you half as much. If you can only spare thirty minutes a day, do one project a week and finish in ten weeks — the order matters more than the speed.

4. Can I build these HTML projects without JavaScript?

Yes — all ten are built with HTML and a little CSS only, and that is deliberate. JavaScript is a powerful tool, but it is not required for any page in this guide, including the FAQ sections (which use the <details> element) and the photo gallery (which uses links to full-size images instead of a lightbox script). Learning HTML properly first means that when you do start JavaScript, you will be adding behaviour to pages whose structure you already understand, instead of using scripts to paper over structure you never learned. The right time to add JavaScript is after project 10, when you have ten working pages to improve.

5. What should I learn after finishing these HTML projects?

CSS, then a second round of HTML. Learn CSS properly — selectors, the box model, flexbox, and grid — and then rebuild your favourite project from this guide with real styling: the portfolio is the best candidate, because a styled portfolio is the page that gets you noticed. After that, revisit the HTML itself: semantic tags you skipped, accessibility testing with a screen reader, and the validation skills from the debugging guide. And keep building: a second set of ten projects, chosen by you, teaches more than any course. The moment you can look at a website, sketch its structure on paper, and build a simplified version of it in an afternoon, you are no longer a beginner.

Conclusion

Ten HTML projects, ten finished pages, and one skill that none of the tutorials could give you on their own: the ability to start from a blank file. The profile page taught you the skeleton. The tribute and recipe pages taught you lists, tables, and semantic structure. The form taught you to collect information, the gallery taught you to handle images properly, and the portfolio taught you to link your work together. The landing page taught you to write for a goal, the article page taught you to write for a reader, the event page taught you to write for a deadline, and the documentation site taught you to think in pages instead of files.

None of those lessons required a framework, a build tool, or a line of JavaScript — just a text editor, a browser, and the willingness to finish things. Keep the folder with all ten projects. Open it the next time someone asks what you have built, and the next time you sit down to learn CSS, start from the portfolio page in it: you already own the structure, and now you get to make it beautiful.

Next, turn the confidence these projects gave you into interview answers: the 30 HTML interview questions guide takes the tags you just used — forms, tables, semantic elements, attributes — and shows you how to explain them out loud, with code examples, the way an interviewer will ask. Build first, explain second, and the explanations will be easy because the pages are already yours.

Related Articles You’ll Love

No comment

Leave a Reply

Your email address will not be published. Required fields are marked *