# THIS YOU — ISSUE 01 IMAGE PLAN
### v3
## NEW YORK / AUTUMN 2026
### Shared + Personalized Asset Plan for Print and Digital

---


## STEP 5 CURRENT STATUS

### STORY visuals
All six STORY-page visual directions are now selected.

- Page 05 — NYFW → Pexels / Following NYC
- Page 09 — Armory Show → Vincent Tullo / courtesy The Armory Show
- Page 13 — CBGB Fest → official Shore Fire / CBGB Festival press image
- Page 17 — New York After Dark → official NYCWFF / `NYCWFF_2026_PhotoGallery76.jpg`
- Page 21 — NYC Marathon → Tong Su / Unsplash
- Page 25 — NYFF → **two-image editorial composition**
  - Alev Takil / Unsplash — Lincoln Center audience context
  - FLC Press — `NYFF_Opening Night_Announcement_1600x900.png` / *Paper Tiger* Opening Night

### SCENE visuals
Not generated yet.

Decision:

> **First lock / collect all STORY images. Then generate the SCENE set as one coherent visual pass.**

This avoids mixing stock/press selection work with constructed/generative SCENE production.

### External-asset source of truth
Detailed URLs, download instructions, credits and rights notes live in:

`THIS_YOU_ISSUE_01_STORY_IMAGE_REGISTRY_v3.md`


# 1. PURPOSE

This document defines the image system for **THIS YOU / Issue 01 — New York / Autumn 2026**.

It is designed to answer:

- which pages need images,
- what kind of images they need,
- whether they are shared or personalized,
- whether print and digital can use the same source,
- when separate print/web versions are recommended,
- which pages need motion or digital-only extensions,
- what file names and folders should be used.

This is an **asset plan**, not a final layout file.

The magazine pages themselves should still be assembled by the system using:
- HTML/CSS,
- layouts,
- page data,
- image assets,
- print rendering.

Do **not** generate entire final magazine pages as flat images.

---

# 2. IMAGE SYSTEM PRINCIPLES

## 2.1 Asset types

We work with 3 major image classes:

### A. SHARED EDITORIAL IMAGES
Same for every reader:
- concept/demo image,
- scene visuals,
- story supporting images,
- artwork stills,
- city map / visual assets,
- shared sponsor references,
- back cover visuals.

### B. PERSONALIZED IMAGES
Generated separately for each reader:
- cover image,
- 6 arrival hero images,
- sponsored personalized ad hero image,
- optional summary visual.

### C. DIGITAL-ONLY / MOTION ASSETS
Used online only:
- ArtCodingLab animation,
- playlist / motion embeds,
- extra gallery/detail assets,
- hover/zoom / carousel extras.

---

## 2.2 File variants

For important images we keep 3 variants:

### MASTER
Best source version.

### WEB
Optimized for digital issue.

### PRINT
Optimized for print/PDF output.

Recommended naming:

```text
page-06-scene-main-master.jpg
page-06-scene-main-web.webp
page-06-scene-main-print.jpg
```

---

## 2.3 Print vs digital logic

Not every page needs a separate print and digital image.

There are 3 modes:

### SAME SOURCE
One generated source is used for both print and digital, with normal export resizing.

### SAME SOURCE, DIFFERENT CROP
One generated source, but the system creates different web/print crops.

### SEPARATE RENDERS
Two deliberately different renders based on the same concept:
- one for print,
- one for digital.

This should be used only when the layout or reading experience clearly benefits from it.

---

# 3. RECOMMENDED FOLDER STRUCTURE

## Shared assets

```text
issue-001/shared/page-02/
issue-001/shared/page-03/
issue-001/shared/page-04/
...
issue-001/shared/page-32/
```

## Personalized assets

```text
issue-001/personalized/user-XXXX/page-01/
issue-001/personalized/user-XXXX/page-07/
issue-001/personalized/user-XXXX/page-11/
...
issue-001/personalized/user-XXXX/page-30/
```

---

# 4. ISSUE 01 — PAGE-BY-PAGE IMAGE PLAN

