Getting started
How Meridian is organised and who it is for.
Meridian is the design system for www.commenda.io. It is Pathfinder’s sister: the same tokens, icons and components, with a few additions for marketing pages.
Who it is for
Three readers, three sets of rules.
Designers
- Enable Meridian from the Assets panel for every website file.
- Place components as they are. An override is a bug report: post it, and the fix goes into the library.
- Never detach. If a component cannot do the job, propose a new property.
- Every page and section frame carries its layout grid.
Engineers
- Every variable carries its code syntax; Dev Mode shows it.
- Component and property names match the code, so Code Connect maps one to one.
- Each component has a .md spec in
docs/design-system/meridian. - Token changes land in code and Figma on the same day.
Agents
- Read a component’s description before using it: it names the source, every property and the rules.
- Variant property names are prop names; values are prop values (
variant=primary,size=xl). - Use only Meridian. Never reach into Pathfinder or anything on
_Internal. - Two fonts only: Baskervville Medium and Inter.
How the file is organized
Pages run from foundations to components, grouped under dividers in the page list.
| Group | Pages |
|---|---|
| Start here | Cover, Getting started, Changelog |
| Foundations | Color, Typography, Spacing radius and size, Layout, Elevation and borders, Motion, Icons, Flags, Logos |
| Actions | Button, IconButton, SegmentedControl |
| Inputs | Input, Textarea, Select, Multi-select, Tag, Pill, PhoneInput, AddressInput |
| Selection controls | Checkbox, Radio, Switch |
| Data display | Badge, Eyebrow, Table, Calendar |
| Product elements | Dialog, Popover. Used in website animations and product shots. |
| _Internal | Parts the components are built from. Never place them in a design. |
How a component page works
Every component page has the same parts, in the same order, as in Pathfinder.
- A header card with what it is for, and a link to its .md.
- Live examples of each variant and state, built from the real component.
- An anatomy blueprint, with its measurements and tokens.
- Best practices, ending with its source: Pathfinder or Meridian.
- The component set sits to the right of the docs, in a section named Component · Name.
Where things live
Three places, one source each.
- Figma: this file, Meridian. Components, variables, styles and the docs pages.
- Specs:
docs/design-system/meridian, one .md per component, plus llms.txt for agents. - Code:
web/packages/meridianand the website app, using@commenda/pathfinderwhere the part is unchanged.
Notes
- Most of Meridian is Pathfinder. Every component and token says its source in its description.
- Meridian adds: the 40 control (Button xl, all fields), Button link-arrow, Tag md 24, the Web type roles, Label/14 and Label/16, shot/lift/ring shadows, pop/glide easings, four website grids, Eyebrow, brand logos and the Commenda submark.
- Modelled on Pathfinder’s Getting started page.