# THIS YOU — HOW TO BUILD A SHARED ISSUE WITH CHATGPT
## Editorial workflow manual for the non-personalized / shared part of the magazine

---

# 1. PURPOSE

This manual explains how to create the **shared editorial issue** together with ChatGPT.

This is the part of the magazine that is the same for all readers of a given issue:
- issue concept
- chapter structure
- STORY pages
- SCENE pages
- THE MOMENT setup
- interviews
- essays
- music pages
- art pages
- objects pages
- ads
- intro / contents / credits / CTA pages

The personalized parts (`YOUR ARRIVAL`, `THE STYLE`, reader-specific products and personal notes) are handled separately.

Core model:

> **Shared magazine. Personalized arrivals.**

---

# 2. WHAT WE ARE TRYING TO PRODUCE

For each issue, we want a clean editorial package that can be inserted into the system.

Example:

## ISSUE 02
**AUTUMN / ART / MUSIC / CITY**

The output we want from our collaboration with ChatGPT is:

1. issue theme
2. issue concept text
3. chapter list
4. 32-page structure
5. page-by-page content
6. image plan
7. asset naming plan
8. copy ready for the CMS
9. notes about what is shared and what is personalized

---

# 3. THE BEST COLLABORATION MODEL WITH CHATGPT

The easiest and cleanest way is this:

## STEP 1 — YOU GIVE THE ISSUE VISION

You tell ChatGPT:
- season
- issue title / theme
- desired feeling
- cities / places / events
- article ideas
- interviews
- music ideas
- artwork ideas
- fashion direction
- any references or inspiration images
- how many personalized moments you want

Example brief:

> Create an Autumn issue. I want it to feel urban, cultured, editorial and warm. The issue should connect art, music, architecture and one real event. Use 6 personalized Moments. I want one chapter about galleries, one about a rock concert, one about food, one about books, one about city walking and one about night. The recurring idea is: the city changes, and your clothes change with it.

## STEP 2 — CHATGPT PROPOSES THE ISSUE STRUCTURE

Ask ChatGPT to produce:
- issue concept
- title options
- 32-page structure
- chapter list
- page rhythm
- shared vs personalized breakdown

## STEP 3 — YOU REFINE IT TOGETHER

You discuss:
- stronger chapter names
- which articles stay
- which Moments are best
- which Scene pages should be more visual
- where to place ads / CTA / contents / credits

## STEP 4 — CHATGPT WRITES THE SHARED CONTENT

Once the issue structure is approved, ask ChatGPT to write:

- editor's letter
- concept page
- STORY texts
- SCENE copy
- article intros
- interview questions or draft
- art captions
- playlist text
- self-promo / CTA pages
- contents labels
- next issue teaser

## STEP 5 — YOU EDIT + APPROVE

You manually polish whatever matters:
- tone
- strength of writing
- cultural references
- your own ideas
- real names
- accuracy
- quotes
- any article you want to make more human

## STEP 6 — PREPARE THE ISSUE PACKAGE

Then ChatGPT helps transform the final issue into:
- a page list
- a page-by-page content map
- asset checklist
- file names
- admin import notes

This package is what goes into the magazine system.

---

# 4. RECOMMENDED ISSUE BUILDING GRAMMAR

The current editorial grammar is:

> **STORY → SCENE → THE MOMENT → YOUR ARRIVAL → THE STYLE**

For the shared editorial part, you mainly create:
- STORY
- SCENE
- THE MOMENT setup / situation

The personalized system later fills:
- YOUR ARRIVAL
- THE STYLE

## 4-page chapter model

For most personalized story packages:

### Page A — STORY
Shared article / essay / interview / culture text

### Page B — SCENE
Shared visual atmosphere / quote / playlist / image-led page / mood page

### Page C — THE MOMENT / YOUR ARRIVAL
Hybrid page:
- shared Moment situation
- personalized arrival image

### Page D — THE STYLE
Personalized products + Why it works + Style notes

This is the best rhythm for both digital and print.

---

# 5. WHAT TO ASK CHATGPT FOR

Below is the most useful sequence of requests.

## REQUEST 1 — ISSUE CONCEPT

Ask:

> Based on this vision, propose a strong editorial concept for the issue, 5 title options, a one-paragraph concept statement and 6 possible personalized Moments.

## REQUEST 2 — 32-PAGE MAP

Ask:

