cyc-stack 0.9.1 → 0.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/plugin.json +1 -1
- package/.codex-plugin/plugin.json +1 -1
- package/.cursor-plugin/plugin.json +1 -1
- package/README.md +3 -2
- package/bin/cyc.mjs +72 -20
- package/docs/README.md +2 -0
- package/docs/context.md +18 -10
- package/docs/project-tools.md +2 -12
- package/docs/runtime.md +5 -1
- package/docs/work-assessments.md +4 -4
- package/docs/work-queue.md +187 -0
- package/methods/cyc-build/SKILL.md +1 -1
- package/methods/cyc-context/SKILL.md +28 -20
- package/methods/cyc-context/references/evidence.md +1 -1
- package/methods/cyc-context/references/templates.md +30 -18
- package/methods/cyc-design/frontend-design/SKILL.md +132 -21
- package/methods/cyc-design/frontend-design/references/color.md +43 -56
- package/methods/cyc-design/frontend-design/references/craft-rules.md +17 -14
- package/methods/cyc-design/frontend-design/references/decision-sheet.md +95 -93
- package/methods/cyc-design/frontend-design/references/experience-review.md +15 -6
- package/methods/cyc-design/frontend-design/references/field-guide.md +439 -0
- package/methods/cyc-design/frontend-design/references/generic-tells.md +83 -32
- package/methods/cyc-design/frontend-design/references/layout-archetypes.md +5 -5
- package/methods/cyc-design/frontend-design/references/patterns.md +108 -0
- package/methods/cyc-design/frontend-design/references/reference-standards.md +118 -22
- package/methods/cyc-design/frontend-design/references/typography.md +59 -44
- package/methods/cyc-design/frontend-design/references/ux-foundations.md +2 -1
- package/methods/cyc-design/frontend-design/references/visual-material.md +43 -8
- package/methods/cyc-design/frontend-design/scripts/contrast.mjs +39 -0
- package/methods/cyc-design/frontend-design/scripts/first-screen.mjs +911 -0
- package/methods/cyc-design/frontend-design/scripts/photo-text.mjs +230 -0
- package/methods/cyc-verify/SKILL.md +1 -1
- package/package.json +6 -1
- package/plugin.json +1 -1
- package/scripts/catalog.mjs +5 -3
- package/scripts/context-review.mjs +364 -261
- package/scripts/hub-page.mjs +275 -0
- package/scripts/hub.mjs +139 -0
- package/scripts/project-tools.mjs +14 -6
- package/scripts/queue-board.mjs +287 -0
- package/scripts/queue.mjs +283 -0
- package/scripts/run-gate.mjs +8 -5
- package/scripts/runtime.mjs +270 -19
- package/scripts/source-snapshot.mjs +20 -2
- package/scripts/work-review.mjs +4 -3
- package/skills/cyc/SKILL.md +12 -4
- package/skills/cyc/references/playbooks/experience.md +2 -0
- package/skills/cyc/references/playbooks/plan.md +2 -0
|
@@ -1,29 +1,62 @@
|
|
|
1
1
|
# Generic tells
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
These are the sites a model writes when nobody tells it otherwise. Learn them so you can recognize them in your own output. There are two opposite ways to miss: a brochure, good to look at with nothing to do, and a bare page, with plenty to do and nothing to look at. Score the requested surface. Apply brochure length, visual inventory and destination checks to a full visual site. For a bounded task view, inspect the actual records, task, state and access needs recorded before implementation. Count the applicable tells present. Any brochure tell (23 to 28) fails the page, and so do tells 21, 34, 39 and 40. Otherwise three or more tells fail it, and the repair is a different decision, not a different color. One or two: fix them before extending the work.
|
|
4
4
|
|
|
5
|
-
## The
|
|
5
|
+
## The brochure
|
|
6
|
+
|
|
7
|
+
These come first because styling cannot repair them. On 2026-11-21 two builders given “Build a website for a neighborhood bicycle repair shop” each produced a single page under three screens tall with seven things to act on in its first screen. One of them was using an earlier version of this method.
|
|
8
|
+
|
|
9
|
+
23. A full-site brief was reduced to one page. The navigation scrolls to sections of the same page and no link leads to another page of the site.
|
|
10
|
+
24. The first screen is a slogan, a sentence, one or two buttons and one picture. Fewer than twelve things to act on at desktop width.
|
|
11
|
+
25. The visitor is meant to compare options but is missing available records or the facts needed to choose, such as price, time, date, size or status.
|
|
12
|
+
26. No task a visitor can finish. Every button scrolls, opens a mail link or shows a message; nothing is searched, filtered, booked, built or checked.
|
|
13
|
+
27. Nothing is true now. Hours, dates and availability are written into the copy, so the page says the same thing at midnight as at noon.
|
|
14
|
+
28. A whole visitor-facing site ends before its promised inventory, evidence or next action. Three screens is the full-homepage benchmark. A requested single working view can fit in one screen.
|
|
15
|
+
|
|
16
|
+
## The bare page
|
|
17
|
+
|
|
18
|
+
This is what a builder produces when told only to add substance. On 2026-11-21 a barbershop built that way had six pages and a booking a visitor could finish, and its owner judged it worse than the one-page site built with no method at all. It read as a form.
|
|
19
|
+
|
|
20
|
+
34. On a visual public homepage the first desktop screen holds fewer than four pictures and none covers a quarter of it.
|
|
21
|
+
35. On a page whose promise depends on imagery, the first phone screen and the one after it hold no picture.
|
|
22
|
+
36. The choice depends on appearance or physical condition, but the entries show only text or initials. A status-first view can show comparable facts and put a useful photograph in the detail view.
|
|
23
|
+
37. One visual weight: every control, label and fact in the first screen is small, outlined in gray and about the same size, so nothing leads. No headline, no dominant picture and no field of color.
|
|
24
|
+
38. Small controls packed in to raise the count of things to act on: rows of outlined chips under 40 px tall, or a main button under 44 px.
|
|
25
|
+
39. The opening hides the material needed to choose. Examples include an invitation with no visible people or date, a finder with no comparable options, or a working view buried under a decorative campaign.
|
|
26
|
+
|
|
27
|
+
## The unchosen look
|
|
28
|
+
|
|
29
|
+
A page can avoid every tell above and still look like nobody decided anything. The look is five choices made from the subject and written in the decision sheet. No canvas, typeface or palette is a tell by itself; an unchosen one is, and so is the one pairing builds without this method reach for.
|
|
30
|
+
|
|
31
|
+
29. The look was not chosen: the sheet's canvas, type voice, corners or color source is missing, or its reason would fit any business.
|
|
32
|
+
30. The page matches the line written under “Without this method I would have built”: the same canvas, the same type voice and the same opening.
|
|
33
|
+
31. No signature move: nothing in the first screen that a different business's site could not also carry unchanged.
|
|
34
|
+
32. Nothing carries color: neither photographs, nor content, nor artwork, nor a field of the brand color. The page is black, white and gray with colored buttons.
|
|
35
|
+
33. Two sites built in the same request share a canvas, a type voice and a header arrangement.
|
|
36
|
+
40. The look builds without this method chose: a warm tint (cream or paper) behind most of the text with a serif headline, when no brand you were given sets them. Three of three such builds set the page background to cream, and two set the headline in Fraunces. Either one alone is a choice.
|
|
37
|
+
|
|
38
|
+
## The older default page
|
|
6
39
|
|
|
7
40
|
Layout
|
|
8
41
|
|
|
9
42
|
1. Centered hero: headline, one-sentence subhead, two buttons (filled and outline), everything centered, nothing else in the first viewport.
|
|
10
|
-
2. Three equal cards in a row, each with an icon in a tinted circle, a bold title and two lines of text. Repeated as
|
|
43
|
+
2. Three equal cards in a row, each with an icon in a tinted circle, a bold title and two lines of text. Repeated as “features”, “services” and “why us”.
|
|
11
44
|
3. Every section built the same way: the same max-width container, the same vertical padding, a centered heading and centered subhead, then a grid.
|
|
12
45
|
4. White and light gray (`#f9fafb`, `#f3f4f6`) alternating as the only rhythm.
|
|
13
46
|
5. A testimonials row of three quote cards with avatar circles, and a stats row of four numbers nobody measured (10k+, 99%, 24/7, 4.9 stars).
|
|
14
|
-
6. A footer with four
|
|
47
|
+
6. A footer with four columns of links and a copyright line, however small the site.
|
|
15
48
|
|
|
16
49
|
Type
|
|
17
50
|
|
|
18
|
-
7.
|
|
19
|
-
8. Display text at 36 to 48 px with default letter-spacing and line-height 1.2, so the headline reads as large body text.
|
|
20
|
-
9.
|
|
51
|
+
7. Several type families where one would do: a display face, a text face, a label face and a fallback all visible in the first screen.
|
|
52
|
+
8. Display text at 36 to 48 px in a regular or bold weight with default letter-spacing and line-height 1.2, so the headline reads as large body text. A deliberately light 40 px line is a [voice](typography.md#voices), not this.
|
|
53
|
+
9. Interface text set large: navigation, labels and facts at 18 px or more, so few items fit and the page reads as a poster.
|
|
21
54
|
10. Centered text everywhere, including paragraphs.
|
|
22
55
|
|
|
23
56
|
Color and surface
|
|
24
57
|
|
|
25
|
-
11.
|
|
26
|
-
12.
|
|
58
|
+
11. The accent color on the button, every icon and an arbitrary headline word, so nothing says which is the action.
|
|
59
|
+
12. More than one brand color competing: two saturated hues given equal area.
|
|
27
60
|
13. Border-radius 12 to 16 px and a soft drop shadow on every box; cards inside cards.
|
|
28
61
|
14. A gradient blob, glass panel or mesh background behind the hero.
|
|
29
62
|
|
|
@@ -31,14 +64,14 @@ Imagery and copy
|
|
|
31
64
|
|
|
32
65
|
15. Emoji as icons, or several icon sets at different stroke widths.
|
|
33
66
|
16. A category illustration (a cup, a camera, a house outline) stretched to hero size, or a stock-style photo unrelated to the copy.
|
|
34
|
-
17. Headlines that could head any business:
|
|
35
|
-
18. Placeholder specifics:
|
|
36
|
-
19. A pill badge above the headline reading
|
|
37
|
-
20. The phone layout is the desktop layout stacked: hero text still centered, the three cards now three tall cards.
|
|
67
|
+
17. Headlines that could head any business: “Welcome to [Name]”, “Quality you can trust”, “Keep on rolling”, “Crafted with care”, “Elevate your experience”.
|
|
68
|
+
18. Placeholder specifics: “123 Main Street”, “John Doe”, “$99/month”, “Since 1995”, “Lorem ipsum”.
|
|
69
|
+
19. A pill badge above the headline reading “✨ Now live” or “New”.
|
|
70
|
+
20. The phone layout is the desktop layout stacked: hero text still centered, the three cards now three tall cards, and no route to the main task that stays within reach.
|
|
38
71
|
|
|
39
|
-
The opposite failure
|
|
72
|
+
The opposite failure
|
|
40
73
|
|
|
41
|
-
21. Wall of text: no photograph, rendered object
|
|
74
|
+
21. Wall of text: no photograph, rendered object or color surface at least a quarter of the viewport wide anywhere within the first two viewports. See the [density rule](visual-material.md#the-density-rule). On a task-dense screen, judge whether the records and actions make the task legible.
|
|
42
75
|
22. Flat page: every section sits on the same canvas with the same content column; no full-bleed band, no panel, no change of surface for item-like content.
|
|
43
76
|
|
|
44
77
|
## Escaping each tell
|
|
@@ -47,30 +80,48 @@ Each row is a different decision, not a style.
|
|
|
47
80
|
|
|
48
81
|
| Tell | Replace with |
|
|
49
82
|
| --- | --- |
|
|
50
|
-
|
|
|
51
|
-
|
|
|
52
|
-
|
|
|
83
|
+
| 23 Incomplete site | Restore missing destinations from the agreed inventory. An expressly single view can use in-place states |
|
|
84
|
+
| 24 Slogan opening | The first screen of the chosen [site model](reference-standards.md): the task entry or the items themselves, real navigation and what is true now |
|
|
85
|
+
| 25 Nothing to choose | The records from the inventory, each with its facts in the same place |
|
|
86
|
+
| 26 No task | One journey built end to end with its confirmation, empty state and error state |
|
|
87
|
+
| 27 Nothing true now | Open or closed, the next date and availability computed from the data file |
|
|
88
|
+
| 28 Incomplete visit | Restore the missing evidence or next action within the agreed scope |
|
|
89
|
+
| 34, 35 No pictures | A first screen from the chosen model with its photograph, its items or its product in it; see [visual material](visual-material.md) for where pictures come from |
|
|
90
|
+
| 36 Missing visual evidence | Show equally framed examples when visitors choose by appearance, or a useful inspection photo where condition matters |
|
|
91
|
+
| 37 One visual weight | One thing that leads: the model's photograph, its items, or a headline in the chosen [type voice](typography.md#voices) |
|
|
92
|
+
| 39 Missing decision evidence | Restore the material promised in the sheet: the scene and date, comparable items, inspectable example, or records and their controls |
|
|
93
|
+
| 38 Small packed controls | Fewer, larger controls: main buttons 44 to 56 px tall, choices as cards or rows a thumb can hit |
|
|
94
|
+
| 29, 30 Look not chosen | The five choices in [Step 3](../SKILL.md#step-3-choose-the-look-from-the-subject), each with a reason only this subject gives |
|
|
95
|
+
| 31 No signature move | One or two moves taken from the subject and repeated down the page |
|
|
96
|
+
| 32 Nothing carries color | A [color source](color.md#where-the-color-comes-from) that suits the subject |
|
|
97
|
+
| 33 Sites that match | A different canvas or type voice for each site, chosen from its own subject |
|
|
98
|
+
| 40 Unguided look | A white or dark canvas under the serif, or a warm tint under another [type voice](typography.md#voices), chosen from the subject |
|
|
99
|
+
| 1 Centered hero | The model's first screen. For a section, a composition from the [catalog](layout-archetypes.md) |
|
|
100
|
+
| 2, 3 Equal cards, identical sections | Structure that follows the content: a process as a numbered list, a menu as a price list with hairline rules, work as a grid with one lead item, a comparison as a real table |
|
|
101
|
+
| 4 Gray and white alternation | Rhythm by density and surface: one dark or brand-colored section, one full-bleed image band, one quiet section at a narrow measure |
|
|
53
102
|
| 5 Invented stats and quotes | Specific proof: a real menu with prices, a named project with its brief, a plan table with actual limits. Or nothing |
|
|
54
|
-
| 6 Four-column footer | A footer proportional to the site:
|
|
55
|
-
| 7 to 9
|
|
56
|
-
| 11, 12
|
|
57
|
-
| 13 Rounded and shadowed | One
|
|
58
|
-
| 15, 16 Emoji, category clip art | One icon set at one stroke width;
|
|
59
|
-
| 17, 18 Generic copy | Copy made of this business's nouns
|
|
60
|
-
| 19 Pill badge |
|
|
61
|
-
| 20 Stacked phone |
|
|
62
|
-
| 21 Wall of text | Material from [visual material](visual-material.md):
|
|
63
|
-
| 22 Flat page | One full-bleed image or color band, a tinted panel behind item-like content
|
|
103
|
+
| 6 Four-column footer | A footer proportional to the site: the pages, the address, the hours and a contact |
|
|
104
|
+
| 7 to 9 Type | One [voice](typography.md#voices), each family with one job. Interface text at 12 to 16 px. Display scale for an invitation or a compact heading above comparable facts |
|
|
105
|
+
| 11, 12 Color | One color for the main action and a quiet second button. See [color](color.md) |
|
|
106
|
+
| 13 Rounded and shadowed | One radius family; hairline borders or flat blocks; shadows only on things that float |
|
|
107
|
+
| 15, 16 Emoji, category clip art | One icon set at one stroke width; photographs of this business's real things, framed alike |
|
|
108
|
+
| 17, 18 Generic copy | Copy made of this business's nouns and numbers: the job, the price, the street, the turnaround, the date |
|
|
109
|
+
| 19 Pill badge | Remove it unless it states something true now, such as today's hours |
|
|
110
|
+
| 20 Stacked phone | The model's phone pattern: a bottom bar or pinned search, items two across or as a compact list, the action before the explanation |
|
|
111
|
+
| 21 Wall of text | Material from [visual material](visual-material.md): photographs, the product rendered as an object, a color surface holding content |
|
|
112
|
+
| 22 Flat page | One full-bleed image or color band, a tinted panel behind item-like content |
|
|
64
113
|
|
|
65
114
|
## Score sheet
|
|
66
115
|
|
|
67
|
-
|
|
116
|
+
Score the designed view in its ordinary presentation. A system font, simplified layout or system color supplied by the visitor's zoom, font or forced-colors settings is an adaptation to respect. A treatment required by an existing brand is recorded in the decision sheet and not counted. A passing score never offsets a barrier found on the primary path.
|
|
117
|
+
|
|
118
|
+
Record this for the first screen and for the finished site, at desktop and phone width:
|
|
68
119
|
|
|
69
120
|
```text
|
|
70
121
|
View: desktop 1440 | phone 390
|
|
71
|
-
|
|
72
|
-
|
|
122
|
+
First-screen judge: [the pass and FAIL lines it printed]
|
|
123
|
+
Tells present: [numbers] Count: N Check: fail for any of 21, 23 to 28, 34, 39, 40, or count >= 3
|
|
73
124
|
Changed decisions: ...
|
|
74
125
|
```
|
|
75
126
|
|
|
76
|
-
Counting is deliberate. It stops
|
|
127
|
+
Counting is deliberate. It stops “it feels fine” from passing a page a reviewer recognizes as default at a glance. The count is a self-review, not a measurement of quality. A page can score zero and still be weak, which the [experience review](experience-review.md) exists to catch.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Layout archetypes
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Use these sketches and CSS examples to compose a section once the [site model](reference-standards.md) and its content are decided. They arrange content; they do not supply it, and none of them is a site. Retain established layouts when the brief calls for them.
|
|
4
4
|
|
|
5
5
|
Column widths below assume a 12-column grid on a 1280 px content width with full bleed allowed outside it.
|
|
6
6
|
|
|
@@ -52,7 +52,7 @@ Fits: a service with one strong photograph of the work or the person. Phone: ima
|
|
|
52
52
|
.next { margin-top: -4rem; position: relative; }
|
|
53
53
|
```
|
|
54
54
|
|
|
55
|
-
The scrim covers only the text half; the subject keeps its detail. Fits: a product with a person in it, hospitality, anything where atmosphere is the promise. Phone: change `object-position` to keep the subject, scrim from the bottom, text at the bottom of the scene.
|
|
55
|
+
The scrim covers only the text half; the subject keeps its detail. Fits: a product with a person in it, hospitality, anything where atmosphere is the promise. Phone: change `object-position` to keep the subject, scrim from the bottom, text at the bottom of the scene. Seen on a studied service site.
|
|
56
56
|
|
|
57
57
|
## 3. Typographic poster
|
|
58
58
|
|
|
@@ -91,7 +91,7 @@ No image in the opening; a full-bleed photograph or rendered object must arrive
|
|
|
91
91
|
.tool form { display: grid; grid-template-columns: 1fr auto; gap: 0.75rem; }
|
|
92
92
|
```
|
|
93
93
|
|
|
94
|
-
The main action is the opening; explanation follows. Fits: catalogs, registrations, quote finders, anything the visitor came to use. Phone: the card fills the width with 16 px gutters; the input and button stack.
|
|
94
|
+
The main action is the opening; explanation follows. Fits: catalogs, registrations, quote finders, anything the visitor came to use. Phone: the card fills the width with 16 px gutters; the input and button stack. Seen with a postal-code input beside the primary action.
|
|
95
95
|
|
|
96
96
|
## 5. Editorial grid
|
|
97
97
|
|
|
@@ -129,7 +129,7 @@ One item leads; the others are secondary on purpose. Fits: portfolios, menus wit
|
|
|
129
129
|
.row-3 { display: grid; grid-template-columns: repeat(3, 1fr); gap: 1.5rem; }
|
|
130
130
|
```
|
|
131
131
|
|
|
132
|
-
|
|
132
|
+
In one studied fitness product, a chart, a workout photo and a short progress note each get space suited to their content. Its phone layout uses a bottom bar. For comparable records, consistent crops, labels or aligned rows help the eye find the differences. Reserve the [equal-card tell](generic-tells.md) for the repeated icon-and-blurb treatment that hides those differences.
|
|
133
133
|
|
|
134
134
|
## 7. Stacked bands
|
|
135
135
|
|
|
@@ -185,4 +185,4 @@ The list is the design; no cards. Fits: menus, services, schedules, specificatio
|
|
|
185
185
|
|
|
186
186
|
## Combining
|
|
187
187
|
|
|
188
|
-
|
|
188
|
+
An opening can grow directly from the subject, including a collection, map or working interface. Describe the relationship in the decision sheet. Carry a recognizable alignment, material or type treatment into the next section and change the density when the visitor’s job changes.
|
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
# Patterns
|
|
2
|
+
|
|
3
|
+
Each pattern here was seen working on one or more of eight production sites studied on 2026-11-21, at 1440 × 900 and 390 × 844, with sizes read from the live pages. They are grouped by the decision you are making. Pick by the visitor's job, not by taste, and build the whole pattern: a pattern with one part missing is usually the brochure again.
|
|
4
|
+
|
|
5
|
+
A pattern is not a look. The same pattern was seen on a white page, a cream page and a dark one. Choose the look in [the method's Step 3](../SKILL.md#step-3-choose-the-look-from-the-subject).
|
|
6
|
+
|
|
7
|
+
## First screen
|
|
8
|
+
|
|
9
|
+
Choose one opening. It decides what the page is.
|
|
10
|
+
|
|
11
|
+
Choose the first screen by the evidence the visitor needs. A finder can open on real choices and editable criteria; a schedule can open on dates and availability. The dealership comparison favored a photograph with the finder over it and actual vehicles directly below. Use that composition when seeing the scene helps someone choose.
|
|
12
|
+
|
|
13
|
+
- **Hero photograph with the task on it.** Use when a scene helps someone picture the place, understand the work, or desire the item. Build one photograph the full width of the screen and 70 to 90 percent of its height, behind the header or directly under it. It strikes when it has one subject, real light (dusk, a window, a lit counter), room for the text on one side, and fills the full width with no frame. Set on it a short headline in the chosen type voice, one sentence, and the task itself: the search bar, the booking bar or the one main button, on a solid panel so it reads. Place any time, cost or eligibility detail that changes the decision beside the task. Start the real items directly below the photograph, so the first row shows at the bottom edge or after one scroll. On a phone the photograph is shorter (45 to 60 percent of the screen) and the task panel sits below it at full width.
|
|
14
|
+
- **Search on the hero.** Use with the hero when the visitor came to find one option among many. Build the search as one panel on the photograph: two to four labelled parts with a gray prompt inside each ("Add dates"), one button in the action color, and a live count on the button ("Show 19 cars"). Real results start directly below the photograph.
|
|
15
|
+
- **Items under the hero.** Use with the hero when browsing is the job and the things have pictures. Build two full rows of real items directly under the photograph, each row named for a place, a time or a category taken from the data ("Newest on the lot", "Under $20,000"), each item with its own photograph.
|
|
16
|
+
- **Choices in view.** Use when the visitor chooses by comparing attributes or times. Build the finder or schedule beside real options with aligned facts, visible criteria and a path to inspect or select one.
|
|
17
|
+
- **Returning task first.** Use when many visitors already have an account or a booking. Build a compact band directly under the navigation that holds the returning task itself, with its fields visible (sign in, find my booking, track an order), and put the offer for new visitors below it.
|
|
18
|
+
- **One photograph, one panel.** Use when the offer is a single next step. Build one photograph the full width of the screen and about half its height, with one plain panel on it holding a headline, one sentence and one button. Nothing else competes.
|
|
19
|
+
- **Product as the picture.** Use when the visitor is judging software or a tool. Build a short centered headline, one sentence and two buttons, then the real product at readable size. Let it start inside the first screen and run off the bottom edge so the page invites the scroll.
|
|
20
|
+
- **Working surface.** Use when the site is the product. Build the working screen as the landing page, with real content a logged-out visitor can use, and keep the offer to sign up in one bar pinned to the bottom edge.
|
|
21
|
+
- **Person doing the task.** Use when a service asks for trust. Build the headline and buttons on one side and, on the other, a photograph of a person doing the thing the service helps with, run to the edge of the screen and faded into the canvas. Lay two or three pieces of the real product over it, such as a question, an answer and a follow-up.
|
|
22
|
+
- **People and the next date.** Use when the visitor is deciding whether to join or attend. Build a large headline that speaks to them, a photograph of real members that runs to the edge, and the next real event as its own card inside the first screen with its date, time and one button.
|
|
23
|
+
- **Campaign photograph.** Use when the visitor came to see a collection and its style. Build one photograph of people with the product, edge to edge and most of the screen tall, with the offer set on it in display type and the buttons on it too.
|
|
24
|
+
- **Result before sign-up.** Use when the product returns a result, such as a score, a quote or a plan. Build a sample result beside the headline: the number, three counted categories and one line explaining a finding, labelled as an example.
|
|
25
|
+
|
|
26
|
+
## Navigation and header
|
|
27
|
+
|
|
28
|
+
- **Plain-word navigation.** Use on every site. Build three to nine category or task names in one row, with no icons, and put sign-in or the main action at the right end. Measured: 13 to 16 px text.
|
|
29
|
+
- **Header that stays.** Use when the page is longer than three screens. Build the header pinned to the top, 64 to 96 px tall on a desktop, with the main action always in it.
|
|
30
|
+
- **Search that shrinks.** Use with "Search on the hero". Build the large search bar so that on scroll it becomes a compact pill in the pinned header that restates the current search.
|
|
31
|
+
- **Action that wakes up.** Use when the hero already holds the main button. Build the header's copy of that button quiet at the top of the page and filled once the hero has scrolled away.
|
|
32
|
+
- **Context row.** Use when place or time changes what the visitor can get. Build one thin row above the header with what is true now: open or closed, the nearest location, the next slot, a phone number.
|
|
33
|
+
- **Trust line on top.** Use when the visitor is handing over money or personal data. Build one small line above the logo stating the protection that applies, such as the insurance, the license or the guarantee.
|
|
34
|
+
- **Rotating notice bar.** Use when there are two or three current offers. Build one bar above the header that rotates them, with previous, next and pause buttons.
|
|
35
|
+
- **Topic switch.** Use when one long page serves several kinds of visitor. Build a row of two to four topics that swaps the content below and then stays pinned. On a phone it becomes a pinned dropdown.
|
|
36
|
+
- **Leaving-the-site mark.** Use for any link that opens another site. Build a small diagonal arrow beside its label, in navigation and on buttons alike.
|
|
37
|
+
- **Text menu.** Use when a category has more than six children. Build the menu that opens under it as two or three columns of plain links with small gray column headings and generous space, no pictures.
|
|
38
|
+
- **Skip link.** Use on every site. Build "Skip to main content" as the first tab stop, hidden until focused. Seven of the eight studied sites have one.
|
|
39
|
+
|
|
40
|
+
## Records and cards
|
|
41
|
+
|
|
42
|
+
- **The picture is the card.** Use when items have photographs. Build each item as a photograph with text under it and nothing around it: no border, no box, no shadow. Measured: 180 px wide with a 12 px gap, seven across at 1440, pictures close to square.
|
|
43
|
+
- **Three facts under the picture.** Use for anything a visitor compares. Build the same lines in the same order on every item: what and where, the price as a total, and the rating or status. Example: "Cabin in Broken Bow · $635 for 2 nights · ★ 5.0".
|
|
44
|
+
- **Badge and save, fixed corners.** Use when items can be saved or carry a status. Build the status as a small pill at the top left of the picture and the save heart at the top right, in the same places on every card.
|
|
45
|
+
- **Shape tells the type.** Use when two kinds of thing share a shelf. Build one kind square and the other round, so a visitor can tell them apart before reading.
|
|
46
|
+
- **Portrait product photograph.** Use for clothing and anything worn or held. Build every product picture portrait, about 4 to 5, square-cornered, with the same framing and background.
|
|
47
|
+
- **Price first on a tile.** Use for a deal. Build the price large on the photograph, then the product name as an underlined link, then the old price: "$15 COZY TEES Was $29.95".
|
|
48
|
+
- **Old and new price together.** Use when something is reduced. Build the old price struck through directly beside the new one, with the reason or the deal name on the next line in the sale color.
|
|
49
|
+
- **Quiet demand strip.** Use when real sales or booking counts exist. Build a thin strip across the bottom of the picture with the count ("335 sold"). Never invent the number.
|
|
50
|
+
- **Product with checkmarked facts.** Use when products differ by terms, not looks. Build each as: its picture, a tag saying who it is for, the name, three or four checkmarked facts, then the actions. Every product identical in structure.
|
|
51
|
+
- **Two actions, ranked.** Use when an item has a safe step and a committing step. Build both as buttons, stacked, the safe one filled and on top, the committing one outlined below.
|
|
52
|
+
- **Highlight one line.** Use when one fact on one item is time-limited. Build a pale highlight behind that single line and a small tag naming it.
|
|
53
|
+
- **Compare box.** Use when items number more than about eight and differ by terms. Build a compare checkbox on every item and keep the filter button and the count pinned while scrolling.
|
|
54
|
+
- **Directory of faces.** Use when people are the proof. Build a grid of small portraits with names, four across, sixteen or more, linking to the full list.
|
|
55
|
+
- **Program in three facts.** Use to sum up a course, plan or service. Build three small capital labels with a value under each: duration, format, commitment.
|
|
56
|
+
- **Editorial tile in the grid.** Use on a long product grid. Build one tile with a photograph and a link to a related collection, placed in the grid in place of a product.
|
|
57
|
+
- **Colored category tiles.** Use when there are many categories and no photographs for them. Build a grid, four across, each tile one flat saturated color with the name at the top left and a small tilted picture at the bottom right.
|
|
58
|
+
- **Shelf with "show all".** Use when the page has several kinds of content. Build each as a row with a heading on the left, "Show all" on the right, and its own previous and next buttons.
|
|
59
|
+
|
|
60
|
+
## Results and filters
|
|
61
|
+
|
|
62
|
+
- **List and map together.** Use when place decides the choice. Build the list on one side and a map on the other that stays put while the list scrolls. Put the price on each map pin.
|
|
63
|
+
- **Search restated.** Use on every results page. Build the header to show what was searched, with a Filters button beside it and a heading giving the count ("Over 1,000 homes in Austin").
|
|
64
|
+
- **Count in the heading.** Use on every category page. Build the heading with the number of items in brackets after it, under a breadcrumb.
|
|
65
|
+
- **Fastest option first.** Use when same-day pickup or availability exists. Build it as a switch at the very top of the filters.
|
|
66
|
+
- **Collapsed filter groups.** Use when there are more than four filters. Build each as a closed group with a plus sign, in one column, with sub-category links above them.
|
|
67
|
+
- **Bigger pictures on results.** Use when a results page shows fewer items than the home page. Build the cards larger, with a dot row showing more photographs and three gray lines of facts.
|
|
68
|
+
|
|
69
|
+
## Trust and reassurance
|
|
70
|
+
|
|
71
|
+
- **Fear removed before the button.** Use on any action that feels risky. Build the sentence above the button so it names the fear and removes it: "See if you'll be approved before accepting."
|
|
72
|
+
- **Reassurance beside the action.** Use beside a consequential action when the visitor has a specific reason to hesitate. Build one short line or three small items stating what it costs and what it will not do: "No credit card required", "No impact to your credit score", "Cancel anytime".
|
|
73
|
+
- **Practical line under the button.** Use on an upload, a booking or a form. Build one small gray line answering the practical questions: what is free, how long it takes, which files or details are needed.
|
|
74
|
+
- **Numbers instead of adjectives.** Use wherever the page would otherwise praise itself. Build three numbers with labels from the real data: members, events a year, price to attend.
|
|
75
|
+
- **Named testimonial.** Use only with a real person's words. Build the quotation with the name, the role and the specific program or product they used.
|
|
76
|
+
- **Example labelled as an example.** Use whenever sample data is shown. Build a small capital label on it: "Illustrative example". Never present invented results as real.
|
|
77
|
+
- **Limits stated.** Use when the product is new or partial. Build one plain sentence in the first screen saying so.
|
|
78
|
+
- **Footnotes that connect.** Use for regulated or conditional claims. Build a numbered mark on the claim, linked to the note, with all notes collected at the foot of the page.
|
|
79
|
+
- **Privacy as a real choice.** Use for analytics or tracking consent. Build the notice with analytics off until allowed and with Decline and Allow as buttons of equal size.
|
|
80
|
+
|
|
81
|
+
## Plans and prices
|
|
82
|
+
|
|
83
|
+
- **Period switch with the saving.** Use when billing has two periods. Build a two-part switch above the plans with the saving stated beside it.
|
|
84
|
+
- **One plan made dominant.** Use when one plan suits most buyers. Build it filled with the dark or brand color, with the only filled button and a small tag. Keep the others pale.
|
|
85
|
+
- **Plan as five lines.** Use for every plan. Build the name, the price with its unit, one line saying who it is for, a full-width button, then a checklist that begins "Everything in [the plan before], and:".
|
|
86
|
+
- **Plans grouped by purpose.** Use for four or more plans. Build two panels, each with its own headline, and put two plans in each.
|
|
87
|
+
- **Risk row.** Use directly under a pricing heading. Build three short items that remove risk: what is free, how to cancel, what the buyer keeps.
|
|
88
|
+
|
|
89
|
+
## Words
|
|
90
|
+
|
|
91
|
+
- **Headline about the visitor.** Use for a service or a community. Build the headline as their situation or a question to them, with the product's name nowhere in it: "What are you building?"
|
|
92
|
+
- **Steps as an eyebrow.** Use when the product is a short process. Build a small capital line above the headline that lists the steps in order.
|
|
93
|
+
- **Facts as headings.** Use for section headings. Build each from a fact in the organization's own voice: "Pizza at six. Talks at 6:45."
|
|
94
|
+
- **Buttons that name the place.** Use on every button. Build the label from where it goes or what it does: "Shop Women", "Find a meetup", "Check my eligibility". Never "Learn more" or "Get started" alone.
|
|
95
|
+
- **Two buttons, two jobs.** Use when the hero has a second action. Build the main one filled with an arrow and the second outlined with an icon that shows what it is, such as a play mark for a demonstration.
|
|
96
|
+
- **Empty state with a way forward.** Use for any list that can be empty. Build one sentence of help and one button inside the empty space: "Create your first playlist. It's easy, we'll help you."
|
|
97
|
+
|
|
98
|
+
## Phone
|
|
99
|
+
|
|
100
|
+
- **Bottom bar.** Use when the site has three to five destinations a visitor moves between. Build a fixed bar at the bottom with an icon and a label for each, the active one in the action color.
|
|
101
|
+
- **Action in the header.** Use when one action matters most. Build it as a small filled button in the phone header beside the menu, on every page.
|
|
102
|
+
- **One-pill search.** Use with "Search on the hero". Build the search as one full-width pill, 56 px tall, that opens the full search.
|
|
103
|
+
- **Chips for categories.** Use when a desktop tab row will not fit. Build the categories as a row of chips that scrolls sideways.
|
|
104
|
+
- **Row with the next item cut off.** Use for any shelf. Build it to scroll sideways with a little over two items showing, so the cut edge says there is more.
|
|
105
|
+
- **Pinned filter pills.** Use on a product grid. Build two pills, one for category and one for filter and sort, that stay pinned under the header, with the grid two across.
|
|
106
|
+
- **Picture first.** Use with the hero photograph, "One photograph, one panel" and "People and the next date". Build the photograph at the top and the headline, sentence and button below it at full width.
|
|
107
|
+
- **Shorter headline.** Use when the desktop headline wraps past three lines at 390 px. Build a shorter one for the phone and keep the same button.
|
|
108
|
+
- **Notice as a sheet.** Use for an announcement or an offer. Build it as a centered dialog on a desktop and as a sheet rising from the bottom on a phone, with one plain way to close it.
|
|
@@ -1,38 +1,134 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Site models
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Eight production sites that the project's owner holds up as the bar were studied on 2026-11-21. Each stands here for a site model: a way of organizing a site around what its visitor came to do. They are described by that job, not by name. Choose the model by the visitor's job, take its anatomy, and fill it with the project's own inventory, pictures and look.
|
|
4
4
|
|
|
5
|
-
##
|
|
5
|
+
## What was measured
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Public home pages, signed out, with the [probe](../scripts/first-screen.mjs) in a desktop browser at 1440 × 900 and a phone browser at 390 × 844. Actions are the links, buttons and form controls visible in the first screen. Pages linked are the other pages on the same site that the home page links to. Pictures are images, video and drawn graphics at least 80 px on each side, and the last column is how much of the first screen the largest one covers.
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
| Model | Actions, desktop | Actions, phone | Pages linked | Height in screens | Pictures, desktop | Largest picture | Pictures, phone | Canvas |
|
|
10
|
+
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
|
|
11
|
+
| Finder | 43 | 28 | 212 | 4.9 | 22 | 2% | 9 | white |
|
|
12
|
+
| Store | 25 | 14 | 58 | 6.9 | 8 | 42% | 4 | white |
|
|
13
|
+
| Campaign | 29 | 19 | 138 | 5.9 | 4 | 84% | 4 | white |
|
|
14
|
+
| Front door | 23 | 9 | 111 | 4.9 | 4 | 53% | 2 | white |
|
|
15
|
+
| Product showcase | 14 | 12 | 60 | 5.2 | 6 | 44% | 1 | white |
|
|
16
|
+
| Working surface | 88 | 16 | 291 | 1 (app shell) | 19 | 21% | 6 | near-black |
|
|
17
|
+
| Proof-led service | 15 | 7 | 20 | 8 | 1 | 86% | 0 | warm cream |
|
|
18
|
+
| Gathering | 19 | 7 | 7 | 6 | 1 | 29% | 1 | dark navy |
|
|
19
|
+
| Bike shop, generated without the method | 7 | 4 | 0 | 2.3 | 1 | 27% | 1 | cream |
|
|
20
|
+
| Barbershop, generated without the method | 9 | 7 | 0 | 8.3 | 3 | 26% | 3 | cream |
|
|
21
|
+
| Barbershop, earlier method that counted actions only | 36 | 26 | 5 | 3.6 | 1 | 9% | 0 | white |
|
|
10
22
|
|
|
11
|
-
|
|
23
|
+
The generated pages show the two ways to miss. The pages built without the method each had a large photograph and little to do: one page, nothing linked, under twelve things to act on. The page built with an earlier version of this method had six working pages and a booking a visitor could finish, and one small photograph. The owner judged it worse than the page built without the method. Substance without something to look at fails the bar, and so does a good-looking page with nothing to do.
|
|
12
24
|
|
|
13
|
-
|
|
25
|
+
The [floor](../SKILL.md#step-4-build-the-first-screen-and-the-journey-then-measure) sits just under the lowest studied site on each count that separated the groups: things to act on, pages linked, height, and pictures. Every studied desktop first screen held four or more pictures or one covering over a quarter of it. One studied phone page opens on text and a button with no picture, so the phone count is reported without a verdict.
|
|
14
26
|
|
|
15
|
-
|
|
27
|
+
A second visit the same day gave different counts on sites that load content as the visitor scrolls or that test variants: 50 actions and 2.6 screens on the finder, 35 actions and 2.3 screens on the store, 18 actions under a different headline on the product showcase. On both visits every site had at least 14 actions on a desktop, 7 on a phone, 7 pages linked, and pictures at or above the floor. Page height did not hold steady, so a first screen with twice the floor of actions is not judged on height.
|
|
16
28
|
|
|
17
|
-
|
|
29
|
+
Limits: two visits per site on one day, signed out, United States content. The store was read through a verification screen, so its anatomy below is the least certain. Record counts depend on how a page is built. Read the numbers as the gap between these sites and a generated page, not as targets to reach.
|
|
18
30
|
|
|
19
|
-
|
|
31
|
+
## Finder
|
|
20
32
|
|
|
21
|
-
|
|
33
|
+
The visitor came to find one option among many.
|
|
22
34
|
|
|
23
|
-
|
|
35
|
+
- **First screen:** no slogan. A header with five category tabs, each with a small illustrated icon. One pill-shaped search bar split into where, when and who, with a round button in the brand color. Then two full rows of real items.
|
|
36
|
+
- **One item:** a near-square photograph with 20 px corners, a status pill at the top left, a heart at the top right, a 13 px title, and one gray 12 px line with the total price and the rating. No box around it. Seven across at 1440.
|
|
37
|
+
- **Down the page:** more rows, each named for a place and often a time from the visitor's own area, each with an arrow to the full set.
|
|
38
|
+
- **Results page:** the list beside a map that stays put, price pills as map pins, the search restated in the header with a Filters button, and the count as the heading.
|
|
39
|
+
- **Phone:** one full-width search pill, categories as chips, rows that scroll sideways with the next item cut off, and a bottom bar.
|
|
40
|
+
- **Look seen with it:** white canvas, quiet type voice, soft corners, color from the photographs.
|
|
24
41
|
|
|
25
|
-
|
|
42
|
+
Use it when the site's worth is the number and quality of its options: stays, homes, cars, classes, tradespeople, restaurants, jobs.
|
|
26
43
|
|
|
27
|
-
|
|
44
|
+
## Store
|
|
28
45
|
|
|
29
|
-
|
|
46
|
+
The visitor came to buy from a catalog, here or today.
|
|
30
47
|
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
| Atlassian | Short headline, one blue, real product screenshot | One geometric sans, one weight | Logo strip; product at readable size |
|
|
36
|
-
| AHS | Input beside the primary action inside a card | Serif display in brand colors | Plan limits in dollars; awards; technician photo |
|
|
48
|
+
- **First screen:** a pinned header 80 px tall with categories, deals, pickup and delivery, a wide search field that asks a question, and the account. The delivery postal code and the nearest store are in the header. Then this week's offer and a grid of category pictures, six across.
|
|
49
|
+
- **One item:** a square picture with the name under it.
|
|
50
|
+
- **Buttons:** full pills, 40 to 44 px tall, in the one brand color.
|
|
51
|
+
- **Look seen with it:** white canvas, quiet type voice with 29 px section headings, pill corners, one saturated brand color.
|
|
37
52
|
|
|
38
|
-
|
|
53
|
+
Use it when visitors already know roughly what they want and the questions are where, when and how much: grocery, hardware, pharmacy, a café menu, a parts counter.
|
|
54
|
+
|
|
55
|
+
## Campaign
|
|
56
|
+
|
|
57
|
+
The visitor came to see a collection and choose a style.
|
|
58
|
+
|
|
59
|
+
- **First screen:** a bar of rotating offers, tabs for sister brands, a centered wordmark with search to the right, and nine plain category words in one row. Then one photograph of people in the product, edge to edge, with the offer set on it in display type and pill buttons on it that name where they go.
|
|
60
|
+
- **Down the page:** tiles two and four across, each a photograph with the price large, the product name underlined and the old price. A band of repeated words separates sections.
|
|
61
|
+
- **Category page:** the heading with the count, a same-day pickup switch as the first filter, collapsed filter groups, and a grid three across.
|
|
62
|
+
- **One product:** a portrait photograph, a saving tag on one corner and a heart on the other, a small status line, the name, the old price struck through beside the new one, and the deal name in the sale color.
|
|
63
|
+
- **Phone:** a row of six header icons, the grid two across, and category and filter pills that stay pinned.
|
|
64
|
+
- **Look seen with it:** white shop with a seasonal campaign palette, display type on photographs, square pictures with pill buttons.
|
|
65
|
+
|
|
66
|
+
Use it when the product is chosen by how it looks on someone: clothing, furniture, beauty, a portfolio, a venue.
|
|
67
|
+
|
|
68
|
+
## Front door
|
|
69
|
+
|
|
70
|
+
The visitor came either to resume a task or to explore an offer.
|
|
71
|
+
|
|
72
|
+
- **First screen:** a one-line trust statement above the logo. Six plain product names, three icon utilities and sign-in. A band directly below with the sign-in fields visible. Then one full-width landscape photograph with a white panel on it: a light 40 px headline, one sentence that removes the main fear, and one button.
|
|
73
|
+
- **Down the page:** a row of topics that switches the content and stays pinned. Three starting points, each a small flat illustration, a heading, one sentence and one link. Alternating picture and text panels on pale gray. The mobile app shown as a real screen.
|
|
74
|
+
- **Product list page:** every product built identically with its picture, a who-it-is-for tag, checkmarked facts and two ranked buttons, with a compare box, pinned filters and a count.
|
|
75
|
+
- **Phone:** the picture first, then the panel below it at full width; sign-in becomes one header button.
|
|
76
|
+
- **Look seen with it:** white canvas, light type voice, nearly square corners, one brand color for every link and button.
|
|
77
|
+
|
|
78
|
+
Use it when returning customers and new ones arrive at the same address: a bank, an insurer, a clinic, a utility, a school, any business with accounts or bookings.
|
|
79
|
+
|
|
80
|
+
## Product showcase
|
|
81
|
+
|
|
82
|
+
The visitor came to judge whether software fits.
|
|
83
|
+
|
|
84
|
+
- **First screen:** navigation on the left, the mark centered, account and one pill button on the right. One centered headline at 80 px, one sentence, two pill buttons the same size. Then the real product in a large frame, moving, starting inside the first screen and running off the bottom.
|
|
85
|
+
- **Down the page:** each section is one large heading, one live picture of the product, then three short columns of a bold line and a gray sentence with no boxes. Connected tools shown by name with a count. Customers as a row of tiles. The page closes on the headline size and buttons it opened with.
|
|
86
|
+
- **Pricing page:** customer marks under the headline, a period switch with the saving, plans grouped into two panels, each plan as five lines, one plan dominant.
|
|
87
|
+
- **Phone:** the headline at 40 px, the two buttons side by side, and the main button always in the header.
|
|
88
|
+
- **Look seen with it:** white canvas, large grotesque voice, pill buttons, no brand color: color comes from artwork behind the product.
|
|
89
|
+
|
|
90
|
+
Use it when the product is a screen: software, an app, a dashboard, a developer tool.
|
|
91
|
+
|
|
92
|
+
## Working surface
|
|
93
|
+
|
|
94
|
+
The visitor came to use the product, signed in or not.
|
|
95
|
+
|
|
96
|
+
- **First screen:** the product itself. A top bar with home, a search field that asks a question, and sign-in as a filled pill. Rounded panels on a darker page: a library with helpful empty states, then shelves of content with a heading and "Show all".
|
|
97
|
+
- **One item:** a square cover with a title and one gray line. People are circles.
|
|
98
|
+
- **Offer:** one bar pinned to the bottom edge in a gradient used nowhere else, with one button.
|
|
99
|
+
- **Browse page:** a grid of flat colored category tiles, four across.
|
|
100
|
+
- **Phone:** the mark and one pill in the top bar, a bottom bar with four destinations, shelves that scroll sideways.
|
|
101
|
+
- **Look seen with it:** near-black canvas, quiet type voice in two weights, pill buttons, color from the content.
|
|
102
|
+
|
|
103
|
+
Use it when the site is the tool: a player, an editor, a tracker, a booking desk, a catalog people work in daily.
|
|
104
|
+
|
|
105
|
+
## Proof-led service
|
|
106
|
+
|
|
107
|
+
The visitor came to decide whether a service can deliver.
|
|
108
|
+
|
|
109
|
+
- **First screen:** navigation in its own floating pill, with a separate filled button. An eyebrow listing the steps of the service. A serif headline about the visitor's situation with one handwritten phrase. Three plain sentences. A filled 56 px button and an outlined one. Three reassurances with icons. On the right, a photograph of a person doing the task, run to the edge and faded into the canvas, with pieces of the real product laid over it.
|
|
110
|
+
- **Down the page:** the real product in a frame on a dark band. Examples labelled as examples. Four numbered steps. Plans with one made dominant and a row that removes risk.
|
|
111
|
+
- **Tool page:** a sample result beside the headline, and one practical line under the button.
|
|
112
|
+
- **Phone:** a shorter headline, a full-width button, the steps as a two-by-two grid.
|
|
113
|
+
- **Look seen with it:** warm cream canvas, editorial serif voice, a deep color with a warm accent, small radii.
|
|
114
|
+
|
|
115
|
+
Use it when a person is hiring judgment or skill: a consultancy, a clinic, a tutor, a repair or building trade, a salon, a studio.
|
|
116
|
+
|
|
117
|
+
## Gathering
|
|
118
|
+
|
|
119
|
+
The visitor came to decide whether to join something that has a next date.
|
|
120
|
+
|
|
121
|
+
- **First screen:** a pinned, slightly see-through header with the join button always visible. An eyebrow naming the place. A very large headline that asks the visitor a question, with one word on a block of the brand color. A specific paragraph: who comes, how often, what it costs. Two buttons. One line of proof with a number. A photograph of real members run to the edge, and the next event as its own card with date, time and one button.
|
|
122
|
+
- **Down the page:** four ways to take part as four verbs. Three numbers with labels. A named testimonial. Sections that each pair a small handwritten label with a large factual heading. Photographs with an offset block shadow and handwritten captions. A directory of faces.
|
|
123
|
+
- **Phone:** the photograph first, then the headline at 52 px, with the two buttons side by side.
|
|
124
|
+
- **Look seen with it:** dark canvas, heavy type voice with handwritten labels, soft corners, one bright brand color used in fields.
|
|
125
|
+
|
|
126
|
+
Use it when the offer is people and a date: a meetup, a club, a class series, a congregation, a league, a venue with a calendar.
|
|
127
|
+
|
|
128
|
+
## The opening, whatever the model
|
|
129
|
+
|
|
130
|
+
The anatomy above describes observed pages. Borrow the part that answers this visitor’s question. The dealership owner preferred the car photograph with search on it and real vehicles immediately below. A stay finder can lead with editable criteria and comparable options, and a working application with the records themselves. See the [field guide](field-guide.md) for the associated behavior, access needs and phone decisions.
|
|
131
|
+
|
|
132
|
+
## Combining two
|
|
133
|
+
|
|
134
|
+
Where two kinds of visitor start in different places, put one model's opening above the other's. A front door's returning-task band sits well above a finder's search or a store's offer. A gathering's next-event card sits well inside a proof-led service's first screen. Take the item anatomy from the model that owns the records.
|