## QUICK LEGEND

- **Mode** = shared / hybrid / personalized
- **Need** = yes / optional / no
- **P/W mode** = print/web mode
- **Motion** = no / optional / yes

---

## PAGE TABLE

| Page | Page title / role | Page type | Mode | Image needed | Asset role | Orientation | P/W mode | Motion | Notes |
|---|---|---|---|---|---|---|---|---|---|
| 01 | Cover | cover | personalized | yes | cover-hero | portrait | same source, different crop allowed | no | Reader clearly recognizable; premium editorial portrait |
| 02 | How THIS YOU works / One Moment. Three Readers. | concept | shared | yes | concept-demo-main | portrait or landscape composition adapted to page | separate render recommended | no | 3 readers, same moment, visibly different arrivals |
| 03 | Editor's letter / issue intro | editorial | shared | optional | intro-supporting | portrait or landscape | same source | no | Could also be text-only if layout is strong enough |
| 04 | Contents / city map / six moments | contents | shared | yes | city-map-visual | portrait | same source | no | Graphic / illustrated map or editorial city visual |

| 05 | NYFW story | story | shared | yes | story-visual-anchor | portrait or landscape | same source | no | One supporting image if needed, but text can dominate |
| 06 | NYFW scene | scene | shared | yes | scene-main | portrait | separate render or different crop allowed | no | Still-life / objects page: invitation, coffee, sunglasses, etc. |
| 07 | NYFW arrival | moment/arrival | hybrid | yes | arrival-hero | portrait | same source, different crop allowed | no | Personalized reader in “Between Shows” moment |
| 08 | NYFW style | style | personalized | no new main image required | reuse-arrival-hero | n/a | reuse | no | Use page 07 hero; optional tiny support image only if needed |

| 09 | Armory story | story | shared | yes | story-visual-anchor | portrait or landscape | same source | no | Art-world context page |
| 10 | Armory scene | scene | shared | yes | scene-main | portrait | same source, different crop allowed | no | Objects / residue page: tote, floor plan, notebook, water bottle |
| 11 | Armory arrival | moment/arrival | hybrid | yes | arrival-hero | portrait | same source, different crop allowed | no | Personalized reader at the fair |
| 12 | Armory style | style | personalized | no new main image required | reuse-arrival-hero | n/a | reuse | no | Same logic as other style pages |

| 13 | CBGB story | story | shared | yes | story-visual-anchor | portrait or landscape | same source | no | Music history / event context |
| 14 | CBGB scene | scene | shared | yes | scene-main or scene-typography-main | portrait | separate render recommended | optional | Strong music/typography page; can include track-led design |
| 15 | CBGB arrival | moment/arrival | hybrid | yes | arrival-hero | portrait | same source, different crop allowed | no | Personalized reader under the K Bridge |
| 16 | CBGB style | style | personalized | no new main image required | reuse-arrival-hero | n/a | reuse | no | Use page 15 hero |

| 17 | New York After Dark story | story | shared | yes | story-visual-anchor | portrait or landscape | same source | no | Food/nightlife editorial page |
| 18 | New York After Dark scene | scene | shared | yes | scene-main | portrait | same source, different crop allowed | no | Cinematic rooftop / blue-hour / skyline scene |
| 19 | New York After Dark arrival | moment/arrival | hybrid | yes | arrival-hero | portrait | same source, different crop allowed | no | Personalized dinner-into-night look |
| 20 | New York After Dark style | style | personalized | no new main image required | reuse-arrival-hero | n/a | reuse | no | Use page 19 hero |

| 21 | Marathon story | story | shared | yes | story-visual-anchor | portrait or landscape | same source | no | Marathon / city transformation context |
| 22 | Marathon scene | scene | shared | yes | acl-still-main | portrait | same source for still; digital extension separate | yes | Print gets still; digital opens ArtCodingLab motion visualization |
| 23 | Marathon arrival | moment/arrival | hybrid | yes | arrival-hero | portrait | same source, different crop allowed | no | Personalized runner image |
| 24 | Marathon style | style | personalized | no new main image required | reuse-arrival-hero | n/a | reuse | no | Use page 23 hero |

