AdvancedLesson 30 of 307 min read

Advanced capstone: build and publish a professional portfolio

Combine everything from the course to build, audit and publish a complete portfolio website with SEO, accessibility and performance.

In this lesson you will

  • Plan and build a four-page portfolio
  • Reuse a professional page template
  • Audit with the validator and Lighthouse
  • Publish your site for free

About 25 minutes

The capstone: a portfolio you can show the world

You started this course not knowing what a tag is. Now you know forms, semantic structure, media, accessibility, SEO, performance and security. The last lesson pulls it all together into one finished product that carries your name: a portfolio website. Employers, clients and friends can open it with one link, and it proves what you can do far better than a sentence on a CV.

What you will build

  • A homepage with a hero section, a short bio and highlights of your best work.
  • A projects page where each project is an article with an image, description and link.
  • An about page with your story, skills and a downloadable CV.
  • A contact page with an accessible, validated form.
  • Excellent head tags, social cards, structured data, responsive images and secure links on every page.

If you do not yet have projects of your own, use the ones from this course: the profile page from lesson 10 and the bakery site from lesson 20 are perfectly good first entries.

Step 1: Plan the site

  1. Write who the site is for. A hiring manager? Clients? Choose one primary visitor.
  2. List the three things they should learn in the first ten seconds.
  3. Sketch each page as a list of regions: header, main sections, footer.
  4. Pick a simple structure of four pages and a consistent navigation.
  5. Decide on the file and folder names now. Lower case and hyphens only.
portfolio/
  index.html
  projects.html
  about.html
  contact.html
  css/style.css
  js/main.js
  images/
  files/cv.pdf
  favicon.svg

Step 2: Build a reusable page template

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Priya Sharma | Web Developer in Lahore</title>
  <meta name="description" content="Portfolio of Priya Sharma: websites, forms and accessible web pages.">
  <link rel="canonical" href="https://priya.example.com/">
  <link rel="icon" href="favicon.svg" type="image/svg+xml">
  <meta property="og:title" content="Priya Sharma | Web Developer">
  <meta property="og:description" content="Websites that are fast, accessible and easy to use.">
  <meta property="og:image" content="https://priya.example.com/images/share.jpg">
  <meta name="twitter:card" content="summary_large_image">
  <link rel="stylesheet" href="css/style.css">
  <script src="js/main.js" defer></script>
</head>
<body>
  <a class="skip" href="#content">Skip to main content</a>
  <header>
    <a href="index.html">Priya Sharma</a>
    <nav aria-label="Main">
      <a href="index.html" aria-current="page">Home</a>
      <a href="projects.html">Projects</a>
      <a href="about.html">About</a>
      <a href="contact.html">Contact</a>
    </nav>
  </header>
  <main id="content">
    ...
  </main>
  <footer>
    <p>&copy; 2026 Priya Sharma</p>
  </footer>
</body>
</html>

Look at what is in there: UTF-8, viewport, a unique title and description, canonical, icon, Open Graph and Twitter tags, a deferred script, a skip link, semantic landmarks, a labelled navigation, and the current page marked with aria-current. That is a professional head in thirty lines, and you now understand every one of them.

Step 3: The projects page

<h1>Selected projects</h1>

<article>
  <h2>Bakery website</h2>
  <picture>
    <source type="image/webp" srcset="images/bakery-800.webp 800w, images/bakery-400.webp 400w" sizes="(max-width: 600px) 100vw, 600px">
    <img src="images/bakery-800.jpg" alt="Screenshot of the Priya's Bakery homepage" width="800" height="500" loading="lazy">
  </picture>
  <p>A three-page business site with a validated order form and a menu table.</p>
  <ul>
    <li>HTML5, accessible forms and semantic layout</li>
    <li>Built in two days</li>
  </ul>
  <a href="https://example.com/bakery" target="_blank" rel="noopener noreferrer">View the live site</a>
</article>

Build one project card of your own: an article with an h2, an image with proper alt, width and height, a one-sentence description and a safe external link.

<!-- your project article here -->

Follow the card above: article, h2, img, p, then the link with rel=”noopener noreferrer”.

<article>
  <h2>My first website</h2>
  <img src="https://picsum.photos/400/250" alt="Preview of my first website" width="400" height="250" loading="lazy">
  <p>A personal profile page built with HTML.</p>
  <a href="https://example.com" target="_blank" rel="noopener noreferrer">View the project</a>
</article>

Step 4: Add structured data

