{"course":{"slug":"design-foundations","title":"Design, before Any Software","url":"https://addaly.com/learn/design-foundations","level":"beginner","track":"create"},"lesson":{"slug":"a-system-you-can-build-in-a-day","title":"The afternoon version","url":"https://addaly.com/learn/design-foundations/a-system-you-can-build-in-a-day","position":71,"of":74,"minutes":8,"answer":"A working design system for a small project is about thirty tokens and six components, all derived from decisions already made in the earlier blocks.","keyIdea":"A working design system for a small project is about thirty tokens and six components, all derived from decisions already made in the earlier blocks, and the step that proves it is rebuilding one real screen using nothing else."},"body":{"format":"markdown","text":"## Most of the value, very little of the work\n\nPublished design systems are enormous because they come from companies with dedicated teams and thousands of screens. The version that helps a solo designer or a three-person team is about one per cent of that, and it takes an afternoon.\n\nHere is the whole thing.\n\n## Step 1: the token file\n\nOne CSS file. No build step, no tooling, works everywhere.\n\n```css\n:root {\n  /* neutrals */\n  --grey-50:  oklch(0.98 0.004 255);\n  --grey-100: oklch(0.95 0.006 255);\n  --grey-200: oklch(0.90 0.008 255);\n  --grey-400: oklch(0.72 0.010 255);\n  --grey-600: oklch(0.54 0.012 255);\n  --grey-800: oklch(0.32 0.010 255);\n  --grey-900: oklch(0.20 0.008 255);\n\n  /* brand */\n  --brand-300: oklch(0.75 0.12 255);\n  --brand-500: oklch(0.55 0.18 255);\n  --brand-700: oklch(0.42 0.16 255);\n\n  /* semantic */\n  --colour-text:       var(--grey-900);\n  --colour-text-muted: var(--grey-600);\n  --colour-surface:    white;\n  --colour-raised:     var(--grey-50);\n  --colour-border:     var(--grey-200);\n  --colour-action:     var(--brand-500);\n  --colour-danger:     oklch(0.52 0.19 28);\n\n  /* space */\n  --space-1: 0.25rem; --space-2: 0.5rem;  --space-3: 1rem;\n  --space-4: 1.5rem;  --space-5: 2rem;    --space-6: 3rem;\n\n  /* type */\n  --text-sm: 0.8125rem; --text-md: 1rem;\n  --text-lg: 1.25rem;   --text-xl: 1.75rem; --text-2xl: 2.5rem;\n  --leading-tight: 1.2; --leading-normal: 1.55;\n\n  /* form */\n  --radius-sm: 4px; --radius-md: 8px; --radius-full: 999px;\n  --shadow-md: 0 4px 12px rgb(0 0 0 / 0.08);\n  --dur-fast: 150ms; --ease-out: cubic-bezier(0.2, 0, 0, 1);\n}\n```\n\nThat is roughly thirty decisions. Every one of them came from an earlier block in this course: the lightness ramp, the spacing scale, the modular type scale, two radius values, one shadow agreeing about the light, one duration.\n\n## Step 2: six components\n\nNot sixty. These six cover the overwhelming majority of what a small product or a set of marketing pages needs:\n\n1. **Button**: three variants, two sizes, all six states.\n2. **Text field**: with label, hint and error.\n3. **Card**: surface, padding, optional media slot.\n4. **Heading set**: three levels, with space above and below defined.\n5. **Link**: in-text and standalone.\n6. **Badge or tag**: because every product grows one.\n\nSpecify each with the state table from the previous lesson. Two hours.\n\n## Step 3: rebuild one real screen using only these\n\nThis is the step that makes the exercise worth doing, and the step people skip.\n\nTake an existing screen and rebuild it using nothing but the tokens and the six components. You will immediately discover:\n\n- Values you need that are not in the scale, which are either missing tokens or accidental values in the original.\n- Components you need that are not in the six, which tells you what the seventh should be.\n- Places where the original screen used four greys where the system offers two, and looks no worse for the reduction.\n\nThe third finding is the common one, and it is the system paying for itself on its first day.\n\n## The tools, and what they cost\n\n**For the tokens and components**: a text editor and a browser. Nothing else is required, and a single HTML page showing every component in every state is a perfectly respectable component gallery.\n\n**For visual design files**:\n\n- **Penpot**: open source, free, self-hostable, with components and design tokens. The genuine free alternative.\n- **Figma**: free tier with limits on files and version history; the industry default and what job advertisements name.\n- **Inkscape**: excellent for vector artwork, not a UI design tool.\n- **Sketch** is paid and macOS only; **Adobe XD** has been discontinued.\n\n**For a rendered component gallery**: Storybook is the named industry tool and is free and open source. A hand-written HTML page does the same job for a small project with none of the setup.\n\n## Step 4: write down the six rules you keep\n\nOne short page, and it matters more than it looks. The tokens say what values exist; this says how they are used.\n\nA realistic example:\n\n```\n1. Body text is --text-md at --leading-normal, capped at 34em.\n2. One primary action per view. Everything else is secondary or ghost.\n3. Space between groups is at least three times the space inside them.\n4. Interactive targets are at least 44px, with 8px between neighbours.\n5. Any colour-carried meaning also has an icon or a word.\n6. Motion is 150-300ms, ease-out, and respects reduced-motion.\n```\n\nEvery one of those is a decision from an earlier block, written down so it does not have to be re-argued. Six lines is the right length: a page of forty rules will not be read, and these six catch most of what goes wrong.\n\n## What this does not require\n\nNo build step. No framework. No component library dependency. No design tool subscription.\n\nThat is worth stating plainly, because the visible ecosystem around design systems is expensive and elaborate, and it can make the whole activity look like something that needs funding. It does not. A stylesheet of custom properties, six components written in plain HTML and CSS, an HTML page showing them, and six rules in a text file is a complete and useful design system, and it runs on a laptop that cannot install anything.\n\n## What you have not built\n\nBe clear about the boundary. An afternoon produces tokens and six components. It does not produce contribution guidelines, a versioning policy, a deprecation process, cross-platform token generation, usage analytics or a governance model.\n\nYou do not need any of those yet, and the last lesson in this block is about recognising when you do."},"check":{"question":"A solo designer builds a token file and six components in an afternoon, then rebuilds an existing screen with them and finds the screen needs five greys where the system offers three. What is the most useful interpretation?","options":[{"text":"The system is too restrictive for real work, and the neutral ramp should be expanded until it covers every value the existing screens use.","correct":false,"tempting":"Treats the existing screens as the specification, which imports the accidental values the system was built to remove."},{"text":"The two extra greys are probably accidental values, and the screen should be checked to see whether it looks worse with three.","correct":true},{"text":"The ramp was built with too few steps, and a full 50-to-900 ramp of nine values would have avoided the mismatch entirely.","correct":false,"tempting":"Assumes more steps is the answer without asking whether the original screen's greys were distinguishable or intended."},{"text":"The rebuild should be abandoned, since a system proven inadequate on its first real screen will fail on the remainder and needs more design work before it is applied anywhere.","correct":false,"tempting":"Reads a normal and expected finding as a failure, when the point of the rebuild is to surface exactly this kind of gap."}]},"prev":{"slug":"icons-as-a-system","title":"Icons are a set, not a collection","url":"https://addaly.com/learn/design-foundations/icons-as-a-system"},"next":{"slug":"documenting-and-handing-off","title":"Specifications that survive contact","url":"https://addaly.com/learn/design-foundations/documenting-and-handing-off"},"authorship":"Founder and series editor: Dr Mustafa Mun. Written by AI models to a written standard. Source and assessment review continues. Academic review invited.","review":{"status":"Draft, open for academic review"},"cite":"Addaly (2026) 'The afternoon version', in Design, before Any Software. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/design-foundations/a-system-you-can-build-in-a-day (Accessed: 21 November 2026).","licence":{"name":"CC BY-NC-SA 4.0","url":"https://creativecommons.org/licenses/by-nc-sa/4.0/"},"reader":{"schema":1,"title":"The afternoon version","courseTitle":"Design, before Any Software","module":{"index":7,"slug":"making-decisions-once","title":"Making the decision once"},"answer":null,"keyIdea":"A working design system for a small project is about thirty tokens and six components, all derived from decisions already made in the earlier blocks, and the step that proves it is rebuilding one real screen using nothing else.","hero":{"kind":"plate","image":null,"alt":null,"caption":null},"blocks":[{"t":"h2","id":"most-of-the-value-very-little-of-the-work","runs":[{"text":"Most of the value, very little of the work"}]},{"t":"p","runs":[{"text":"Published design systems are enormous because they come from companies with dedicated teams and thousands of screens. The version that helps a solo designer or a three-person team is about one per cent of that, and it takes an afternoon."}]},{"t":"p","runs":[{"text":"Here is the whole thing."}]},{"t":"h2","id":"step-1-the-token-file","runs":[{"text":"Step 1: the token file"}]},{"t":"p","runs":[{"text":"One CSS file. No build step, no tooling, works everywhere."}]},{"t":"code","lang":"css","label":"CSS","text":":root {\n  /* neutrals */\n  --grey-50:  oklch(0.98 0.004 255);\n  --grey-100: oklch(0.95 0.006 255);\n  --grey-200: oklch(0.90 0.008 255);\n  --grey-400: oklch(0.72 0.010 255);\n  --grey-600: oklch(0.54 0.012 255);\n  --grey-800: oklch(0.32 0.010 255);\n  --grey-900: oklch(0.20 0.008 255);\n\n  /* brand */\n  --brand-300: oklch(0.75 0.12 255);\n  --brand-500: oklch(0.55 0.18 255);\n  --brand-700: oklch(0.42 0.16 255);\n\n  /* semantic */\n  --colour-text:       var(--grey-900);\n  --colour-text-muted: var(--grey-600);\n  --colour-surface:    white;\n  --colour-raised:     var(--grey-50);\n  --colour-border:     var(--grey-200);\n  --colour-action:     var(--brand-500);\n  --colour-danger:     oklch(0.52 0.19 28);\n\n  /* space */\n  --space-1: 0.25rem; --space-2: 0.5rem;  --space-3: 1rem;\n  --space-4: 1.5rem;  --space-5: 2rem;    --space-6: 3rem;\n\n  /* type */\n  --text-sm: 0.8125rem; --text-md: 1rem;\n  --text-lg: 1.25rem;   --text-xl: 1.75rem; --text-2xl: 2.5rem;\n  --leading-tight: 1.2; --leading-normal: 1.55;\n\n  /* form */\n  --radius-sm: 4px; --radius-md: 8px; --radius-full: 999px;\n  --shadow-md: 0 4px 12px rgb(0 0 0 / 0.08);\n  --dur-fast: 150ms; --ease-out: cubic-bezier(0.2, 0, 0, 1);\n}"},{"t":"p","runs":[{"text":"That is roughly thirty decisions. Every one of them came from an earlier block in this course: the lightness ramp, the spacing scale, the modular type scale, two radius values, one shadow agreeing about the light, one duration."}]},{"t":"h2","id":"step-2-six-components","runs":[{"text":"Step 2: six components"}]},{"t":"p","runs":[{"text":"Not sixty. These six cover the overwhelming majority of what a small product or a set of marketing pages needs:"}]},{"t":"ol","start":1,"items":[[{"text":"Button","b":true},{"text":": three variants, two sizes, all six states."}],[{"text":"Text field","b":true},{"text":": with label, hint and error."}],[{"text":"Card","b":true},{"text":": surface, padding, optional media slot."}],[{"text":"Heading set","b":true},{"text":": three levels, with space above and below defined."}],[{"text":"Link","b":true},{"text":": in-text and standalone."}],[{"text":"Badge or tag","b":true},{"text":": because every product grows one."}]]},{"t":"p","runs":[{"text":"Specify each with the state table from the previous lesson. Two hours."}]},{"t":"h2","id":"step-3-rebuild-one-real-screen-using-only-these","runs":[{"text":"Step 3: rebuild one real screen using only these"}]},{"t":"p","runs":[{"text":"This is the step that makes the exercise worth doing, and the step people skip."}]},{"t":"p","runs":[{"text":"Take an existing screen and rebuild it using nothing but the tokens and the six components. You will immediately discover:"}]},{"t":"ul","items":[[{"text":"Values you need that are not in the scale, which are either missing tokens or accidental values in the original."}],[{"text":"Components you need that are not in the six, which tells you what the seventh should be."}],[{"text":"Places where the original screen used four greys where the system offers two, and looks no worse for the reduction."}]]},{"t":"p","runs":[{"text":"The third finding is the common one, and it is the system paying for itself on its first day."}]},{"t":"h2","id":"the-tools-and-what-they-cost","runs":[{"text":"The tools, and what they cost"}]},{"t":"p","runs":[{"text":"For the tokens and components","b":true},{"text":": a text editor and a browser. Nothing else is required, and a single HTML page showing every component in every state is a perfectly respectable component gallery."}]},{"t":"p","runs":[{"text":"For visual design files","b":true},{"text":":"}]},{"t":"ul","items":[[{"text":"Penpot","b":true},{"text":": open source, free, self-hostable, with components and design tokens. The genuine free alternative."}],[{"text":"Figma","b":true},{"text":": free tier with limits on files and version history; the industry default and what job advertisements name."}],[{"text":"Inkscape","b":true},{"text":": excellent for vector artwork, not a UI design tool."}],[{"text":"Sketch","b":true},{"text":" is paid and macOS only; "},{"text":"Adobe XD","b":true},{"text":" has been discontinued."}]]},{"t":"p","runs":[{"text":"For a rendered component gallery","b":true},{"text":": Storybook is the named industry tool and is free and open source. A hand-written HTML page does the same job for a small project with none of the setup."}]},{"t":"h2","id":"step-4-write-down-the-six-rules-you-keep","runs":[{"text":"Step 4: write down the six rules you keep"}]},{"t":"p","runs":[{"text":"One short page, and it matters more than it looks. The tokens say what values exist; this says how they are used."}]},{"t":"p","runs":[{"text":"A realistic example:"}]},{"t":"code","lang":"","label":"Text","text":"1. Body text is --text-md at --leading-normal, capped at 34em.\n2. One primary action per view. Everything else is secondary or ghost.\n3. Space between groups is at least three times the space inside them.\n4. Interactive targets are at least 44px, with 8px between neighbours.\n5. Any colour-carried meaning also has an icon or a word.\n6. Motion is 150-300ms, ease-out, and respects reduced-motion."},{"t":"p","runs":[{"text":"Every one of those is a decision from an earlier block, written down so it does not have to be re-argued. Six lines is the right length: a page of forty rules will not be read, and these six catch most of what goes wrong."}]},{"t":"h2","id":"what-this-does-not-require","runs":[{"text":"What this does not require"}]},{"t":"p","runs":[{"text":"No build step. No framework. No component library dependency. No design tool subscription."}]},{"t":"p","runs":[{"text":"That is worth stating plainly, because the visible ecosystem around design systems is expensive and elaborate, and it can make the whole activity look like something that needs funding. It does not. A stylesheet of custom properties, six components written in plain HTML and CSS, an HTML page showing them, and six rules in a text file is a complete and useful design system, and it runs on a laptop that cannot install anything."}]},{"t":"h2","id":"what-you-have-not-built","runs":[{"text":"What you have not built"}]},{"t":"p","runs":[{"text":"Be clear about the boundary. An afternoon produces tokens and six components. It does not produce contribution guidelines, a versioning policy, a deprecation process, cross-platform token generation, usage analytics or a governance model."}]},{"t":"p","runs":[{"text":"You do not need any of those yet, and the last lesson in this block is about recognising when you do."}]}],"check":{"question":[{"text":"A solo designer builds a token file and six components in an afternoon, then rebuilds an existing screen with them and finds the screen needs five greys where the system offers three. What is the most useful interpretation?"}],"options":[{"text":[{"text":"The system is too restrictive for real work, and the neutral ramp should be expanded until it covers every value the existing screens use."}],"correct":false,"tempting":[{"text":"Treats the existing screens as the specification, which imports the accidental values the system was built to remove."}]},{"text":[{"text":"The two extra greys are probably accidental values, and the screen should be checked to see whether it looks worse with three."}],"correct":true,"tempting":null},{"text":[{"text":"The ramp was built with too few steps, and a full 50-to-900 ramp of nine values would have avoided the mismatch entirely."}],"correct":false,"tempting":[{"text":"Assumes more steps is the answer without asking whether the original screen’s greys were distinguishable or intended."}]},{"text":[{"text":"The rebuild should be abandoned, since a system proven inadequate on its first real screen will fail on the remainder and needs more design work before it is applied anywhere."}],"correct":false,"tempting":[{"text":"Reads a normal and expected finding as a failure, when the point of the rebuild is to surface exactly this kind of gap."}]}],"order":[0,3,1,2],"why":null},"prev":{"slug":"icons-as-a-system","title":"Icons are a set, not a collection","minutes":8},"next":{"slug":"documenting-and-handing-off","title":"Specifications that survive contact","minutes":8}}}