| 25 | NYFF story | story | shared | yes | story-visual-anchor | portrait or landscape | same source | no | Film / opening-night context |
| 26 | NYFF scene | scene | shared | yes | scene-main | portrait | same source, different crop allowed | no | Elegant cinematic / ticket / program / light page |
| 27 | NYFF arrival | moment/arrival | hybrid | yes | arrival-hero | portrait | same source, different crop allowed | no | Personalized dress-up cinema arrival |
| 28 | NYFF style | style | personalized | no new main image required | reuse-arrival-hero | n/a | reuse | no | Use page 27 hero |

| 29 | Your Autumn / style summary | summary | personalized | optional | summary-supporting | portrait or collage | separate render optional | no | Can be text-led or include mini visual / collage |
| 30 | Sponsored personalized ad | sponsored_ad | hybrid | yes | sponsor-personal-hero | portrait | separate render recommended | no | Shared sponsor shell + personalized reader image |
| 31 | Next issue + credits | credits | shared | optional | teaser-supporting | portrait or landscape | same source | no | Could be mostly text, or include next-city teaser image |
| 32 | Absurd.website back cover | back cover | shared | yes | back-cover-main | portrait | same source | no | Shared publisher back-cover creative |

---

# 5. ASSET COUNTS

## Shared assets — recommended baseline

### Required or near-required
- Page 02 concept/demo image = 1
- Page 04 city map / visual = 1
- 6 scene-main images (pages 06, 10, 14, 18, 22, 26) = 6
- Page 32 back cover image = 1

### STORY visual anchors — required by default
- Story page visual anchors (pages 05, 09, 13, 17, 21, 25) = 6
- Page 03 intro image = 0–1
- Page 31 teaser image = 0–1

### Shared total
**Minimum strong plan:** about **15 shared visuals**  
**Expanded plan:** about **17–22 shared visuals**

---

## Personalized assets — per reader

### Required
- Page 01 cover = 1
- 6 arrivals (pages 07, 11, 15, 19, 23, 27) = 6
- Page 30 sponsor ad = 1

### Optional
- Page 29 style summary visual = 0–1

### Personalized total per reader
**Minimum:** **8 images per reader**  
**Expanded:** **9 images per reader**

---

# 6. PAGE-SPECIFIC IMAGE DIRECTIONS

## PAGE 02 — HOW THIS YOU WORKS

### Asset
`page-02-concept-demo-main`

### Purpose
Immediately explain the magazine through image.

### Visual logic
One shared event. Three clearly different readers. Three different arrivals.

### Recommendation
Generate this as a **special shared demo visual**, not a normal fashion page.

### Print/web
Recommend **separate render or at least separate layout-aware crop**, because the explainer page may have significantly different typography needs in print and digital.

---

## PAGE 04 — CONTENTS / CITY MAP

### Asset
`page-04-city-map-visual`

### Purpose
Give the issue a city-level orientation.

### Visual logic
Could be:
- stylized editorial map,
- map with six moments,
- abstract city route,
- typography-led map visual.

### Print/web
Same source is probably enough.

---

## PAGE 06 — NYFW SCENE

### Asset
`page-06-scene-main`

### Type
Shared editorial scene image.

### Format direction
Objects / still-life / editorial composition.

### Suggested objects
- invitation,
- espresso,
- sunglasses,
- taxi receipt,
- shoes,
- phone,
- street textures.

### Print/web
A large source with different crop flexibility is recommended.

---

## PAGE 10 — ARMORY SCENE

### Asset
`page-10-scene-main`

### Type
Shared editorial scene image.

### Format direction
Objects / “what remains after an afternoon at the fair”.

### Suggested elements
- tote bag,
- folded fair map,
- gallery card,
- notebook,
- glasses,
- water bottle,
- wristband.

### Print/web
Same source likely enough.

---

## PAGE 14 — CBGB SCENE

### Asset
`page-14-scene-main`

