Skip to content
Tutorials Center
My learning

Topics

Lesson 35 of 37 ยท Projects and Practice

Project: A Portfolio Site

Plan and build a professional portfolio in Wix or Webflow: goals, sitemap, wireframes, case studies, CMS projects, contact form, SEO, launch. Includes planning and checking stand-ins.

A portfolio is the classic first project: small enough to finish, real enough to show to employers or clients. In this project you plan and build a portfolio of 5 to 7 pages on either platform, using skills from the whole course: layout, CMS, interactions, forms, SEO, performance and launch. The steps are described precisely, but because Wix and Webflow cannot run on this site, you will do the building in your own account, and the stand-ins here help with planning and checking.

Use a free plan or trial to build, and publish on the platform's free address. Features such as custom domains, code embeds and form limits can require paid plans; check the current plan table before you promise anything to a client.

Step 1: Define the goal and audience

Write three sentences: Who will visit (a hiring manager, a small-business client)? What do you want them to do (email you, book a call, download a CV)? Why should they pick you (your specialty, results, style)? One primary action decides the design: every page leads toward it.

Step 2: Plan the sitemap and content

A good portfolio has:

  • Home: headline stating what you do and for whom, 3 selected projects, social proof (a testimonial), a clear contact button.
  • Work (index): all projects in a grid with filters if you have many.
  • Project (case study template): one page design used for every project.
  • About: short story, photo, skills, how you work.
  • Contact: a form and direct email.
  • Optional: blog or notes, services/pricing, CV page.

Gather the content before designing: project images (resized), short descriptions, results, quotes, a headshot, bio and contact details. Designing with real content avoids surprises.

Step 3: Wireframe and style

Sketch each page on paper, then choose a design system: two fonts (one for headings, one for body), a color palette (a dark text color, a light background, one accent; check contrast, see Accessibility and Launch Checklist), a spacing scale (for example 8, 16, 24, 48, 96 px) and consistent button styles.

In Webflow, define these as classes and variables (global swatches and a style guide page); in Wix Studio, use site-wide design settings (colors and text themes). Consistency beats cleverness.

Step 4: Build the layout

Start with the structure, not the decoration:

  1. Create the navigation bar and footer once and reuse them (Webflow symbols/components; Wix header and footer, or master components).
  2. Build the Home page sections from top to bottom: hero, selected work, about snippet, testimonial, call to action.
  3. Make it responsive at each breakpoint: desktop, tablet, mobile landscape and mobile portrait in Webflow; the breakpoints available in Wix Studio or the Editor's mobile view in the classic editor. Check long headlines, image crops and menus on small screens.

Step 5: Add the project CMS

Create a Projects collection (Webflow CMS Collection; Wix Content Manager collection) with fields:

Field Type
Title Text
Slug Text (URL part)
Cover image Image
Summary Plain text (max ~160 chars)
Client Text
Year Number
Role Text
Gallery Multi-image
Body Rich text
Featured Switch

Design the Project template once and bind fields to elements. Show a Featured list on Home, and the full list on Work. This is the same pattern that powers blogs and stores.

Before building, model the data and check it. The stand-in below validates a project list against the fields you plan.

JS Stand-in: validate project entries

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Step 6: Write case studies that sell

For each project, use this structure: Challenge (the problem), Approach (what you did and why), Result (numbers or outcomes), and a visual story (3 to 5 strong images with captions). Clients buy outcomes. Use concrete numbers, such as "Checkout completion up from 41% to 55%", only when they are real.

Step 7: Add polish with restraint

Step 8: SEO and speed

Give each page a unique title and description, add alt text, choose clean slugs, set one H1 per page and publish a sitemap (SEO Fundamentals, Performance and Core Web Vitals). Resize images to the displayed size, keep the hero eager, and test on mobile.

Step 9: Launch

Connect your domain if you have one (Domains, DNS and SSL), enable indexing, submit the sitemap to Search Console, run the launch checklist and ask two friends to try the site on their own devices.

A quick project scorer

Use this stand-in to rate your own build against the project rubric.

JS Stand-in: self-assessment

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Stretch goals

Add a blog, a dark-mode palette, a filterable project grid, a downloadable CV, or a case study with an interactive before/after slider.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What should decide the design of a portfolio's pages?

    One primary action (for example contact) shapes layout, content and calls to action.
  2. 2. Why use a CMS collection for projects?

    A template plus structured fields keeps all case studies consistent and easy to add.
  3. 3. A strong case study includes

    That structure shows the problem, your thinking and the outcome.
  4. 4. Before launch you should

    A launch checklist catches broken forms, links and mobile issues.

Summary

  • Start with a goal, a sitemap and real content, then design a small system of fonts, colors and spacing.
  • Build navigation and footer once, then pages, then a Projects CMS with a template.
  • Write case studies around challenge, approach and result.
  • Add forms, restrained motion, SEO and performance work, then launch with a checklist.

Next: Project: An Online Store Launch