Tables and charts.
The people reading this site check numbers for a living. A table here is ruled like the parts list or the revision block on a drawing, and a chart is labeled so it can be read without its colors. Every figure says what it counts and where it comes from.
Playground.
The four tables the site prints, as the real components, on either stock.
Drawing list
Strut assembly, forward
18 sheets · 1 assembly · 41 minutes
| Sheet | Part no | Title | Rev | Std | Drafted |
|---|---|---|---|---|---|
| 001 | DFT-40120 | Bracket, forward mount | B | Y14.5 | |
| 002 | DFT-40121 | Fitting, feed line | A | Y14.5 | |
| 003 | DFT-40122 | Doubler, skin splice | A | Y14.5 | |
| 004 | DFT-40123 | Standoff, avionics tray | C | Y14.5 | |
| 005 | DFT-40124 | Cover, access panel | A | Y14.5 | |
| 006 | DFT-40125 | Clip, harness routing | A | Y14.5 |
import { DrawingPackage, PACKAGES } from "#/ui/site/drawing-package";
<DrawingPackage {...PACKAGES.aerospace} />
// or: title, meta, rows, sheets, draftedAnatomy of a table.
- A real table. A
tablewith header cells, never a grid of divs, and never a picture of one: a screenshot of a table in a ported post is rebuilt as a table. - Header in annotation type. Mono, uppercase, 10 to 11px, faint, over a rule.
- Rules, not fills. Hairlines between rows and, where the columns need it, between columns. No zebra stripes, no shaded cells, no shadow.
- Identifiers in mono. Sheet numbers, part numbers and revisions in Plex Mono with tabular figures; titles and labels in Switzer.
- One column may carry the redline. The comparison’s Drafter column is the only colored thing in its table.
- It scrolls on a phone. A table that does not fit scrolls inside its own box. It does not drop the columns that make it the document it is.
The four tables.
- Drawing list. The flagship artifact on the industry pages: sheet, part number, title, revision and standard, in the order a release package prints them, with a footer saying the rest continue. The part numbers are made up and the table says it is illustrative.
- Comparison. On /product-features: three ways a team gets production drawings, checked or crossed. The other columns get a check where it is true (outsourcing does free your engineers; in-house does keep your data), because a comparison where only one column ever scores is not believed.
- Revision record. On /drafter-for-defense: a drawing’s revision block filling in as the model is revised and run again. A program office audits a record, so the page shows one.
- Reference. In a post, a chart from a standard or a handbook, rebuilt as a table so it reads on a phone and can be searched, with its figure number and caption.
The working.
A calculator shows its arithmetic. The savings calculator’s Show the math is a table of every line with the reader’s own numbers in it: today, with Drafter, and the difference, with each source footnoted in the order it is first cited and each estimate labeled as one. See it on /savings-calculator.
Donut and key.
The savings calculator’s time result, live. Point at a slice or a row and the two light together; point at a dotted term and it defines itself. Every slice has its label and value in the key, so the chart reads without its colors.
Engineering time saved per year
5.3 engineers
Full time, or about 9,500 hours a year.
- Making each new drawing. With Drafter, a simple one takes 20% of today's time, a typical one 25% and a complex one 30%.4,200 hours
- Checking each new drawing before release. With Drafter, 10% of today's time.2,700 hours
- Changing a drawing after release and checking it again. With Drafter, 25% of today's time, our estimate.2,500 hours
Show codeHide code
// From /savings-calculator, at its opening values.
<Result label="Engineering time saved per year" value="..." rows={rows} active={active} setActive={setActive} />
<Donut rows={rows} active={active} setActive={setActive} center="..." sub="engineers" />Charts.
- A chart only when the shape matters. A single figure is a number in type, not a chart.
- One color family. The redline and its warm neighbors, so the page keeps its one hue. The savings donut is redline, a burnt orange (#8a3a10) and an amber (#dba550), checked with a color-vision validator against paper.
- Color is never the only label. Every slice has its name and value in the key beside it.
- Chart and key are linked. Pointing at a slice lights its row and fades the rest, and each row’s term defines itself on hover, focus or a tap.
- Proof is drawn as instruments. The homepage’s four figures draw themselves in the site’s linework rather than sitting as big numbers. See Proof.
Numbers.
- Digits and units. 41 minutes, 18 sheets, ±.005. The unit goes in the cell or in the column’s header, never nowhere.
- Tabular figures wherever numbers line up in a column or change in place.
- No false precision. Results the reader’s inputs drive are rounded to two significant figures. An estimate is shown as an estimate, and kept out of the headline number.
- Say where a number comes from. A customer’s figure is credited to the customer, a study’s to the study, and Drafter’s own working figures are called that.
Best practices.
Do
- Use a real table, with header cells.
- Put identifiers in mono and numbers in tabular figures.
- Give every slice of a chart its label and value.
- Let a wide table scroll inside its own box.
Don't
- Do not shade rows or cells.
- Do not use a second accent color in a table.
- Do not chart a single number.
- Do not show more precision than the inputs have.