QuQi
RÉDACTION DE CONTENU

Newsletter issue from saved links

Use when you have a week of saved links and need an issue with a view rather than a list.

curated-newsletter-issue-build.md
Télécharger le .md
You are assembling a curated newsletter issue. The value is the judgement between the links, not the links.

Saved items, each with title, source and my note: {{SAVED_ITEMS}}
Who subscribes and what they do for a living: {{SUBSCRIBERS}}
Issue length and how many items it holds: {{ISSUE_SHAPE}}
The through-line I think this week has, if any: {{THEME_HUNCH}}

Output:
1. Selection table: Item from {{SAVED_ITEMS}} | Why a reader in {{SUBSCRIBERS}} would care | Overlaps with another item | In, out or reserve.
2. Running order for the items marked in, up to the count in {{ISSUE_SHAPE}}, with the reasoning for the first slot and the last.
3. The issue itself: an opening under 120 words that makes an argument, then each item with a two to three sentence take that says the thing my note implies but does not spell out.
4. Verdict on {{THEME_HUNCH}}: supported, partly supported, or not at all. If not, say what this week is actually about.

Rules:
- Do not summarise an item beyond what {{SAVED_ITEMS}} contains. You have not read the sources.
- Cut rather than pad to reach the count in {{ISSUE_SHAPE}}.
- Nothing gets in on novelty alone. It has to be useful to {{SUBSCRIBERS}}.
- No em dashes. British spelling.

À remplir avant de lancer

Remplacez chaque espace réservé par vos propres détails. Plus vous êtes précis, moins le modèle invente.

  • {{SAVED_ITEMS}}
  • {{SUBSCRIBERS}}
  • {{ISSUE_SHAPE}}
  • {{THEME_HUNCH}}

Obtenir un meilleur résultat

  1. Write a one-line note when you save the link, since the takes are only as good as those notes.
  2. A forced theme reads worse than an honest grab bag, so believe the verdict in section 4.
  3. Keep the reserve items. A thin week is much easier with last week's rejects to hand.