Skip to main content

Frontend development · Intermediate · 22 min

Build a responsive page from a Figma frame

By Padding · Updated 18 Nov 2026
Modern browsers · CSS Media Queries Level 4 and Flexible Box Layout · checked in Chromium 159 · Node.js 26

You will build the Larkfield Clinic Pick a time screen as one responsive page from its phone, tablet and desktop frames, with values mapped to tokens, breakpoints taken from the design note, and a script that screenshots and measures the page at each width.

On this page

A designer hands you three frames of the same screen: a phone at 360 pixels wide, a tablet at 768 and a desktop at 1280. The tempting build is three layouts, one per frame, with every number copied from the inspect panel. That page looks right at exactly three widths and wrong at the thousands of widths in between, and the first time the designer changes a spacing value you have to find it in three places.

This tutorial builds one page instead. You read the frames as a set of rules, put the shared values into tokens, write the phone layout as the default, and add only what changes at each breakpoint. Then you write a short Playwright script that screenshots the page at the three frame widths and prints the measurements that matter, so you can compare it with the design and run it again after every change.

The screen is Pick a time from the Larkfield Clinic booking app, a fictional community clinic used across these tutorials. A patient has chosen a Nurse appointment (15 minutes) and now sees a week strip with Tuesday 9 December selected, Morning and Afternoon time slots with 10:30 chosen, a phone number for people who cannot find a time, and a Continue button. The design note from Design one layout for phone, tablet and desktop sets two breakpoints, at 600 and 960 pixels. If you do not have the Figma file, every value you need is in the first step.

Step 1 · Turn the frames into a build sheet

Open the Larkfield file in Dev Mode and select each block on the three Pick a time frames in turn. Inspect a Figma design as a developer covers the inspect panel in detail; here the job is to sort what you read. Every number in a frame is one of three kinds:

  • Token. A value with a name in the design, such as a colour variable (colour/accent), a text style (Heading/M) or a step on the spacing scale (8, 16, 24, 32). Dev Mode shows the variable name next to the value. You write the name, never the raw value.
  • Rule. A constraint from the auto layout settings or the breakpoint note: a slot is at least 72 and at most 120 wide, the panel is fixed at 320, the content stops growing at 720. These become layout tokens or CSS properties.
  • Result. A number the layout produced at one particular width. At 360, each time slot measures 76 wide, because four slots of at least 72 plus three gaps of 8 fill 328 pixels of content. Type 76 into CSS and the slots stop wrapping correctly at every other width. Results are what you check against later, never what you build from.

Open a text file next to your code and write the build sheet. This is the one for Pick a time:

Text
Pick a time: build sheet
Read in Dev Mode                      Kind     Write in code
Fills: text, text-muted, surface,     token    --colour-text, --colour-text-muted, ...
  canvas, line, border, accent, ...
Heading/M, Body, Body/Small, Label    token    --text-heading-m, --text-body, ...
Margins 16, 24, 32                    token    --space-16, --space-24, --space-32
Gap between groups 24, slots 8        token    --space-24, --space-8
Corner radius 8                       token    --radius-control
Slot fill, min 72, max 120            rule     --slot-min, --slot-max
Week strip: 7 equal cells             rule     grid, repeat(7, minmax(0, 1fr))
Continue 48 tall; 200 wide (medium)   rule     --control-height, --continue-width
Back control 44 x 44                  rule     --tap-min
Panel 320 (wide)                      rule     --panel-width
Content max 720 (medium), 1216 (wide) rule     --content-max-medium, --content-max-wide
Breakpoints 600, 960                  rule     37.5rem, 60rem in media queries
Slot 76 at 360, main column 864       result   nothing: check these in the browser

Dev Mode can show CSS in rem instead of px (a setting in the Code section, with a 16 pixel root by default). Either way, divide by 16 when you convert: 600 pixels is 37.5rem and 960 is 60rem. Writing sizes in rem means the layout responds when someone raises their browser's default text size.

Check it worked

Every number in your build sheet has a kind. No result, such as 76 or 864, appears in the "Write in code" column. If you find a value that is neither on the spacing scale nor in the note, such as a 15 pixel gap next to a 16 pixel one, add it to a list of questions for the designer instead of copying it.

Step 2 · Put the tokens in one file

Create a folder for the page and write the tokens. The colour and type values are the Larkfield variables and text styles. The names match Turn design tokens into CSS custom properties, so if you already have a tokens.css from that tutorial, copy it in and add only the layout section.

