BeginnerLesson 10 of 306 min read

Beginner project: build a personal profile page

Combine headings, lists, tables, images and links in a complete profile page, then check it like a professional.

In this lesson you will

  • Plan a page from an outline
  • Combine headings, lists, tables, images and links
  • Validate and test your work
  • Finish the beginner level with a real page

About 20 minutes

What you will build

It is time to combine everything from lessons 1 to 9 into one real page: a personal profile page you could show to a friend, a teacher or a future client. There is no new theory here. The goal is to practise planning, writing, and checking a page from start to finish, which is how real work feels.

  • A heading with your name and a short introduction
  • A photo with proper alt text
  • A list of skills and a numbered learning plan
  • A small table of goals
  • Links to other pages and to your email

Step 1: Plan before you type

Professionals sketch first. Take two minutes and write the outline on paper or in a comment. A plan prevents the most common beginner problem, which is starting to type with no idea where the page is going.

Page: Priya Sharma - Learner
  h1 name
  intro paragraph
  h2 About me      (paragraphs + photo)
  h2 My skills     (unordered list)
  h2 My plan       (ordered list)
  h2 Goals         (table)
  h2 Contact       (links)

Step 2: Write the skeleton

  1. Create a folder profile and a file index.html.
  2. Type the HTML5 skeleton from lesson 3, with a clear title and description.
  3. Add the h1 and the outline headings with empty paragraphs. Save and view. A page with only headings should already read like a document.

Step 3: Fill in the content

Now add real content under each heading. Use the model below as a guide, then replace everything with your own words and details. Use the editor to try it live.

Complete the page: add a second skill to the list, add a third step to the plan, add one more row to the goals table, and change the name to yours.

<h1>Priya Sharma</h1>
<p><strong>Learner</strong> and future web developer.</p>

<h2>My skills</h2>
<ul>
  <li>Typing</li>
</ul>

<h2>My plan</h2>
<ol>
  <li>Finish the HTML course</li>
  <li>Learn CSS</li>
</ol>

<h2>Goals</h2>
<table border="1" cellpadding="6">
  <tr><th>Goal</th><th>Deadline</th></tr>
  <tr><td>Build a portfolio</td><td>June</td></tr>
</table>

<h2>Contact</h2>
<p><a href="mailto:priya@example.com">Email me</a></p>

Copy an existing <li> line and change the words. For the table copy a whole <tr>...</tr>.

<h1>Your Name</h1>
<p><strong>Learner</strong> and future web developer.</p>

<h2>My skills</h2>
<ul>
  <li>Typing</li>
  <li>Problem solving</li>
</ul>

<h2>My plan</h2>
<ol>
  <li>Finish the HTML course</li>
  <li>Learn CSS</li>
  <li>Build three projects</li>
</ol>

<h2>Goals</h2>
<table border="1" cellpadding="6">
  <tr><th>Goal</th><th>Deadline</th></tr>
  <tr><td>Build a portfolio</td><td>June</td></tr>
  <tr><td>Publish online</td><td>July</td></tr>
</table>

<h2>Contact</h2>
<p><a href="mailto:priya@example.com">Email me</a></p>

Step 4: Add a photo and a second page

Add an image from your images folder with meaningful alt text and dimensions (lesson 6). Then create projects.html with a heading and a list of things you plan to build. Link between the two pages using relative links in both directions (lesson 5). Visiting every page from every other is the quickest way to test navigation.

<img src="images/me.jpg" alt="Priya smiling at her desk" width="300" height="300">
<p><a href="projects.html">See my projects</a></p>

Step 5: Check your work

Real developers always run a checklist before showing anything. Go through it now.

Check How
Valid structure Paste your code into the free validator at validator.w3.org and fix any errors it lists
Headings in order One h1, then h2 sections, no skipped levels
Every image has alt Use View Source and search for <img
Links work Click each one, from each page
Opens on a phone Use Chrome developer tools, device toolbar, or open your page on a real phone
No spelling errors Read it aloud once. Mistakes jump out
Use the browser inspector

Press F12 in Chrome or Edge, then click the arrow icon and point at any element. You can see its HTML and try changes temporarily. It is the single best debugging tool you will use.

Common problems in this project

  • A list that suddenly looks wrong: you probably forgot a closing </li> or </ul>.
  • A broken image: the path or capital letters differ from the real file name.
  • Everything looks bold or huge: an unclosed strong or heading tag is leaking onto what follows.
  • A table that is crooked: a row has too many or too few cells.

Stretch goals

  • Add a figure and caption for a second photo.
  • Add a description list of your favourite tools.
  • Add a fragment-link menu at the top that jumps to each section.
  • Write the page again from scratch tomorrow without looking. It will be faster, and that speed is learning.
Good to know

You have now completed the beginner level. Your page is plain, and that is fine. Everything you added will be styled with CSS later. HTML is the content and structure; once they are right, design is easy.

Check what you learned

Five quick questions. Pick an answer and you will see straight away whether it is right and why.

Why plan a page before writing the code?

  1. It is required by browsers
  2. It prevents confusion and gives the page a clear structure
  3. It makes the page faster
  4. It removes the need for headings

An outline shows what sections you need and in what order.

Which is a good profile page heading structure?

  1. h1 name, then h2 sections
  2. Five h1 headings
  3. Only paragraphs
  4. h4 then h2

One h1 for the main topic, then h2 for each section.

A list looks broken after one item. What is the most likely cause?

  1. The browser is faulty
  2. A missing closing li or ul tag
  3. Too many images
  4. The page has a title

Unclosed tags can swallow what follows. Check each opening tag has its partner.

What does the W3C validator do?

  1. Hosts your site
  2. Checks your HTML for errors
  3. Compresses images
  4. Writes CSS

It reports structure problems such as unclosed tags and invalid nesting.

Which tool lets you inspect any element in the browser?

  1. Notepad
  2. Developer tools opened with F12
  3. The address bar
  4. The bookmarks menu

Developer tools show the HTML and let you test changes temporarily.

Summary

  • Plan first, then write the skeleton, then fill in the content.
  • Test links, images and structure with a checklist.
  • The validator and F12 tools find problems fast.
  • Plain HTML is complete; CSS will make it beautiful.

Next lesson

Intermediate level begins: forms that collect information from visitors.

Questions

Do I need real photos for this project?

No. Use a picture of anything you have permission to use, or a placeholder. The skill is writing the markup correctly.

Can I publish this page?

Yes. Free hosts such as GitHub Pages and Netlify can publish static HTML. We cover publishing later in the course.

What if the validator shows many errors?

Start with the first one. A single missing closing tag can cause a cascade of errors, so fix and re-check one at a time.

How long should this project take?

About 20 minutes of focused work for the first version, and as long as you like for stretch goals.

Progress is saved in this browser.