### Type
Shared scene image, possibly typography-led.

### Format direction
More graphic and music-oriented than other scenes.

### Suggested elements
- heavy typography,
- concrete texture,
- wristband,
- poster fragments,
- song title,
- dark industrial visual mood.

### Print/web
Separate render may help because digital could support more text/music information.

---

## PAGE 18 — NEW YORK AFTER DARK SCENE

### Asset
`page-18-scene-main`

### Type
Shared cinematic scene image.

### Format direction
Blue hour rooftop / skyline / food-night transition.

### Suggested elements
- skyline,
- plate / glass,
- atmospheric light,
- twilight tone,
- elegant night-city mood.

### Print/web
Same source with crop flexibility.

---

## PAGE 22 — MARATHON SCENE

### Asset
`page-22-acl-still-main`

### Type
Shared scene image + digital motion extension.

### Format direction
ArtCodingLab still derived from:
- route,
- distance,
- borough progression,
- pulse / rhythm / motion.

### Digital extension
Motion version for online edition:
- animation,
- interactive visual,
- route-reactive piece.

### Print/web
Print uses still. Digital opens motion.

---

## PAGE 26 — NYFF SCENE

### Asset
`page-26-scene-main`

### Type
Shared elegant scene image.

### Format direction
Quiet cinematic / opening-night / restrained luxury.

### Suggested elements
- ticket,
- program,
- dusk light,
- coat-check token,
- one glass,
- refined typography.

### Print/web
Same source likely enough.

---

## PAGE 30 — SPONSORED PERSONALIZED AD

### Asset
`page-30-sponsor-personal-hero`

### Type
Hybrid page.

### Shared layer
- sponsor,
- product,
- brand copy,
- logo,
- CTA,
- disclosure.

### Personalized layer
- reader-specific generated hero image.

### Recommendation
Treat this as a **separate image class** from normal arrivals.

Why:
- the sponsor product must remain central,
- the product needs to be recognizable,
- the image is campaign-led, not event-led.

### Print/web
Recommend **separate render or at minimum separate final crop**, because ad typography may differ more sharply between print and digital.

---

## PAGE 32 — ABSURD BACK COVER

### Asset
`page-32-back-cover-main`

### Type
Shared publisher visual.

### Recommendation
Treat as a normal campaign image for Absurd.website or one selected project.

### Print/web
Same source usually enough.

---

# 7. PERSONALIZED IMAGE SYSTEM

## 7.1 Cover

### Asset
`page-01-cover-hero`

### Role
Immediate “this is my magazine” moment.

### Key requirements
- reader recognizable,
- premium editorial framing,
- works with cover typography,
- not overly cropped,
- fashion signal visible.

---

## 7.2 Arrival hero images

Pages:
- 07
- 11
- 15
- 19
- 23
- 27

### Asset naming
```text
page-07-arrival-hero
page-11-arrival-hero
page-15-arrival-hero
page-19-arrival-hero
page-23-arrival-hero
page-27-arrival-hero
```

### Shared rules
All should:
- feel like one issue,
- have the same overall editorial quality,
- vary according to the chapter,
- keep the reader recognizable,
- respond to city / weather / environment / formality.

---

## 7.3 Style pages

Pages:
- 08
- 12
- 16
- 20
- 24
- 28

### Recommendation
Do **not** require a second large hero image for each style page.

Instead:
- reuse the arrival image,
- or use a cropped/detail version,
- or use no large image if layout is clean.

This saves generation load and keeps the rhythm efficient.

---

## 7.4 Page 29 summary visual

### Asset
`page-29-summary-supporting`

### Recommendation
Optional.

Possible formats:
- mini collage,
- 6-look contact sheet,
- one quiet portrait,
- no image at all.

For MVP, this page can be text-led.

---

# 8. STORY PAGE VISUAL ANCHORS — FINAL SELECTIONS

Every STORY page contains at least one visual anchor.

Core role:

> **STORY = read + see**

The STORY visual supports context / reality.  
The following SCENE page remains interpretive / atmospheric.

