From design to build
Take a design from your design system into a session that builds it: requests, review on live frames, releases, updates and the X-ray.
In the pilot
The design system module is in the pilot. It is on for pilot orgs first. An org admin can tell you whether yours has it.
Northwind's checkout needs a step indicator. Olivia maintains Northwind UI, the design system. Dan builds the checkout in Northwind Shop, a product that uses Northwind UI. This page follows the part from a missing component to a built, checked page, and links the Design system page for each step.
Before you start:
- Your org needs the
designmodule. EasyCode staff can close the design system pages with thedesignkill switch. - Northwind Shop declares Northwind UI under Systems it uses on its Design system tab. See Design in every session.
- Review comments posted to GitHub, docs publishing and the X-ray run in the desktop app.
Walk it through
Dan's session knows the system
Dan starts a session on his checkout task. The session is told which release of Northwind UI the product is on, and
reads its components and tokens from org/design.tsv. It builds with the system's parts and stops when one is
missing, rather than inventing one. See The design system record.
The session files a request, and the task waits
There is no step indicator in Northwind UI. The agent proves it: no component, no variant, no composition of existing ones. Dan chooses "a request". The agent files a design request on Northwind UI with the proposed part, or makes the task wait on an open request that asks for the same thing.
Dan's task becomes Blocked, and its card reads "Waiting on" the request. See Design requests.
Olivia triages and builds the part
On Northwind UI's Requests, Olivia presses Accept, assigns herself and sets a priority. She builds the component in the system's repo and opens a pull request. The request moves to In review. If the change spans several repos, Open changes shows every pull request in one place. See Open changes across repos.
Review the change on live frames
From Open changes, Olivia's teammates press Review on the pull request's lane. The default branch sits on one
side and the pull request on the other, each story running live, by theme and device. They pin comments on a tile,
then Approve or Request changes. In the desktop app, both post to GitHub with the reviewer's own gh login.
See Review a design change on live frames.
The release closes the request
When the pull request merges, the request reads "Merged, waiting for release". It is not done yet: nobody should build on a part that is not out. Olivia tags the release. The request reads "Released in Northwind UI 1.3.0" and closes, and Dan's task returns to To do. Dan is told.
The product gets its update task
Northwind Shop is still on 1.2.0. When the system is marked Required and the gap changes a component the product uses, EasyCode opens one update task, such as "Update Northwind UI: v1.2.0 to v1.3.0", listing what changed. A later scan that finds the product on the latest release marks it done. See Found versions and update tasks.
Publish the docs for the release
The release comes with its docs: a page per component and per token group. Olivia opens the release's Docs block and presses Publish docs to send them to the docs repo as a pull request. Publishing runs in the desktop app. See Docs from the record.
Dan builds, and the X-ray checks it
Dan's session builds the checkout with the new component. In the session's browser pane, he opens Tools and turns on X-ray. Each element is labelled System, Old kit, One-off or Unlabelled. A one-off that should be a component becomes a request with File request.
When the agent proves the change, Dan asks it to pass conformance: true to proof_run. The pull
request then carries a Design conformance block with the counts per flow. See
X-ray and conformance.
Where does the team talk it through?
On a design board on the Studio home, the team places live frames of the system's stories and of prototypes, plus stickies and cards for the request and the task. Everyone with edit access works on it at the same time. See The design board.
Related
Something wrong or missing? Suggest a change
From acceptance criteria to QA sign-off
Turn a spec's acceptance criteria into checks, prove them in the built-in browser, report bugs and sign the work off.
Ship and announce a feature
Release a merged feature with a gated workflow, then tell people with a launch post, a walkthrough, a deck or a film.