Sharing Our Work Thus Far
Colleagues needed to understand why screen parts now live in one shared library, and why the old practice playground kept breaking.
A new Layer page explains the shared library, what it gives every project and how it beats the old way. The icon docs were tidied and a table bug was fixed.
Documents
With file names, on their own page →Threads
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
One page now explains why the shared library exists, what it provides and how each project uses it.
A page that explains the shared library · came from Mark Parsonopen →
- 26 old one-icon demo pages became a single gallery using the one icon component. In words
- The shared table no longer pulls in an image from another project when it has no rows. 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.
c16-D1 Explain the shared library through its logic and its benefits: composition, one source for every site, and why the old playground kept breaking. — Mark Parson
One page now explains why the shared library exists, what it provides and how each project uses it.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Set out the case for the shared library
Listed what colleagues should hear: build once and compose everywhere, why the old /dev playground broke, one set of parts for the app and the marketing site, live demos ("the feel of the wheel seals the deal"), clean docs and clear roles.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 1
The full record 0 decisions · 5 key-change entries · 435 words · 1 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 c16 →