# Report device palette

These are selectable composition devices. Read the [composition rules](composition.md) first.


Each device below is a layout primitive. Most pages compose **2–4 devices**: one hero plus a few supporting. Some pages need only one.

---

### Prose-with-inline-figures

**What it is.** A single-column body of body-tier paragraphs with figures (charts, structural diagrams, micrographs) embedded inline at the point they're first cited. No tile grid, no parallel columns — a continuous read.

**Best for.** Long-form narrative content where the argument unfolds in order: single-paper summaries, mechanism explanations, structural-biology walkthroughs, opinion / position pieces.

**What the eye lands on.** The first paragraph (the abstract, the TL;DR, the lede). Figures are second; section headings are third.

**Composability.** Pairs well with an outline rail only when the body has at least six substantive sections and exceeds one viewport. Pairs poorly with a KPI tile grid: prose density and tile density read as belonging to different documents.

**Inspiration:**
- [Distill.pub](https://distill.pub/) — figures are the equal of the prose, embedded at the moment they're discussed; sidenotes and margin annotations.
- [Nature article view](https://www.nature.com/) — single-column reading body, figures full-bleed within the column, optional right-side outline.
- [ScienceDirect article view](https://www.sciencedirect.com/) — same pattern, with collapsible section anchors on the left.

---

### KPI tile grid

**What it is.** A row (or two) of equal-sized tiles, each holding one headline number plus a label. Typically 3–6 tiles per row. Near-zero prose inside the grid itself.

**Best for.** Content where the reader's first job is to grasp 3–6 headline numbers at a glance — primary efficacy endpoint, enrollment, response rate, AUC, NOAEL, etc.

**What the eye lands on.** The numbers themselves, all roughly at the same hierarchy level. A tile with `--accent-default` lands first only when the evidence provides a real primary metric; otherwise keep the peers equal.

**Composability.** Pairs naturally with a chart cluster directly below it (numbers explain the charts, charts explain the numbers). Pairs poorly with parallel columns — the two devices both try to chunk the page horizontally and the eye loses the grid.

**Inspiration:**
- [Datadog dashboards](https://www.datadoghq.com/dashboards/) — dense tile grids with status colors and trend deltas.
- [Mixpanel Company KPIs Dashboard](https://mixpanel.com/blog/company-kpis-dashboard-template-release-metrics/) — clean 3–4 tile rows with sparklines.
- Stripe Dashboard public screenshots — KPI tiles with subtle period-over-period deltas.

---

### Chart cluster

**What it is.** Two to six charts grouped on the page, often in a 2×N or 3×N grid, each answering a related question. Distinct from a KPI tile grid in that each cell is a chart, not a single number.

**Best for.** Multi-angle quantitative storytelling: enrollment over time + response distribution + AE incidence + dose-response, viewed together.

**What the eye lands on.** Whichever chart is biggest and/or top-left. Use that slot intentionally.

**Composability.** Sits naturally below a KPI tile grid (numbers then charts). Pairs poorly with prose — long body paragraphs above or below a chart cluster make the page feel like two pages stapled together.

**Color discipline (load-bearing for this device).** Chart chrome stays quiet and neutral. Data marks follow the active product or scientific visualization profile; never invent a report-only palette. `grayC` remains explicit-request-only. One undifferentiated series uses one contrast-safe stop. Multiple colors require multiple documented meanings and a legend or direct labels. Product status semantics apply only to actual product statuses; scientific charts retain their own color mapping.

The test:

1. Cover the segment labels with your hand — can you still tell what the chart is "saying" from the colors alone? If yes, and the colors are carrying ordinal / status meaning, fine. If no, the colors are decoration — strip them.
2. Look at the chart at thumbnail scale: does any segment shout louder than the page-level emphasis (the bracket, the KPI tile, the headline accent)? If yes, lighten that segment — the chart is competing with what should be the focal point.

**Inspiration:**
- [Datadog dashboards](https://www.datadoghq.com/dashboards/) — chart clusters arranged to be read as a coherent system.
- [ClinicalTrials.gov detail page](https://clinicaltrials.gov/) — endpoint and AE charts grouped under tabs.
- [Looker dashboard examples](https://cloud.google.com/looker) — BI-style chart clusters with shared filters.

---

### Sticky infobox

**What it is.** A tall, narrow vertical panel — usually ~280–320px wide, fixed to the right side of the content (sticky on scroll) — holding structured key-value data about a single entity: identifiers, classifications, dosing, image, external links.

**Best for.** Single-entity reference pages where the reader is looking up specific facts and a sectioned long-form body sits to the left as context.

**What the eye lands on.** The entity's image / structural diagram at the top of the infobox, then the first 4–5 key-value rows. The long-form body is secondary.

**Composability.** Pairs naturally with sectioned prose body on the left. Pairs naturally with a structure gallery embedded in the body. Pairs poorly with another sidebar on the left — two sidebars + body is the "v1 same-skeleton" failure mode.

**Inspiration:**
- [Wikipedia Infobox drug template](https://en.wikipedia.org/wiki/Template:Drugbox) — the canonical vital-stats sidebar; tightly compressed key-value rows.
- [DrugBank entry](https://go.drugbank.com) — broader infobox with linked identifiers and external database cross-references.
- [PubChem compound page](https://pubchem.ncbi.nlm.nih.gov/) — image at top, then sections of physical / chemical / pharmacological data.

---

### Wide comparison table

**What it is.** A single horizontally wide table dominates the page; entities are rows, attributes are columns (or vice versa). A short framing paragraph sits above it; per-row callouts or summary notes sit below.

**Best for.** Side-by-side comparison of 2–N entities on the same set of dimensions — competing drugs, trial inclusion criteria, method benchmarks, software products.

**What the eye lands on.** The table itself. The framing paragraph orients but is brief; the callouts elaborate but only after the reader has scanned the table.

**Composability.** Pairs with a small KPI tile row above (the "winner" of the comparison highlighted), but only when there's a clear winner. Pairs poorly with parallel-column devices — the table is already doing column comparison.

**Inspiration:**
- [Capterra side-by-side compare](https://www.capterra.com/compare/) — up to four products in adjacent columns with feature checkmarks.
- [NN/g comparison-tables article](https://www.nngroup.com/articles/comparison-tables/) — the canonical UX-research guide; sticky headers, scannable rows.
- [G2 compare pages](https://www.g2.com/compare/) — comparison tables with star-rated dimensions and inline reviewer quotes.

---

### 2D positioning chart / market map

**What it is.** A two-axis scatter or quadrant chart (e.g. ability-to-execute × completeness-of-vision) **OR** a tile grid where every tile is a logo/entity sorted into named categories. The chart/map is the hero; it occupies the top half of the page.

**Best for.** Competitive landscapes, market overviews, pipeline maps — content where the reader needs to grasp the *shape* of a field before diving into any single entity.

**What the eye lands on.** The chart, immediately. Specifically, the quadrant that contains the leaders (top-right by convention) or the category that's labelled "Leaders." Individual entity cards are second.

**Composability.** Pairs with an asset-card grid directly below (one card per entity that appeared in the chart, in roughly the same order). Pairs poorly with a sticky infobox — the page is about the field, not one entity.

**Interactivity (default).** This device almost always pairs with cards below it; make that relationship navigable. Hover or focus on a point reveals its details and highlights the paired card; the paired card provides the reverse cue. Activating the point brings the card into view. Use stable identifiers and one shared data source for both representations.

**Inspiration:**
- [CB Insights Market Maps](https://www.cbinsights.com/research/market-map/) — logo-grid maps where every player is positioned into a named category; the visual is the whole page.
- [Gartner Magic Quadrant](https://www.gartner.com/en/research/methodologies/magic-quadrants-research) — the canonical two-axis vendor scatter.
- [BCG market-overview decks](https://www.bcg.com/) — narrative-paired positioning charts on a single slide.

---

### Parallel columns

**What it is.** Three or four equally weighted columns side by side, each with the same internal structure (heading + lede + bullets, or heading + chart + bullets). The columns chunk the page horizontally and the reader scans across.

**Best for.** Evidence-type or pillar-style synthesis — three-pillar arguments (genetics / mechanism / pharmacology), pros / cons / verdict columns, before / during / after comparisons.

**What the eye lands on.** The column headings, all at the same level. The reader chooses which to read first based on the headings.

**Composability.** Pairs with a single framing paragraph above the columns and a synthesis paragraph below. Pairs poorly with a KPI tile grid (both try to chunk the page in row-of-tiles fashion).

**Inspiration:**
- [Cochrane systematic-review summaries](https://www.cochranelibrary.com/) — evidence chunks side by side, each with the same internal anatomy.
- [Nature Reviews Drug Discovery](https://www.nature.com/nrd/) target-validation reviews — pillar-style synthesis with parallel sections.
- [The Pudding](https://pudding.cool/) — frequently uses 3-up parallel columns for comparative narratives.

---

### Timeline rail

**What it is.** A vertical (or horizontal) timeline running down (or across) the page with numbered or dated blocks marching along it. Each block holds the content for that step / day / week. The timeline axis is visible and continuous.

**Best for.** Sequential or chronological content where the **order itself is the story**: recipe steps, day-by-day itineraries, week-by-week training programs, drug development milestones, trial timelines.

**What the eye lands on.** Step 1 / Day 1 / Week 1 — the first block. The timeline axis on the left tells the reader there are N more after this one.

**Composability.** Pairs with a small sidebar holding shared resources (ingredients list, packing list, equipment list) when the content has cross-step dependencies. Pairs poorly with parallel columns — both fight for the horizontal axis.

**Inspiration:**
- [NYT Cooking recipe pages](https://cooking.nytimes.com/) — numbered step blocks; an ingredients sidebar carries the cross-step dependencies.
- [Travaa itinerary builder](https://travaa.com/) — day-segmented blocks with maps and activity cards.
- [Nerd Fitness program pages](https://www.nerdfitness.com/) — week-over-week tables with progressive overload.

---

### Structure gallery

**What it is.** A grid of annotated molecular structures (compound images), each labeled with an identifier and a key property (IC50, selectivity, etc). Per-structure annotations highlight the R-group changes between adjacent structures.

**Best for.** Medicinal chemistry storytelling: hit-to-lead optimization, SAR campaigns, scaffold-hopping narratives.

**What the eye lands on.** The grid of structures, scanned left-to-right and top-to-bottom in the order the campaign unfolded. The "winning" compound is usually visually distinguished (larger, accent border, last in the grid).

**Composability.** Pairs with a small radar or property-profile chart per compound (or one summary radar at the end). Pairs naturally with a wide comparison table when the campaign generated systematic SAR data.

**Inspiration:**
- Medicinal chemistry review figures in *J. Med. Chem.* lead-optimization papers — the canonical structure-gallery shape.
- [Practical Cheminformatics blog](http://practicalcheminformatics.blogspot.com/) — Pat Walters' posts often show structure galleries with property annotations.
- [ChEMBL compound assay views](https://www.ebi.ac.uk/chembl/) — structure-with-data tiles, scannable in series.

---
