← Cycles
design · c18archivedstarted Mar 12Auto draft — not yet reviewed

Document UX Table List

Why we did this

The shared table is the most complex part in the library and is used across the product, but its docs were a thin demo unlike real use.

What happened

Eight table demos now use realistic data and line up properly, and a new guide walks from the simplest table to how the product really builds one.

New in this cycleA new guide shows the eight pieces, a simple working table you can copy, and how a real product page splits it up.

Start here

At a glance
3
changes
0
conversations
1
decisions
0
outside helpers

What changed

The two changes that matter most, in plain words. Open any one to see it.

  1. 1

    A new guide shows the eight pieces, a simple working table you can copy, and how a real product page splits it up.

    A guide to building a data table · came from Mark Parsonopen →

  2. 2

    Every use of the table in the product was read, and ten repeating patterns were written down.

    Ten patterns from 36 files · came from Mark Parson

Also in this cycle
  • The demos wrapped the table header twice, which broke the column alignment; removing the extra wrapper fixed all eight. 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.

Someone said

From the record: no recorded conversation behind this one.

We decided

c18-D1 Document the table from how the product really uses it, with a test dataset that mirrors production. — Mark Parson

So now

A new guide shows the eight pieces, a simple working table you can copy, and how a real product page splits it up.

Someone said

From the record: no recorded conversation behind this one.

We decided

c18-D1 Document the table from how the product really uses it, with a test dataset that mirrors production. — Mark Parson

So now

Every use of the table in the product was read, and ten repeating patterns were written down.

Thanks to

People outside Qpoint first. Every thank-you points at something they said or made.

MP
Mark Parson
Qpoint team

Asked for the deep dive and realistic data

Asked to read every use of the table in the product, explain how it is used, decide where its docs belong, and test it on a dataset that mirrors production.

All images

Every picture from this cycle. Click any one to step through them all.

The pairs

A guide to building a data tableNew in this cycle

Everything captured · 1

The full record 0 decisions · 15 key-change entries · 662 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 c18 →

Qpoint Brand Style Guide