On the homepage add a Person block, so search engines know who you are, where to find your profiles and what you do.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Priya Sharma",
  "jobTitle": "Web developer",
  "url": "https://priya.example.com/",
  "sameAs": ["https://www.linkedin.com/in/example"]
}
</script>

Step 5: Audit like a professional

  1. Validate every page with the W3C validator.
  2. Run Lighthouse and aim for green scores in Performance, Accessibility, Best Practices and SEO.
  3. Test with the keyboard only, then with a screen reader for a few minutes.
  4. Check the page at 360 pixels wide on your phone.
  5. Share a link in a chat and see how the card looks, then fix the image or text.
  6. Click every link, including the ones in the footer, and submit the form with bad data on purpose.

Step 6: Publish for free

  • GitHub Pages: create a repository, upload the folder and turn on Pages in settings.
  • Netlify or Cloudflare Pages: drag the folder into the dashboard and get a live address in a minute.
  • Your own domain: buy one for a small yearly fee and point it at the host. A name like priyasharma.com is far more memorable than a free subdomain.

After publishing, add the address to your CV, your LinkedIn profile and your messaging apps. Then visit the live site on your phone with the Wi-Fi turned off, just to see it as a visitor on a bad connection would.

What comes next

You have finished the HTML course. HTML is the skeleton, and the natural next step is dressing it. The CSS course will teach you colours, fonts, layouts with flexbox and grid, and responsive design. After that, JavaScript will make your pages come alive. Your portfolio will grow with you: each new skill becomes a new project to show.

Keep shipping small

A finished small site beats a perfect site that never launches. Publish this week, then improve a little every week.

Writing the case study that sells you

A grid of screenshots proves you made something. A short explanation proves you can think. For each of your best two or three projects, add three small paragraphs: the problem you were asked to solve, what you did and which choices you made, and the result. If you do not have numbers, use plain facts such as “loads in under two seconds on a phone” or “passed accessibility checks with no errors”.

<article>
  <h2>Bakery website</h2>
  <h3>The problem</h3>
  <p>Customers phoned all day to order cakes and the owner lost track of requests.</p>
  <h3>What I did</h3>
  <p>Built a three-page site with a validated order form, accessible labels and a mobile-first layout.</p>
  <h3>The result</h3>
  <p>Orders arrive by email with every detail filled in, and the page scores 100 for accessibility in Lighthouse.</p>
</article>

Hiring managers and clients skim. This structure lets them find what they care about in seconds, and it shows the habits of a professional: understanding the need, making decisions and checking the outcome.

Common portfolio mistakes

  • Showing every tiny exercise. Choose your best three to six pieces.
  • Broken links and missing images. Test everything on the live site.
  • No way to contact you. Put your email or form on every page footer.
  • Hiding the work behind a long intro. Show a project within the first screen.
  • Never updating it. Add one new item every few months and note the date.

Check what you learned

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

What is the best first step for a portfolio?

  1. Choose colours
  2. Decide who the site is for and what they should learn
  3. Buy ads
  4. Write JavaScript

Knowing the visitor shapes every choice.

Which tag should every page head include for phones?

  1. The viewport meta tag
  2. A script tag
  3. A table tag
  4. A form tag

Without viewport, phones show a shrunken desktop layout.

How should external project links be written?

  1. With target=_blank only
  2. With rel=”noopener noreferrer” when opening a new tab
  3. Without href
  4. As images only

It is a safe, standard habit.

Which tool gives a combined score for performance, accessibility and SEO?

  1. Lighthouse
  2. Notepad
  3. A spell checker
  4. A zip tool

Lighthouse audits all four areas.

Where can you host a portfolio for free?

  1. GitHub Pages or Netlify
  2. Only a paid server
  3. Only your own computer
  4. Nowhere

Static hosts are free for small sites.

Summary

  • Plan the visitor first, then the pages.
  • A good template carries SEO, accessibility and security from the start.
  • Audit with validators, Lighthouse and real testing.
  • Publish early and keep improving.

Next lesson

Congratulations, you have completed the HTML course. Continue with the CSS course to style your pages.

Questions

I have no projects yet. What do I show?

Use the profile page and the bakery site from this course, then add new projects as you learn.

Do I need to know CSS to publish?

Not to publish, but a little styling makes the site far more attractive. The CSS course is the natural next step.

Can I keep the site updated easily?

Yes. Edit the files and upload them again, or connect the repository to your host for automatic updates.

Progress is saved in this browser.