Bash
mkdir -p ~/larkfield-responsive-demo
cd ~/larkfield-responsive-demo
cat > tokens.css <<'CSS'
/* Larkfield tokens used by Pick a time. */
:root {
  --colour-text: #1b1f24;
  --colour-text-muted: #5a6270;
  --colour-surface: #ffffff;
  --colour-canvas: #f6f7f8;
  --colour-line: #d5d9df;
  --colour-border: #7d8592;
  --colour-accent: #0f5e5a;
  --colour-on-accent: #ffffff;

  --font-family: Inter, system-ui, sans-serif;
  --text-heading-m: 600 1.25rem/1.625rem var(--font-family);
  --text-body: 400 1rem/1.5rem var(--font-family);
  --text-body-small: 400 0.875rem/1.25rem var(--font-family);
  --text-label: 600 0.875rem/1.25rem var(--font-family);

  --space-8: 0.5rem;
  --space-16: 1rem;
  --space-24: 1.5rem;
  --space-32: 2rem;
  --radius-control: 0.5rem;

  /* Layout rules from the breakpoint note */
  --slot-min: 4.5rem;             /* 72 */
  --slot-max: 7.5rem;             /* 120 */
  --control-height: 3rem;         /* 48 */
  --tap-min: 2.75rem;             /* 44 */
  --continue-width: 12.5rem;      /* 200 */
  --panel-width: 20rem;           /* 320 */
  --content-max-medium: 45rem;    /* 720 */
  --content-max-wide: 76rem;      /* 1216 */
}
CSS
grep -c -- '^  --' tokens.css

Each text style is one font shorthand: weight, size, line height and family. Heading/M at 20 on 26 becomes 600 1.25rem/1.625rem. The family names Inter first and falls back to the system font. This page does not download Inter, so on a phone without it the system font is used. That keeps the page to two small CSS files and no font download, which matters for patients on prepaid data, and you will see the difference in letter widths when you compare screenshots later.

Check it worked

The grep command prints 26: eight colours, five type tokens, five spacing and radius tokens, and eight layout rules. No value in the file is a result from the build sheet.

Step 3 · Mark up the screen in reading order

Write the HTML once, for every width. The order of elements in the source is the order a keyboard or screen reader user meets them, so it follows the design note: header, service, week strip, slots, then the booking summary and Continue, then the phone fallback. On the phone the summary will be a bar at the bottom of the screen and on the desktop a side panel, but in the source it is always after the slots.

Bash
cd ~/larkfield-responsive-demo
cat > index.html <<'HTML'
<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Pick a time · Larkfield Clinic</title>
  <link rel="stylesheet" href="tokens.css">
  <link rel="stylesheet" href="page.css">
</head>
<body>
  <div class="page">
    <header class="app-header">
      <a class="back" href="#" aria-label="Back to Choose a service">&larr;</a>
      <h1>Pick a time</h1>
    </header>
    <div class="layout">
      <main class="picker">
        <p class="service">Nurse appointment · 15 min</p>
        <div class="week" role="group" aria-label="Day">
          <button type="button" aria-pressed="false">Mon <b>8</b></button>
          <button type="button" aria-pressed="true">Tue <b>9</b></button>
          <button type="button" aria-pressed="false">Wed <b>10</b></button>
          <button type="button" aria-pressed="false">Thu <b>11</b></button>
          <button type="button" aria-pressed="false">Fri <b>12</b></button>
          <button type="button" aria-pressed="false">Sat <b>13</b></button>
          <button type="button" aria-pressed="false">Sun <b>14</b></button>
        </div>
        <h2>Tue 9 Dec</h2>
        <fieldset class="slot-group">
          <legend>Morning</legend>
          <div class="slots">
            <label><input type="radio" name="time" value="09:00">09:00</label>
            <label><input type="radio" name="time" value="09:20">09:20</label>
            <label><input type="radio" name="time" value="09:40">09:40</label>
            <label><input type="radio" name="time" value="10:30" checked>10:30</label>
            <label><input type="radio" name="time" value="11:00">11:00</label>
          </div>
        </fieldset>
        <fieldset class="slot-group">
          <legend>Afternoon</legend>
          <div class="slots">
            <label><input type="radio" name="time" value="14:00">14:00</label>
            <label><input type="radio" name="time" value="14:40">14:40</label>
            <label><input type="radio" name="time" value="15:20">15:20</label>
            <label><input type="radio" name="time" value="16:00">16:00</label>
          </div>
        </fieldset>
      </main>
      <aside class="panel" aria-label="Your booking">
        <div class="booking">
          <p class="summary"><span class="summary-service">Nurse appointment<span class="sep"> · </span></span><span class="summary-time">Tue 9 Dec, 10:30</span></p>
          <button class="continue" type="button">Continue</button>
        </div>
        <p class="fallback">Can't see a time that works? Call <a href="tel:01234567890">01234 567 890</a></p>
      </aside>
    </div>
  </div>
