How to Design a Website in Figma: Step-by-Step Guide for Beginners
Design a small fictional website from a simple brief through layout, reusable UI patterns, prototype links, review notes and a developer-ready handoff.
Introduction to Figma: start with one small website exercise
Figma can be a shared place to plan an interface before it is built. For a first project, keep the scope deliberately small: design a three-page website for a fictional neighbourhood bookshop called Northwind Books. Its visitors should be able to understand the shop, find an upcoming event and send an enquiry.
Write a short brief before you draw anything. This turns a collection of screens into a design decision you can explain.
| Brief item | Decision for this exercise |
|---|---|
| Audience | Readers looking for books and local events. |
| Main action | Open the events page or send an enquiry. |
| Pages | Home, Events and Contact. |
| Content needed | A short introduction, three event cards, address text, opening hours and a contact form outline. |
| Success check | A new visitor can find an event and reach the contact route without guessing. |
Use placeholder copy or content you have permission to use. The point is to practise information order and interface decisions, not to reproduce a real business website.
Setting up your Figma account and workspace
Create or access a Figma account through the sign-in route available to you, then open a new working file. Product labels and account choices can change, so this guide does not depend on a particular screen or plan. Give the file a clear name such as Northwind Books website practice.
Keep the workspace easy to review. Make a place for the brief and notes, a place for reference observations, and a place for the website screens. Name each screen by page and viewport, for example Home — wide and Home — narrow. Clear names matter when another person needs to find the right design later.
This is a compact practice exercise rather than a replacement for a full curriculum. The Figma course outline is a separate route for broader work with interface design, prototypes and handoff.
Creating a new project: map the content first
List the page sections before styling them. For the Home page, use a short purpose statement, a featured event, a three-card event preview and a contact prompt. For Events, make the event list scannable. For Contact, show the essential details and the form fields a visitor would need.
- Sketch the site map: Home, Events and Contact.
- Write the key action for each page: browse events, read one event, or enquire.
- Place the navigation labels in the same order on every page.
- Use rough blocks for headings, copy, cards and actions before adding visual polish.
- Choose a narrow-screen version early, so the design does not depend on one wide layout.
A sitemap and a few low-detail blocks are enough to reveal missing pages and unclear routes. The Web Designing course outline can complement this exercise with HTML, CSS and responsive implementation topics.
Understanding design components: repeat patterns with intent
A component is a reusable interface pattern. For this website, create only three at first: a primary button, a navigation item and an event card. Reuse those patterns rather than redrawing similar controls on every page.
For each component, record the job it performs and the information it needs. An event card might contain an event title, date, short description and a link. A primary button might use a short action label such as “View events.” That small contract helps you keep screens consistent while still leaving room for page-specific content.
- Use one visual treatment for actions that move the visitor toward the main task.
- Keep secondary actions quieter, so every element does not compete for attention.
- Show selected or unavailable states only when they communicate a real condition.
- Rename patterns clearly enough that a reviewer can tell what belongs where.
Starting small is useful. Add a new component only after you see a pattern repeated at least twice or a variation that needs to stay coordinated.
UI design principles for beginners
Good interface design makes the important choice easier to see. Begin with hierarchy: a visitor should first notice the page purpose, then the supporting information, then the action. Use size, weight, spacing and contrast to create that order instead of relying on decoration.
Choose a restrained type and colour system for the practice site. For example, use one type family, a small heading scale, body text with comfortable line spacing, and a limited set of colours with enough contrast to keep text readable. Test the design by reducing the page to a quick glance: can you still identify the page title and the primary action?
Clarity also comes from language. Prefer action labels that name the next step, such as “See all events” or “Send enquiry,” over vague labels such as “Click here.” For broader research, content structure and usability topics, see the UI/UX Design course.
Building your layout with grids and frames
Use a frame to represent each website screen. Start with a wide Home screen, then create a narrow version of the same page. A simple grid gives both screens an alignment system: it helps you line up headings, cards, images and actions instead of positioning every item by eye.
- Place the page content inside consistent side margins.
- Set a maximum width for readable text sections.
- Arrange the three event cards in a row on the wide screen.
- Stack the cards on the narrow screen and keep their order meaningful.
- Check that navigation, headings and buttons still have room to breathe at both sizes.
Use spacing values repeatedly where the relationship is the same. For example, use one gap from a section title to its content and another, larger gap between sections. A layout feels more deliberate when its spacing follows a small system.
Adding interactive elements: prototype one meaningful path
A prototype lets you check the journey before development. Keep the first path short: on the Home screen, select the primary event action; it should lead to the Events screen. From there, select an event card and show a simple event-detail state or an enquiry route. Add the navigation links so the visitor can return to Home or reach Contact.
Do not add movement simply because it is available. Each connection should answer a practical question: where does this action go, what changes after it is selected, and can the visitor recover if they chose the wrong route? Walk through the path yourself, then ask a reviewer to find the next event without telling them where to click.
Collaboration and feedback in Figma
Share the design with a clear review goal. Instead of asking whether someone “likes” the website, ask questions tied to the brief:
- What does the bookshop offer after a quick look at the Home page?
- Where would you go to find the next event?
- Which action would you take if you wanted to ask a question?
- Is any label or section hard to understand on the narrow screen?
Collect observations in a short list, then decide which change addresses each issue. Keep feedback about the stated audience and task. A comment is most useful when it describes what a person expected, saw or could not complete.
Exporting and handoff to developers
A handoff should make implementation decisions visible without requiring the developer to infer the whole design. Prepare a concise package for the Northwind Books exercise:
- The approved wide and narrow page screens, named consistently.
- A list of reusable patterns and their intended states.
- Type, colour and spacing choices used in the design.
- Notes for interactions, including the route from Home to Events and Contact.
- Only the assets that need separate delivery, in an appropriate web format.
- A note identifying unfinished areas or placeholder content.
Choose export formats based on the asset rather than exporting every part of a page as one image. Scalable icons are often supplied as SVG, while photographs or raster artwork should be optimised for their intended use. Confirm the project’s asset, licensing and delivery requirements with the people building the site.
Before handing the work over, compare the three screens with the original brief. The page purpose, event route, contact route, repeated components and narrow-screen layout should all be easy to identify.
Frequently asked questions
Do I need to know how to code before designing the exercise?
No. You can plan the content, hierarchy, screens and prototype route first. Basic HTML and CSS knowledge becomes helpful when you want to understand how the layout may be implemented.
How many screens should a first website exercise include?
Three pages with a wide and narrow version are enough to practise structure, repeated patterns and responsive decisions. Finish that scope before adding more pages.
When should I create a component?
Create one when an interface pattern repeats or needs coordinated variations. In this exercise, the button, navigation item and event card are useful first candidates.
What should a developer receive at handoff?
Provide named screens, reusable pattern notes, visual choices, interaction notes and the assets that require separate delivery. Clearly mark anything that is still a placeholder or needs a product decision.
Take the exercise further
Use this one-site practice brief to build a repeatable workflow, then review the Figma course outline for broader tool and project topics.
View Figma Course