Composing an overview page

An overview page is a record page read as a profile: who or what it is, what it adds up to, how it has been active, and what it made. Commons’ member page is the worked example.

A Commons member: a portrait beside the name and standing, the team and town under it, a row of five figures, their own words, and a chart of posts by month.

When the record is a person or a company, dress its name with an avatar (a photo resource where there is one) and a subtitle — commons/resources.ts:41.
Always, use header() for the head, never a custom section that draws the name a second time — commons/pages/member.ts:13.
When its figures are counted from other tables, declare rollups and show them in a summary; a count two references away takes whose: 'post_id.author_id' — commons/resources.ts:37, member.ts:14.
When it has prose of its own (a bio, a description), a one-column fields section after the figures — member.ts:15.
When it has a history over time, a chart of its activity with whose and a reduced height — member.ts:16.
When a dashboard section applies to one record, reuse it narrowed with whose (“this account’s bookings”) — compass/pages/account.ts:14.
When what it made is the point (threads, posts), related lists with a limit and empty: false, and no aside beside them — member.ts:19.

With no aside, the page runs the full width: a metric strip of three (width: 'third') fits it; beside an aside, use the summary. The skeleton for an operational record is Composing a record page.