</body>
</html>
HTML
touch page.css

Two choices here make the CSS simpler later. The booking summary and the phone fallback share one <aside>, because on the desktop they sit together in the panel; on smaller screens CSS lifts the summary out into the bottom bar and the fallback stays under the slots. And the summary is two spans, so the wide layout can show the service small and the time large without a second copy of the text. The time slots are native radio buttons; Build a time slot picker with radio buttons explains that pattern in full, including taken slots.

Check it worked

Open index.html in your browser (open index.html on macOS, xdg-open index.html on Linux, or drag the file into a window). With an empty page.css, everything is stacked in browser default styles: the header, the service line, seven day buttons, the Tue 9 Dec heading, two groups of radio buttons with 10:30 selected, the summary line, Continue and the phone line, in that order.

Step 4 · Build the compact layout as the default

Write the phone layout with no media query at all. Everything below 600 pixels uses it, and the wider ranges only add changes on top. Three custom properties hold the values that change between ranges: the side margin, the maximum content width and the space reserved for the bottom bar.

Bash
cd ~/larkfield-responsive-demo
cat > page.css <<'CSS'
*, *::before, *::after { box-sizing: border-box; }

/* Values that change per range. Compact is the default. */
:root {
  --margin: var(--space-16);
  --content-max: 100%;
  --bar-space: 9rem;     /* tallest bar: 16 + 48 (two-line summary) + 8 + 48 + 16 + 1 = 137, plus room */
}

html { scroll-padding-bottom: var(--bar-space); }
body {
  margin: 0;
  background: var(--colour-canvas);
  color: var(--colour-text);
  font: var(--text-body);
}
.page {
  width: min(100% - 2 * var(--margin), var(--content-max));
  margin-inline: auto;
  padding-bottom: var(--bar-space);
}

/* Header */
.app-header { display: flex; align-items: center; gap: var(--space-8); padding-block: var(--space-8); }
.app-header h1 { margin: 0; font: var(--text-heading-m); }
.back {
  display: grid; place-items: center;
  min-width: var(--tap-min); min-height: var(--tap-min);
  color: var(--colour-accent); font-size: 1.5rem; text-decoration: none;
}

/* Main column */
.picker { display: flex; flex-direction: column; gap: var(--space-24); }
.picker > * { margin: 0; }
.service { font: var(--text-body-small); color: var(--colour-text-muted); }
.picker h2 { font: var(--text-heading-m); }

.week { display: grid; grid-template-columns: repeat(7, minmax(0, 1fr)); gap: var(--space-8); }
.week button {
  min-height: var(--tap-min); padding: var(--space-8) 0;
  border: 1px solid var(--colour-border); border-radius: var(--radius-control);
  background: var(--colour-surface); color: var(--colour-text); font: var(--text-body-small);
}
.week b { display: block; font: var(--text-label); }
.week [aria-pressed="true"] { background: var(--colour-accent); border-color: var(--colour-accent); color: var(--colour-on-accent); }

.slot-group { margin: 0; padding: 0; border: 0; min-width: 0; }
.slot-group legend { padding: 0; margin-bottom: var(--space-8); font: var(--text-label); }
.slots { display: flex; flex-wrap: wrap; gap: var(--space-8); }
.slots label {
  position: relative;
  flex: 1 1 var(--slot-min);
  max-width: var(--slot-max);
  min-height: var(--control-height);
  display: flex; align-items: center; justify-content: center;
  border: 1px solid var(--colour-border); border-radius: var(--radius-control);
  background: var(--colour-surface); font: var(--text-label);
}
.slots input { position: absolute; inset: 0; margin: 0; opacity: 0; cursor: pointer; }
.slots label:has(:checked) { background: var(--colour-accent); border-color: var(--colour-accent); color: var(--colour-on-accent); }
.slots label:has(:checked)::before { content: "\2713\00a0" / ""; }
.slots label:has(:focus-visible) { outline: 3px solid var(--colour-accent); outline-offset: 2px; }

