Shared Component Library & Nuxt Layer
Our website and our app each kept their own copies of the same buttons, colors and styles, so every change had to be made twice.
The style guide became a shared kit that other projects plug in with one line. Ten shared parts came first, and nothing in the projects had to be renamed.
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
Other projects now borrow buttons, inputs and colors from one shared place instead of keeping copies.
One shared kit, plugged in with one line · came from Mark Parsonopen →
- 2
Colors, type sizes and corner rounding now come from one settings file.
One source for colors and sizes · came from Mark Parson
- Two short guides now explain how shared parts should be built and which settings to use. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
Other projects now borrow buttons, inputs and colors from one shared place instead of keeping copies.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
Colors, type sizes and corner rounding now come from one settings file.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Built the first shared kit
The record names no one. The commits that carry this work, in design and in the app, are authored by Mark Parson.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 2
The full record 0 decisions · 8 key-change entries · 178 words · 2 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c1 →