Cycles
Design · c3

App Migration & Component Documentation

archivedcreated February 2026· last activity 2026-09-11

Why

Components were extracted into q-nuxt-layer during c1–c2, but app.qpoint.io still had local copies. Changes had to be made in two places. The layer was also only partially documented — 12 of 43 components had demos.

Objective

Connect app.qpoint.io to the Nuxt Layer and remove all duplicate local components, then document the previously-undocumented layer components in the design site.

What Was Done

  • Added layer dependency to app.qpoint.io (same tarball pattern as www)
  • Removed 51 local component files (25 UX, 7 table-list, 4 form, 15 icon)
  • Fixed layer bugs discovered during integration (relative imports, missing Tailwind colors)
  • Created 20 new demo files and registry entries in the design site
  • Total documented: 32 of 43 layer components (up from 12)

Outcome

app.qpoint.io consumes 51 components from the layer instead of maintaining local copies. Layer components defined once, consumed by three projects (design, www, app). Design site documents 32 of 43 components with interactive demos.

Visual record

3 captures — heroes, page slices, and full-page renders. Click to view.

c3 hero
c3 slice
c3 full

Qpoint Brand Style Guide