/* Booking bar: fixed to the bottom on compact and medium */
.booking {
  position: fixed; inset-inline: 0; bottom: 0;
  display: flex; flex-direction: column; gap: var(--space-8);
  padding-block: var(--space-16);
  padding-inline: max(var(--margin), (100% - var(--content-max)) / 2);
  background: var(--colour-surface);
  border-top: 1px solid var(--colour-line);
}
.summary { margin: 0; }
.continue {
  min-height: var(--control-height);
  border: 0; border-radius: var(--radius-control);
  background: var(--colour-accent); color: var(--colour-on-accent); font: var(--text-label);
}
.fallback { margin: var(--space-24) 0 0; font: var(--text-body-small); color: var(--colour-text-muted); }
.fallback a { color: var(--colour-accent); white-space: nowrap; }
CSS

This is where the build sheet pays off. Each Figma setting becomes one CSS property:

  • Slots that fill, with a min and max, and wrap. flex: 1 1 var(--slot-min) lets each slot start at 72 and grow, max-width stops it at 120, and flex-wrap: wrap moves slots to a new row when the next one would be narrower than 72. The 76 you measured in Figma is what the browser works out at 360. You never wrote it.
  • Seven equal day cells. repeat(7, minmax(0, 1fr)) keeps seven columns at every width. The minmax(0, …) lets a cell shrink below its content's natural width at 320 instead of pushing the strip wider than the screen.
  • Content width and margins. .page is the screen width minus two margins, but never more than --content-max. On compact that maximum is the full width, so only the margin matters.
  • The bar. position: fixed keeps the summary and Continue at the bottom of the screen while the slots scroll. Because the bar sits on top of the page, .page gets padding at the bottom so the last slot and the phone line can scroll clear of it, and scroll-padding-bottom gives the browser the same space to keep in view when it scrolls to a focused slot. Without it, a keyboard user who arrows through the slots to 16:00 on a short screen can find the focused slot under the bar. --bar-space has to cover the tallest bar the summary can produce, not the one in the frame: at 320 the summary Nurse appointment · Tue 9 Dec, 10:30 is about as wide as the 288 pixel content column, so it wraps onto a second line in any font a little wider than Inter, and a translated summary wraps sooner, so the 9rem allows for two lines. If your longest summary needs three, raise it. The bar's side padding uses max() so its contents line up with the page at every width; the next step shows why.

Check it worked

Reload the page and switch your browser to its responsive or device mode (F12, then the device toolbar icon in Chrome or Edge, or Responsive Design Mode in Firefox and Safari). Set the width to 360. The Morning group shows four slots on the first row and 11:00 alone on the second, the selected 10:30 slot is teal with a tick, and the summary and a full-width Continue sit in a white bar at the bottom. Scroll down: the phone line comes out from under the bar. Now try 320. Morning wraps to three and two, and nothing scrolls sideways.

Step 5 · Add the medium range at 600 pixels

Add a media query for the first breakpoint. It changes only what the design note says changes at 600: wider margins, content capped at 720, and a booking bar that fits on one row.

Bash
cd ~/larkfield-responsive-demo
cat >> page.css <<'CSS'

/* Medium: 600 and up (37.5rem). Summary and Continue fit on one row from 554. */
@media (min-width: 37.5rem) {
  :root {
    --margin: var(--space-24);
    --content-max: var(--content-max-medium);
    --bar-space: 5.5rem; /* 16 + 48 + 16, plus room */
  }
  .booking { flex-direction: row; align-items: center; gap: var(--space-16); }
  .summary { flex: 1; }
  .continue { flex: 0 0 var(--continue-width); }
}
CSS

The breakpoint is written as a number, not var(--…), because custom properties do not work inside a media query condition. Write the pixel value from the note in a comment beside it, so the reason travels with the number. Using rem here also has an effect on accessibility: rem in a media query is based on the browser's default text size, so a patient who sets their default to 20 pixels gets the medium layout from 750 pixels instead of 600, which is when the larger text actually fits on one row.

