# Meeno Zen Design System: adoption checklist

Version 1.17 | 2026-09-14

## Included references

- [Complete guide](https://meenozen.com/brand/assets/guide.md)
- [Project-specific tokens](https://meenozen.com/brand/assets/tokens.json)
- [Semantic CSS variables](https://meenozen.com/brand/assets/tokens.css)
- [Pattern register](https://meenozen.com/brand/assets/patterns.json)
- [Visual system and identity downloads](https://meenozen.com/brand)

These files share one version. CSS exports require deliberate import; existing pages do not all consume them. Implemented references are source examples, not a packaged component library. Client marks and font redistribution rights are not included.

## Before design

- Confirm audience, decision, verified claims, content owner and publication scope.
- Choose a page recipe and record the adopted system version.
- Request approved project assets and confirm font licences.
- Read the reference source and its state contract before reproducing it.

## During implementation

- Preserve brand roles, typography, evidence distinctions and clear navigation.
- Keep complete case anatomy and natural content height.
- Define default, focus, expanded, empty, error, pending and recovery states where relevant.
- Use native semantics; test keyboard operation and focus return.
- Keep client demonstrations visually scoped and speaker notes in a companion window.
- Record exceptions and source paths in the receiving project.

## Before acceptance

- Compare desktop, tablet and 320 px reflow; test both sides of changed breakpoints.
- Test long copy, absent media, filter resets, direct links and browser history.
- For collections, check reorder, exit, entry, rapid input, focus continuity and immediate reduced-motion states.
- Verify publication-time provenance and sorting separately from motion; never invent timestamps or popularity.
- Check reduced motion, zoom, contrast and usable target sizes.
- Verify downloads and supporting evidence against visible claims.
- Run the receiving project's checks and record actual browsers and limitations.
- Obtain publication approval for the validated preview, then verify public routes.

## Upgrade from 1.12

Keep /brand and existing file addresses. Adopt the collection interaction and motion contracts where relevant; use the Writing reference and exported motion values deliberately. The publication-timestamp correction remains outstanding and must be verified separately. Preserve prior guidance: adopt the shared Work/Writing/Contact navigation and six homepage chapters. Use the Writing catalogue for homepage entries and sitemap. Reuse hero art for covers; use writing-editorial.css for semantic prose hierarchy, full-width infographic references with accessible text and optional closing takeaway downloads. Remove article-local trial CSS and inline quote floats. Test library URL state, pagination, empty results, companion inputs and exports. Run a content-specific evidence and visual review before requesting publication approval. The guide, tokens and pattern register must share version 1.17.