> Create a 32-page issue structure. Use our magazine system logic: shared issue + personalized arrivals. Use 6 four-page chapters plus front matter and closing pages.

## REQUEST 3 — PAGE-BY-PAGE OUTLINE

Ask:

> Expand the 32-page structure into a page-by-page editorial plan. For every page specify: page number, page type, whether it is shared or hybrid/personalized, chapter number, title, purpose, a 1–3 sentence content description, linked content, whether the print page needs a page-level QR, and the visual role of the page.

## REQUEST 4 — COPY DRAFTS

Ask:

> Now write the final or near-final copy for pages 1–8.
> Then pages 9–16, etc.

## REQUEST 5 — IMAGE PLAN

Ask:

> Make an asset plan for this issue. Every STORY page should normally have at least one visual anchor. For every page specify whether it needs photography, licensed press imagery, original imagery, generated editorial illustration, artwork, fashion hero image, small supporting image or no image. Also specify image source type, rights status, credit requirements, recommended file names, aspect direction (portrait / landscape / square), and whether print/web use the same source, different crops or separate renders.

## REQUEST 6 — IMPORT PACKAGE

Ask:

> Convert the issue into a CMS-ready page package with all page fields: page_number, page_type, title, subtitle, eyebrow, body_html summary, personalization_mode, layout recommendation, chapter number, accent color, image file names, links, needs_qr, qr_purpose, qr_target_mode, story_visual, image_source_type, image_credit and image_rights_status.

This is the most important request at the end.

---

# 6. HOW TO ORGANIZE THE SHARED ISSUE IN THE SYSTEM

For every issue, think in 3 layers:

## LAYER 1 — ISSUE
Example:
- issue number
- issue title
- issue slug
- season / year
- theme
- theme CSS

## LAYER 2 — CHAPTERS
Each chapter:
- chapter number
- chapter title
- category
- place
- time
- accent color / key
- line motif / graphic marker

## LAYER 3 — PAGES
Each page:
- page number
- page type
- layout key
- shared / hybrid / personalized
- text content
- image asset
- optional data_json

ChatGPT can help define all three layers.

---

# 7. RECOMMENDED DELIVERABLE FORMAT FOR THE SHARED ISSUE

When we finish an issue together, the cleanest deliverable is:

## A. ISSUE BRIEF
Example:
- Issue 02
- AUTUMN / CITY / AFTER DARK
- one-paragraph concept
- 6 chapter summaries

## B. PAGE MAP
Table or list of pages 1–32

## C. FINAL PAGE COPY
Page-by-page content

## D. IMAGE / ASSET CHECKLIST
Exactly which images are needed

## E. FILE NAMING PLAN
Consistent names for all assets

## F. ADMIN IMPORT NOTES
What goes into issue, chapter and page fields

---

# 8. RECOMMENDED FILE NAMING FOR SHARED ASSETS

To keep everything clean, use consistent file names.

## Issue folder naming

Example issue folder:

```text
issue-001/
issue-002/
issue-003/
```

## Shared asset base path

```text
assets/uploads/issues/issue-002/shared/
```

Inside, group by page or page function.

### Option A — by page number
```text
assets/uploads/issues/issue-002/shared/page-05/
assets/uploads/issues/issue-002/shared/page-06/
```

### Option B — by chapter
```text
assets/uploads/issues/issue-002/shared/chapter-01/
assets/uploads/issues/issue-002/shared/chapter-02/
```

I recommend **page-based**, because it is easier to trace.

## Recommended file names

Examples:

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

page-05-story-main-master.jpg
page-05-story-main-web.webp
page-05-story-main-print.jpg

page-06-scene-gallery-detail-master.jpg
page-06-scene-gallery-detail-web.webp
page-06-scene-gallery-detail-print.jpg