Preferred visual balance remains approximately:
- 35–45% visual
- 55–65% text

Exact layout can vary.

---

## PAGE 05 — NYFW
### THE SHOW OUTSIDE THE SHOW

**Status:** APPROVED

**Selected image:** Pexels — *Friends Crossing the Street Together*  
**Creator:** Following NYC  
**Source:** Pexels  
**Source page:**  
https://www.pexels.com/photo/friends-crossing-the-street-together-12107683/

**Recommended credit:**  
`Photo: Following NYC / Pexels`

**Production master filename:**  
`page-05-story-nyfw-following-nyc-pexels-master.jpg`

**Visual role:**  
Fashionable people moving through a New York street/crosswalk. Supports the “between shows” idea much better than a runway image.

**Print layout direction:**  
Portrait/vertical source can be used as a strong crop occupying roughly 35–40% of the STORY page.

---

## PAGE 09 — ARMORY SHOW
### LOOKING, AND BEING LOOKED AT

**Status:** APPROVED

**Selected image:** official Armory Show press photograph  
**Photographer:** Vincent Tullo  
**Credit supplied by source:**  
`Photo Credit: Vincent Tullo courtesy The Armory Show`

**Source page:**  
https://www.thearmoryshow.com/press-room/2024-press-images

**Selected direct image:**  
https://thearmoryshow.com/media/pages/press-room/2023-press-images/ccafd27085-1683133301/tullo_armoryshow2022_day1_1049.jpg

**Recommended magazine credit:**  
`Photo: Vincent Tullo, courtesy The Armory Show`

**Production master filename:**  
`page-09-story-armory-vincent-tullo-master.jpg`

**Visual role:**  
Authentic fair scale + visitors + looking behavior. Keeps the STORY documentary rather than turning it into a generic gallery page.

**Rights note:**  
Archive the official press-page usage context together with the master file.

---

## PAGE 13 — CBGB FEST
### THE ROOM IS GONE. THE NOISE ISN'T.

**Status:** APPROVED

**Selected image:** official CBGB Festival black-and-white crowd / crowd-surfing press image  
**Source:** Shore Fire Media / CBGB Festival press page

**Source page:**  
https://shorefire.com/roster/cbgb-festival

**Working direct image URL:**  
https://shorefire.com/images/uploads/gallery/Screenshot_2025-09-28_at_4.46.04%E2%80%AFPM.png

**Usage note from source:**  
`All rights reserved. Photos are for editorial use only.`

**Working credit:**  
`Photo: Jessica Licata / CBGB Festival`

**Production master filename:**  
`page-13-story-cbgb-crowd-master.png`

**Visual role:**  
Real punk crowd energy, physicality and noise. Strong documentary counterpoint to the constructed SCENE page.

**Final check before print:**  
Confirm downloaded B&W crowd-surfing asset matches the `CBGB Festival crowd` credit entry. Do not print the photographer credit until that final asset-to-credit match is confirmed.

---

## PAGE 17 — NEW YORK AFTER DARK
### WHEN DOES DINNER BECOME NIGHT?

**Status:** APPROVED

**Selected image:** `NYCWFF_2026_PhotoGallery76.jpg`  
**Source:** official Food Network New York City Wine & Food Festival gallery / press assets

**Official gallery:**  
https://nycwff.org/about-us/festival-videos-photos/

**Selected Dropbox preview/source:**  
https://www.dropbox.com/scl/fo/7jkfs021r2xk9z1d0j0ge/APr5Vjw7elDG4Ac2mnLkvDE?dl=0&e=1&preview=NYCWFF_2026_PhotoGallery76.jpg&rlkey=ldiv5aunm856qrsm5isc02ps4&st=fk04ueti

**Recommended credit:**  
`Photo courtesy of Food Network New York City Wine & Food Festival`

**Production master filename:**  
`page-17-story-nycwff-photogallery76-master.jpg`

**Visual role:**  
Nighttime crowd + event lights + New York city context + food-festival environment. Strongest match for the dinner→night transition.

---

## PAGE 21 — NYC MARATHON
### ONE LINE THROUGH THE CITY

