Knowledgebase

Keeping Design and Code in Step Print

  • frontenddevelopment, frontend, guide, howto, solution, zillionkinghost, hosting, support
  • 0

Alignment between disciplines.

WHAT CAUSES DIVERGENCE

Designs produced without reference to what exists Components built without reference to the design system Tokens defined separately in each

WHAT PREVENTS IT

A single source for tokens, consumed by both Designs built from the same component set Regular review of built work against intent

WHAT TO SHARE

Token values, ideally generated from one definition.

WHY

Manually synchronised values diverge immediately.

WHAT TO AGREE

That new patterns are added to the system, not created ad hoc.

WHAT TO ESTABLISH

A process for proposing something new.

WHY

Without one, people build their own, and the system fragments.

WHAT TO REVIEW TOGETHER

Built interfaces against designs, before release.

WHAT TO FLAG EARLY

Designs using values outside the system Designs requiring components that do not exist Patterns duplicating something existing

WHAT TO DECIDE

Whether the system changes, or the design does.

WHAT TO DOCUMENT

The decision, either way.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot