Skip to content
Academy
0/15

Routes

On this page

Build with Milpa · Unit 4 of 4

Compose with @milpa/design

Design ships tokens, motion, primitives, components, artifacts and layouts. It doesn't ship JavaScript: state, data and behavior still belong to the application.

Beginner to intermediate30 min

By the end, you'll be able to

  • Load the six bundles in order
  • Separate the visual contract from product logic

Understand

Design ships tokens, motion, primitives, components, artifacts and layouts. It doesn't ship JavaScript: state, data and behavior still belong to the application.

Consume a published version. Academy can try out ac-* compositions, but it must not duplicate the anatomy of a mui-* piece or read the package's private files.

See

Audit the executable contract

Change theme and surface; the gate computes contrast live.

Do

Run the practice in your checkout and keep the output as evidence.

Verify

Show that you can apply the unit. Progress only advances once you pass the assessment.

Criteria assessed

  • The bundles load tokens, motion, primitives, components, artifacts and layouts, in that order.
  • Progress logic lives in Academy, not in Design.

Graded assessment

Solve the 3 scenarios. This unit requires 3 of 3 correct answers.

0 attempts
Question 1 of 3A new Academy page uses mui-gate and the documentation shell. Which way of loading respects @milpa/design's published contract?
Question 2 of 3Academy needs to save progress, grade quizzes and decide which unit to unlock. Which repository does that logic belong to?
Question 3 of 3A single lesson needs to combine mui-card, mui-steps and a progress summary specific to Academy. No general reusable pattern exists yet. Which implementation respects the governance?

Grading validates answers in this browser; it doesn't certify identity.

Primary sources

Content verified: 2026-07-10