**Status:** APPROVED

**Selected image:** Tong Su / Unsplash — *A group of people running*

**Source page:**  
https://unsplash.com/photos/a-group-of-people-running-Z-GDQeDaSB4

**Source context:**  
New York City marathon runners near Central Park, 2022.

**Recommended credit:**  
`Photo: Tong Su / Unsplash`

**Production master filename:**  
`page-21-story-marathon-tong-su-unsplash-master.jpg`

**Visual role:**  
Authentic New York marathon scale and movement. Avoids generic performance-fashion imagery.

**Caption accuracy:**  
Do not imply the image is from the 2026 race.

---

## PAGE 25 — NYFF
### AN EXCUSE TO DRESS A LITTLE MORE

**Status:** APPROVED — TWO VISUAL ANCHORS

This STORY intentionally uses two images.

### VISUAL A — WHERE YOU ARE

**Selected image:** Alev Takil / Unsplash — audience at the Metropolitan Opera House, Lincoln Center

**Source page:**  
https://unsplash.com/photos/a-large-auditorium-filled-with-lots-of-people-ZeNciLLPQas

**Recommended credit:**  
`Photo: Alev Takil / Unsplash`

**Production master filename:**  
`page-25-story-nyff-audience-alev-takil-unsplash-master.jpg`

**Role:**  
Lincoln Center / audience / cultural-evening context.

**Accuracy note:**  
Do not describe it as an NYFF photograph. Safe contextual caption: `Lincoln Center, New York.`

### VISUAL B — WHAT YOU CAME TO SEE

**Selected image:** official FLC Press asset  
**Folder:** `01 Paper Tiger (Opening Night)`  
**File:** `NYFF_Opening Night_Announcement_1600x900.png`  
**Owner/uploader shown in source:** FLC Press

**Source page:**  
https://app.box.com/s/mxm9kklymhvri5rjlfimfyptac9r9qro/file/2351177372459

**Production master filename:**  
`page-25-story-nyff-paper-tiger-opening-night-press-master.png`

**Role:**  
Direct tie to the actual NYFF64 2026 Opening Night selection, *Paper Tiger*.

**Credit:**  
Use any exact asset-specific credit instruction supplied in the downloaded FLC Press material. Until then, production tracking attribution is:

`Film at Lincoln Center / NYFF64 Press Materials`

### Page 25 layout direction

Do **not** use 50/50 image sizing.

Preferred:
- Visual A = larger contextual image
- Visual B = smaller inset / strip / secondary image
- total visual area ≈ 40–45% of STORY page

Editorial logic:

> **WHERE YOU ARE** → Lincoln Center / audience  
> **WHAT YOU CAME TO SEE** → *Paper Tiger* / NYFF64 Opening Night

---

## STORY IMAGE SOURCE MIX — ISSUE 01

The final selection intentionally avoids a single-source stock aesthetic:

- Pexels — 1
- official event press — Armory
- official event press — CBGB
- official event gallery — NYCWFF
- Unsplash — Marathon
- Unsplash + official FLC Press — NYFF

This mix is desirable.

It gives the issue:
- contemporary street photography,
- real event documentation,
- free licensed contextual imagery,
- current official press material.

The SCENE set will provide the more constructed / authored visual layer.

---

## STORY DOWNLOAD / ARCHIVE RULE

For every external image save:

```text
MASTER IMAGE
SOURCE-URL.txt
CREDIT.txt
RIGHTS.txt / RIGHTS-SCREENSHOT
```

Suggested folder:

```text
issue-001/shared/page-XX/story/
```

Detailed source / rights registry:

`THIS_YOU_ISSUE_01_STORY_IMAGE_REGISTRY_v3.md`

---

# 9. PRODUCTION ORDER

## STAGE 1 — SHARED IMAGE PLAN FINALIZATION
Approve this document.

## STAGE 2A — COLLECT STORY MASTERS
All STORY selections are now approved.

Next:
- download the 6 STORY source sets / 7 total visual files,
- archive source / credit / rights evidence,
- verify resolution,
- create production-safe master filenames.

