Zavon

Approve design changes

Overview

A change to a component or to the design system can change many pages at once, so it goes through approval. The approver reads what changed in words, compares before and after drawings, and sees every page that uses it.

Before you start

To approve, your role needs Approve components and design systems. A role with Publish does not include it. See Roles and access.

The rule Component and design system approval sets who is asked first. See Approvals.

Submit a change

  1. Submit a component

    In the component builder, select Submit for approval. Type a Note, then select the submit button in the dialog.

  2. Submit the design system

    On the System screen, select Save draft. Type a Version note and select Submit for approval.

  3. Wait for the decision

    Wait for an approver. Until then, pages keep the approved version and the screen shows Open the request.

Review the change

  1. Open the request

    In the sidebar, select Workflows › Approvals. Open the request.

  2. Read what changed

    Under What changed, read each change in words, grouped by kind and counted.

  3. Compare the drawings

    Under Before and after, select Desktop or Phone. Before is what pages draw now.

  4. Check where it is used

    Under Where it is used, look at each page that follows the component, before and after.

  5. Decide

    Select Approve. Or select Request changes and type a note for the submitter.

  6. Confirm

    Select the button in the dialog. After an approval, every page that follows the component shows the new version.

A request to approve a new version of a call to action band: the approver, Request changes and Approve, What changed in words, and Before and after drawings
A component change waiting for approval. Shown with a fictional organisation.

Follow or keep a version

Follows the approved version. The page shows each new version as soon as it is approved.

Pinned to a version. The page keeps the version it names. Approving a new version does not change it.

An editor sets this with Version when they select the component on a page. See Build components.

Deprecate a component

  1. Open the list

    In the sidebar, select Theme › Components.

  2. Deprecate it

    Select the archive icon on the card. Pages that use it keep it, but it is not offered for new placements.

  3. Offer it again

    To undo, select the same icon again.

Troubleshooting

If Approve is not on the request, your role cannot approve components and design systems.

If Submit for approval is grey, a version already waits for approval. It must be approved, declined or withdrawn first.

If a list in the drawing is empty, the version is still in review. A repeater shows its empty state in the review drawing.

If the archive icon is grey, your role cannot approve components.

Good to know

Your own changes. If your role can approve, the builder says Save and approve and the Theme screen says Publish. The change goes live at once.

One request at a time. Each component and each theme has at most one open request.

Merge requests. When two people save a component at once, the design approvers also get a merge request. See Edit together.

The theme of the site. Only a design approver can change the theme that the site uses. A new theme from a user who cannot approve waits for approval. See Theme.

Marketplace copies. A component or design system that a user who cannot approve installs from the marketplace waits for approval too. See Marketplace.

The design system. A request for the design system shows a specimen before and after, and the pages of the site.

Technical detail. The stored values are under Technical detail at the foot of the request.

Approvals: who approves, and approval rules.
Build components: build a component and save a version.
Design system: change the design system and publish it.