Look at what you did not change. The slots, the week strip and the header have no new rules, because they were already built from rules rather than sizes. At 768 the slots grow to their 120 maximum and both groups fit on one row by themselves. The bar's padding, max(var(--margin), (100% - var(--content-max)) / 2), now does its job: the bar's white background still spans the full screen, but its contents start and end where the 720 pixel content column does.

Check it worked

Set the device mode width to 768. The bar is one row, with the summary on the left and a 200 pixel Continue on the right, lined up with the edges of the slots above it. Each slot is 120 wide and each group is on one row. Drag the width down to 600: still one row. At 599 the bar stacks again. Then try 959: the content stays 720 wide, centred, with the extra space in the margins.

Step 6 · Add the wide range with a side panel at 960 pixels

The second breakpoint is the one layout change that moves things. The booking summary leaves the bottom bar and joins the phone fallback in a side panel that stays in view while the slots scroll.

Bash
cd ~/larkfield-responsive-demo
cat >> page.css <<'CSS'

/* Wide: 960 and up (60rem). A 320 panel fits beside a 496 main column from 912. */
@media (min-width: 60rem) {
  :root {
    --margin: var(--space-32);
    --content-max: var(--content-max-wide);
    --bar-space: var(--space-32);
  }
  .layout {
    display: grid;
    grid-template-columns: minmax(0, 1fr) var(--panel-width);
    gap: var(--space-32);
    align-items: start;
  }
  .panel {
    position: sticky; top: var(--space-32);
    padding: var(--space-24);
    background: var(--colour-surface);
    border: 1px solid var(--colour-line);
    border-radius: var(--radius-control);
  }
  .booking {
    position: static;
    flex-direction: column; align-items: stretch;
    padding: 0; border: 0; background: none;
  }
  .summary, .continue { flex: none; }
  .summary-service { display: block; font: var(--text-body-small); color: var(--colour-text-muted); }
  .summary-time { display: block; font: var(--text-heading-m); }
  .sep { display: none; }
}
CSS

The .layout grid puts the main column and the <aside> side by side. The main column takes the remaining space, and minmax(0, 1fr) again stops long content from forcing it wider. The panel is position: sticky, so it scrolls with the page until it reaches 32 pixels from the top and then stays there. Inside it, the booking block goes back to normal flow (position: static), its row layout from the medium range is turned back into a column, and the summary splits into a small service line and a large time. The flex: none matters: in a column, a flex-basis of 200 would set Continue's height, not its width.

With the page capped at 1216 and a 320 panel plus a 32 gap, the main column is 864 wide at 1280, the same as the Figma frame. You did not write 864 anywhere.

Check it worked

Set the width to 1280. The header runs across the top, the slots fill the left column on one row per group, and a white panel on the right holds Nurse appointment in small grey text, Tue 9 Dec, 10:30 in large text, a full-width Continue and the phone line. There is no bar at the bottom. At 960 the main column is 544 wide and all seven day labels are readable. At 1440 the content stops at 1216 and sits in the centre with 112 pixels of margin on each side.

Step 7 · Write a screenshot script for the three widths

Checking widths by hand in device mode is slow and easy to skip. A short script with Playwright, which drives a real Chromium from Node.js, does it in a few seconds. Install it in the project folder, pinned to an exact version so the results do not shift under you:

Bash
cd ~/larkfield-responsive-demo
npm init -y > /dev/null
npm install --save-dev playwright@1.65.1
npx playwright install chromium

On Linux, if Chromium will not start because of missing libraries, run sudo npx playwright install-deps chromium once.

The script opens the page at the size of each Figma frame, saves a screenshot of what the screen shows, and prints the range the browser applied with the widths you care about. Extra widths can be passed on the command line, which you use in the next step.

Bash
cd ~/larkfield-responsive-demo
cat > shots.mjs <<'JS'
import { chromium } from 'playwright';
import { mkdir } from 'node:fs/promises';
import { resolve } from 'node:path';
import { pathToFileURL } from 'node:url';

const url = pathToFileURL(resolve('index.html')).href;
// The three Figma frames, plus any widths given on the command line.
const sizes = [[360, 640], [768, 1024], [1280, 800],
  ...process.argv.slice(2).map((w) => [Number(w), 800])];