## STAGE 2B — GENERATE SCENE VISUALS
After STORY masters are collected, generate the six SCENE visuals as one coherent authored set:

- page 06 — NYFW / 47 Minutes Between Shows
- page 10 — Armory / After Four Hours of Looking
- page 14 — CBGB / Play This Loud
- page 18 — New York After Dark / 7:03 PM Blue Hour
- page 22 — Marathon / ArtCodingLab route visual
- page 26 — NYFF / Opening Night

This separation is intentional:

> **STORY = documentary/contextual**  
> **SCENE = constructed/interpretive**

## STAGE 3 — PERSONALIZED VISUAL LANGUAGE
Establish:
- cover direction,
- arrival direction system,
- sponsor-ad direction.

## STAGE 4 — READER GENERATION
Per reader:
- page 01,
- pages 07, 11, 15, 19, 23, 27,
- page 30,
- optionally page 29.

This is the recommended order because shared visual language should be stabilized before personalized generation begins.

---

# 10. FILE NAMING EXAMPLES

## Shared

```text
page-02-concept-demo-main-master.jpg
page-02-concept-demo-main-web.webp
page-02-concept-demo-main-print.jpg

page-04-city-map-visual-master.jpg
page-04-city-map-visual-web.webp
page-04-city-map-visual-print.jpg

page-06-scene-main-master.jpg
page-06-scene-main-web.webp
page-06-scene-main-print.jpg

page-22-acl-still-main-master.jpg
page-22-acl-still-main-web.webp
page-22-acl-still-main-print.jpg

page-32-back-cover-main-master.jpg
page-32-back-cover-main-web.webp
page-32-back-cover-main-print.jpg
```

## Personalized

```text
page-01-cover-hero-master.jpg
page-01-cover-hero-web.webp
page-01-cover-hero-print.jpg

page-07-arrival-hero-master.jpg
page-07-arrival-hero-web.webp
page-07-arrival-hero-print.jpg

page-30-sponsor-personal-hero-master.jpg
page-30-sponsor-personal-hero-web.webp
page-30-sponsor-personal-hero-print.jpg
```

---

# 11. DIGITAL-ONLY EXTENSIONS

The following pages are strongest candidates for extra digital media:

## PAGE 14 — CBGB scene
Could include:
- track link,
- mini playlist,
- audio-related extra content.

## PAGE 22 — Marathon scene
Should include:
- ArtCodingLab motion piece,
- interactive or animated route visual.

## PAGE 30 — Sponsor ad
Could include:
- product click,
- product detail view,
- shop CTA,
- campaign page.

---

# 12. MVP RECOMMENDATION

For the first production cycle, keep the image workload manageable.

## Strong MVP image set

### Shared
- page 02 concept image
- page 04 city map
- 6 scene images
- page 32 back cover

### Personalized
- cover
- 6 arrivals
- sponsor ad

### Optional if time permits
- page 03 intro image
- selected story support images
- page 29 summary visual
- page 31 teaser image

This gives an efficient but premium-feeling first issue.

---

# 13. FINAL SUMMARY

The image strategy for Issue 01 is:

> **Generate assets, not whole pages.**
>  
> **Protect SCENE as the main shared-image space.**
>  
> **Reuse Arrival images on Style pages where possible.**
>  
> **Keep MASTER / WEB / PRINT variants.**
>  
> **Allow print and digital to diverge when useful.**
>  
> **Treat the sponsor page as its own image class.**
>  
> **Stabilize the shared issue world before generating personalized pages.**

This is the recommended working image system for **THIS YOU / Issue 01 — New York / Autumn 2026**.

---

# STEP 5 NOTE — CURRENT SOURCE OF TRUTH

For exact external image URLs, credits, rights and download notes, use:

`THIS_YOU_ISSUE_01_STORY_IMAGE_REGISTRY_v3.md`

This Image Plan controls **what visual belongs on each page and why**.

The Story Image Registry controls **where the external file comes from and how it must be credited/archived**.
