| 1 | # Vertical 3:4 Layout Catalog |
| 2 | |
| 3 | This catalog describes 1200x1600 vertical poster-card structures. It is structural only: style controls color, type mood, decoration, shadows, and texture. |
| 4 | |
| 5 | ## Zone Skeletons |
| 6 | |
| 7 | ### `poster-anchor` |
| 8 | |
| 9 | - **Use for**: poster claims, hero metrics, and concept cards. |
| 10 | - **Zone sketch**: strong top/upper anchor, main proof/value zone, bottom synthesis/source. |
| 11 | - **Balance rule**: the anchor must dominate without crowding the proof zone. |
| 12 | - **Failure sign**: many equal cards replace the poster anchor. |
| 13 | |
| 14 | ### `section-stack` |
| 15 | |
| 16 | - **Use for**: checklists, process pages, evidence groups. |
| 17 | - **Zone sketch**: title/claim, 2-4 grouped vertical sections, short bottom memory point. |
| 18 | - **Balance rule**: sections should be grouped by meaning and sized by importance. |
| 19 | - **Failure sign**: sections are only a long list of cards. |
| 20 | |
| 21 | ### `wide-pocket` |
| 22 | |
| 23 | - **Use for**: short parallel comparisons or evidence pairs inside one section. |
| 24 | - **Zone sketch**: full-width context, compact two-column pocket, full-width synthesis. |
| 25 | - **Balance rule**: the two-column pocket is a local device, not the whole layout. |
| 26 | - **Failure sign**: both columns become paragraph-heavy. |
| 27 | |
| 28 | ## Patterns |
| 29 | |
| 30 | ### `poster-hero-proof` |
| 31 | |
| 32 | - **Input shape**: one strong claim with 2-4 proof points. |
| 33 | - **Structure recipe**: large claim, main proof zone, compact evidence band or bottom conclusion. |
| 34 | - **Budget rule**: hero zone is visibly larger than support. |
| 35 | - **Failure signs**: viewer cannot identify the anchor; proof points become equal heroes. |
| 36 | |
| 37 | ### `hero-metric-explainer` |
| 38 | |
| 39 | - **Input shape**: one key number or result plus context. |
| 40 | - **Structure recipe**: hero metric, short interpretation, 1-3 support rows/chips. |
| 41 | - **Budget rule**: metric owns a large vertical zone; support stays compact. |
| 42 | - **Failure signs**: multiple numbers compete; interpretation is detached from the metric. |
| 43 | |
| 44 | ### `vertical-process` |
| 45 | |
| 46 | - **Input shape**: 3-6 steps, phases, or layers. |
| 47 | - **Structure recipe**: vertical timeline, staircase, or stacked bands. |
| 48 | - **Budget rule**: distribute steps through the middle/lower canvas. |
| 49 | - **Failure signs**: steps become paragraphs; lower canvas is unused. |
| 50 | |
| 51 | ### `comparison-rows` |
| 52 | |
| 53 | - **Input shape**: two options/states compared across shared dimensions. |
| 54 | - **Structure recipe**: aligned rows with labels, or two stacked zones with matching fields. |
| 55 | - **Budget rule**: field count stays consistent and rows remain short. |
| 56 | - **Failure signs**: unequal field counts; contrast hidden in prose. |
| 57 | |
| 58 | ### `evidence-band-stack` |
| 59 | |
| 60 | - **Input shape**: 3-5 facts supporting one conclusion. |
| 61 | - **Structure recipe**: conclusion block plus grouped evidence bands, chips, or rows. |
| 62 | - **Budget rule**: facts are grouped by meaning, not expanded into full cards by default. |
| 63 | - **Failure signs**: evidence reads as scattered facts; too many equal blocks. |
| 64 | |
| 65 | ### `two-column-pocket` |
| 66 | |
| 67 | - **Input shape**: one section with parallel short items. |
| 68 | - **Structure recipe**: one vertical section contains a compact two-column subgrid; surrounding sections stay full-width. |
| 69 | - **Budget rule**: each item is short and aligned. |
| 70 | - **Failure signs**: the pocket becomes the whole page; text is too narrow. |
| 71 | |
| 72 | ### `data-card` |
| 73 | |
| 74 | - **Input shape**: one chart, rank list, hero metric, or compact table. |
| 75 | - **Structure recipe**: title/claim, main data object, interpretation sentence, optional 1-2 support chips. |
| 76 | - **Budget rule**: data object owns the middle zone and interpretation stays nearby. |
| 77 | - **Failure signs**: data is hard to read; interpretation is missing or too far away. |
| 78 |