page-22-music-playlist-art-master.jpg
page-22-music-playlist-art-web.webp
page-22-music-playlist-art-print.jpg
```

Use only:
- lowercase
- hyphens
- no spaces
- no weird symbols

---

# 9. IMAGE QUALITY GUIDELINES

Because we have both web and print, it is best to keep **3 versions** when possible:

## 1. MASTER
Best quality source
- format: JPG or PNG
- long edge: ideally 3000–5000 px
- do not overcompress
- keep this as the source of truth

## 2. WEB
For digital issue
- format: WebP or JPG
- long edge: roughly 1600–2200 px
- optimized for loading speed

## 3. PRINT
For print renderer / PDF
- format: JPG or PNG
- high quality
- for full-page portrait target something around **3300 × 4200 px** or stronger
- for full-page landscape target around **4200 × 3300 px** or stronger

Important:
- if the page uses a bleed image, we will later export exact print dimensions based on POD specs
- until then, give the print file more quality rather than less

---

# 10. WHICH PAGES USUALLY NEED IMAGES

Typical 32-page issue:

## Needs strong image
- cover
- Scene pages
- Moment / Arrival pages
- art pages
- ad pages

## STORY pages — visual anchor by default
Every STORY page should normally contain at least one visual anchor.

This can be:
- licensed press/editorial image,
- original image,
- portrait,
- documentary detail,
- generated editorial illustration,
- small image sequence,
- graphic element.

The STORY image does not need to be full-page.

Typical target:
- about 35–45% visual,
- about 55–65% text,
- adjusted per layout.

## May need only small image or none
- contents
- credits
- poem,
- next issue teaser,
- exceptional intentionally text-led pages.

ChatGPT should decide the exact image role page-by-page.

### Image source rule

Preferred order:

1. licensed / official press imagery with confirmed editorial-use permission,
2. our own / commissioned / original imagery,
3. generated editorial illustration.

Do not treat publicly visible website images as automatically reusable.

Generated imagery for real events should be clearly illustrative rather than fake documentary photography.

---

# 11. HOW YOU CAN WORK WITH CHATGPT ON IMAGES

For the **shared / non-personalized** issue part, there are 3 good methods:

## METHOD A — YOU DESCRIBE THE IMAGE NEED
Example:
> I need a Scene page for Chelsea after 6pm. I want a cultured, quiet, slightly warm editorial image. It should feel like people have just moved from the street into gallery spaces.

ChatGPT helps write:
- the image brief
- the composition
- the styling
- the mood words
- file naming

## METHOD B — YOU SHOW REFERENCE IMAGES
You can upload:
- moodboard
- artwork
- photo references
- layouts
- cultural references

Then ChatGPT helps translate them into:
- page concept
- image brief
- asset role
- system placement

## METHOD C — YOU GENERATE THE VISUAL WITH CHATGPT
For artwork / scene visuals / special editorial pages, we can directly generate the image and then place it into the issue.

---

# 12. WHAT EXACTLY TO ASK CHATGPT FOR EACH PAGE

Use this page prompt format:

## PAGE CONTENT PROMPT

> Create page copy for Issue 02, page 05.  
> Page type: STORY  
> Chapter: 01  
> Chapter title: Art After Dark  
> Purpose: introduce the chapter and set up the gallery culture theme.  
> Tone: editorial, cultured, clear, elegant.  
> Length: around 220–350 words.  
> This is shared content for all readers.

## PAGE IMAGE PROMPT

> Recommend the image approach for Issue 02, page 06.  
> Page type: SCENE  
> Chapter: 01  
> Goal: visually bridge the Story to the Moment.  
> Tell me whether this should be a full-page photo, collage, artwork, quote-page or something else.  
> Also give me the ideal file name and image orientation.

This keeps the process structured.

---

# 13. HOW TO PREPARE CONTENT FOR THE EXISTING SYSTEM

The system wants structured page data.

For each page, ChatGPT should help output something like:

```json
{
  "page_number": 5,
  "chapter_number": 1,
  "page_type": "story",
  "layout_key": "story-editorial-01",
  "personalization_mode": "shared",
  "title": "ART AFTER DARK",
  "subtitle": "Chelsea after working hours",
  "eyebrow": "CHAPTER 01",
  "body_html": "<p>...</p>",
  "image_asset": "page-05-story-main-print.jpg"
}
```

For a hybrid page:

```json
{
  "page_number": 7,
  "chapter_number": 1,
  "page_type": "moment",
  "layout_key": "moment-arrival-01",
  "personalization_mode": "hybrid",
  "title": "CHELSEA GALLERY OPENING",
  "subtitle": "6:40 PM",
  "eyebrow": "THE MOMENT",
  "body_html": "<p>You’ve spent the afternoon...</p>",
  "image_asset": null
}
```

The shared issue content can therefore be prepared in a structured way before it is entered into the admin.

---

# 14. LINKS + SELECTIVE QR

For every page in the shared issue package, explicitly determine:

```text
links
needs_qr
qr_purpose
qr_target_mode
```

Important:

> **`links` and `needs_qr` are independent.**

A digital page may contain useful external links while the print page has no QR.

## DIGITAL

Links can be clickable:
- official events,
- music,
- products,
- artworks,
- sponsor CTA,
- external references.

## PRINT

Use QR only when the digital continuation is important to the page experience.

Standard cases:

### `digital_entry`
Early issue QR, normally Page 02. Opens the reader's digital edition.

### `style`
Personalized Style page. Opens the same digital page for products + reactions.

### `motion`
Print carries a still; digital carries motion / interaction.

### `sponsor`
Personalized sponsor page with meaningful CTA.

## NOT ENOUGH BY ITSELF

Do not set `needs_qr = true` only because a STORY page has:

```text
OFFICIAL EVENT ↗
```

That link remains digital-only.

## Preferred standard issue QR map

```text
02  digital edition entry
08  Style 01
12  Style 02
16  Style 03
20  Style 04
22  ArtCodingLab motion
24  Style 05
28  Style 06
30  personalized sponsor
```

This can change by issue, but the total should stay intentional and low.

---

# 16. FASTEST PRACTICAL WORKFLOW WITH CHATGPT

If you want speed, do it in this order:

## ROUND 1
You tell me the issue idea.

## ROUND 2
I produce:
- issue concept
- 32-page map
- chapter ideas

## ROUND 3
We refine it.

## ROUND 4
I write all shared copy.

## ROUND 5
I produce:
- page-by-page CMS package
- image checklist
- file naming plan
- asset quality notes

## ROUND 6
You place assets in the recommended folders.

## ROUND 7
You enter / import content into the system.

This is the cleanest human + ChatGPT workflow.

---

# 16. HOW TO HANDLE REAL INTERVIEWS / EXTERNAL MATERIAL

If you have:
- a real interview transcript
- notes
- references
- music list
- article draft

You can paste or upload it and ask ChatGPT to:
- edit it to magazine tone
- shorten it
- format it for page space
- create headline + intro + pull quote
- assign it to pages
- propose matching Scene / Moment links

This is one of the strongest ways to use ChatGPT collaboratively.

---

# 17. HOW TO MARK WHAT IS SHARED VS PERSONALIZED

For every page in the issue package, explicitly mark one of:

- `shared`
- `hybrid`
- `personalized`

Rule:
- shared = same for all
- hybrid = shared page + personalized slot (typically Moment / Arrival)
- personalized = fully reader-specific

This helps avoid confusion later.

---

# 18. WHAT THE FINAL SHARED ISSUE PACKAGE SHOULD CONTAIN

Before we move to personalization, the shared issue should ideally be complete enough that we have:

## Required
- issue title / slug / theme
- 32-page map
- all chapter records
- all shared page copy
- all hybrid page shared copy
- file naming plan
- image checklist
- layout recommendations

## Optional but helpful
- accent colors per chapter
- mood words
- art/music suggestions
- chapter one-line descriptions
- CTA page copy
- next issue teaser

---

# 19. QUICK START TEMPLATE YOU CAN SEND TO CHATGPT

You can literally use this template:

> We are creating a new issue of THIS YOU.  
> It is a shared editorial magazine with personalized arrivals.  
> Please help me build the shared issue only.  
> Theme: [insert]  
> Season/year: [insert]  
> Desired tone: [insert]  
> Main cities / events / settings: [insert]  
> I want [X] personalized Moments.  
> Proposed chapters or article ideas: [insert]  
> Please produce:  
> 1) issue concept  
> 2) 32-page structure  
> 3) page-by-page plan  
> 4) shared copy draft  
> 5) image plan  
> 6) CMS-ready structured page output  
> 7) file naming and folder plan

---

# 20. SHORT VERSION

The simplest explanation:

> **You bring the issue vision. ChatGPT helps turn it into a structured 32-page shared magazine package. Then we prepare images, file names and page data so the content can be inserted into the system cleanly.**

---

# 21. WHAT WE SHOULD DO NEXT IN PRACTICE

For the next real issue we should do this:

1. decide issue theme
2. decide 6 Moments
3. build 32-page structure
4. write pages 1–8
5. create image checklist
6. define file names / folders
7. continue through the rest of the issue
8. prepare CMS-ready page package

That is the exact workflow I recommend.