await mkdir('shots', { recursive: true });
const browser = await chromium.launch();
for (const [width, height] of sizes) {
  const page = await browser.newPage({ viewport: { width, height } });
  await page.goto(url);
  await page.screenshot({ path: `shots/pick-a-time-${width}.png` });
  const m = await page.evaluate(() => {
    const w = (sel) => Math.round(document.querySelector(sel).getBoundingClientRect().width);
    const range = matchMedia('(min-width: 60rem)').matches ? 'wide'
      : matchMedia('(min-width: 37.5rem)').matches ? 'medium' : 'compact';
    const sideways = document.documentElement.scrollWidth > document.documentElement.clientWidth;
    return { range, main: w('.picker'), slot: w('.slots label'), cont: w('.continue'), sideways };
  });
  console.log(`${width}px ${m.range}: main ${m.main}, slot ${m.slot}, Continue ${m.cont}, sideways scroll ${m.sideways ? 'YES' : 'no'}`);
  await page.close();
}
await browser.close();
JS
node shots.mjs
ls shots

The screenshot is the viewport, not the full page, because the Figma frames are screen-sized too: 360 by 640 shows what a patient sees before scrolling, with the bar at the bottom.

Check it worked

The script prints three lines like these, and ls lists three PNG files:

Text
360px compact: main 328, slot 76, Continue 328, sideways scroll no
768px medium: main 720, slot 120, Continue 200, sideways scroll no
1280px wide: main 864, slot 120, Continue 270, sideways scroll no

Each number is a result from your build sheet, and it came out of the rules. Open shots/pick-a-time-360.png: four slots on the first Morning row and the booking bar at the bottom edge.

Step 8 · Compare with the Figma frames at every edge

Export the three Pick a time frames from Figma as PNG at 1x, so one image pixel is one CSS pixel, and save them next to the screenshots as figma-360.png, figma-768.png and figma-1280.png. Open each pair side by side at the same zoom. Look for differences in structure, not in pixels:

  • Must match: the order of blocks, the number of slots per row, the bar or panel and its contents, the column widths the script printed, and the gaps between groups.
  • May differ: letter shapes and text widths if the page fell back from Inter to a system font, anti-aliasing, and a pixel of line height. If a difference comes from the font, it is not a layout bug.

When something does not match, go back to the build sheet before you touch the CSS. Usually the frame and the note disagree, or a value in the frame is a result someone typed as a rule. Add it to your questions for the designer.

Then check the widths no frame shows. Breakpoints fail at their edges, so pass the widths either side of each one to the script:

Bash
cd ~/larkfield-responsive-demo
node shots.mjs 320 599 600 959 960 1440

Finally, try zoom and long text in your own browser. Open the page at full width on a laptop and zoom to 200 percent: a 1280 window becomes 640 CSS pixels and shows the medium layout; at 400 percent it shows compact. Then edit the summary in index.html to the longest text you might ship, such as the French Rendez-vous infirmier · mar. 9 déc., 10:30: the service text (Rendez-vous infirmier) replaces Nurse appointment inside .summary-service, leave the .sep span as it is, and the date and time (mar. 9 déc., 10:30) go in .summary-time. Pasting the whole string into one span breaks the wide panel's two-line split. Try a long service name in Yoruba or Kiswahili if the clinic adds them, and run the script again at 320 and 600. At 320, scroll to the bottom and check the phone line still clears the taller bar. Changing the language or text direction (Arabic, for example) is a bigger job than one test, but the summary wrapping onto two lines instead of being cut off is a quick check worth doing now.

Check it worked

The script prints nine lines. 320, 360 and 599 say compact, 600, 768 and 959 say medium, and 960, 1280 and 1440 say wide. Every line ends sideways scroll no. In shots/pick-a-time-599.png the bar is stacked and in shots/pick-a-time-600.png it is one row with a 200 pixel Continue. Your side-by-side comparison of the three frames lists no structural difference, or each one has a note for the designer.

Step 9 · Clean up

When you have copied what you need into your own project, remove the demo folder, its screenshots and the local Playwright install:

Bash
cd ~
rm -rf ~/larkfield-responsive-demo

Playwright keeps its browser download in a shared cache (~/.cache/ms-playwright on Linux, ~/Library/Caches/ms-playwright on macOS). Remove that folder too if no other project uses Playwright.

Check it worked

ls ~/larkfield-responsive-demo reports that the folder does not exist.

Next steps

Need this done for you?

Padding does this work for growing companies, from the first diagnosis to a system that keeps working.

Digital Transformation

Get new tutorials

New tutorials, about twice a month.