@@ −22 +22 @@
### The content atom
Every piece of content has a "content atom" — the single core insight, framework, or story that makes it valuable. Repurposing starts by extracting the atom, not by reformatting the surface.
+
+This atom can become: an X/Threads post, a LinkedIn post, a blog post, a newsletter segment, short-form video (Reels/Shorts/TikTok), a carousel, a YouTube video, documentation, and a podcast talking point.
−**Example content atom:**
+### AI-assisted repurposing (note)
−\`\`\`
−Atom: "Replacing 400 lines of custom RAG with 50 lines of native SDK calls
− reduced latency 12x and improved accuracy."
−\`\`\`
−This atom can become: an X thread, a LinkedIn post, a blog post, a newsletter segment, a conference talk, a YouTube video, a documentation example, and a podcast talking point.
+Newer tools automate extraction and formatting (examples: OpusClip for video clipping and LayerProof for multi-format post generation). Automation speeds work but requires a verification pass: check facts, timestamps, and metrics; confirm that generated claims are traceable to source material.
−### The adaptation matrix
+## Adaptation matrix (updated)
−Each format has different constraints and affordances:
+Each format has different constraints and affordances. Additions for 2026: carousels (LinkedIn/Instagram), short-form vertical video (TikTok/Reels/Shorts), and automated clipping tools.
| Format | Length | Depth | Audience | Proof style | Shelf life |
|--------|--------|-------|----------|-------------|------------|
+| X / Threads | 3–10 posts | Medium | Tech-savvy | Screenshots, code, concise steps | 24–72 hours |
+| X single post | ~280–500 chars (platforms vary) | Shallow | Broad tech | One metric or quote | 12–48 hours |
+| LinkedIn post | 300–1,300 words | Medium-deep | Professional | Narrative, metrics, slides | 3–14 days |
+| Instagram / LinkedIn carousel | 3–10 slides | Medium | Visual learners | Swipeable steps, visuals, screenshots | 3–14 days |
+| Blog post | 800–2,500+ words | Deep | Search + direct | Full code, benchmarks, alternatives | Months–years |
+| Newsletter segment | 200–500 words | Medium | Subscribers | Summary + link + subscriber-only context | 1–4 weeks |
+| Short-form vertical video (Reels/Shorts/TikTok) | 15–90 seconds | Shallow–Medium | Broad / discovery | Visual hook, captions, edit cuts | Weeks–months |
−| X thread | 3–10 posts | Medium | Tech-savvy | Screenshots, code | 24–48 hours |
+| Video clips / highlights | 30–180 seconds | Medium | Social + search | Clips, captions, on-screen proof | Weeks–months |
−| X single post | 280 chars | Shallow | Broad tech | One metric or quote | 12–24 hours |
−| LinkedIn post | 300–1300 words | Medium-deep | Professional | Narrative, metrics | 3–7 days |
−| Blog post | 800–2500 words | Deep | Search + direct | Full code, benchmarks | Months–years |
−| Newsletter segment | 200–500 words | Medium | Subscribers | Summary + link | 1 week |
−| Video script | 5–15 min | Deep | Visual learners | Screen recording, diagrams | Months–years |
| Documentation | Varies | Very deep | Users/developers | Code examples, API refs | Maintained |
| Conference talk | 15–30 min | Deep | Live audience | Slides, live demo | Recorded: years |
−| Podcast talking point | 3–5 min segment | Medium | Audio listeners | Verbal storytelling | Months |
+| Podcast segment | 3–10 min | Medium | Audio listeners | Verbal storytelling, examples | Months |
−### The repurposing waterfall
+## The repurposing waterfall (updated)
−Content flows downhill from high-effort to low-effort formats:
+Content flows downhill from high-effort canonical sources to constrained formats. New recommended paths:
+Canonical source (blog, long video, whitepaper)
+ ├── Blog (canonical SEO source)
+ ├── Long-form video / recorded talk → automated clip extraction (OpusClip) → shorts
+ ├── LinkedIn article (expanded narrative + slides)
−\`\`\`
+ ├── Carousel (3–8 slides) for Instagram/LinkedIn (visual summary)
−Long-form source (blog, talk, video)
− ├── LinkedIn article (extract narrative + key takeaways)
├── X thread (compress to 5–7 punchy posts)
+ ├── Newsletter segment (summarize + subscriber-only hook)
− │ └── X single post (extract the single best line)
+ └── Documentation example (code + how-to)
− ├── Newsletter segment (summarize + add subscriber-only context)
− ├── Documentation example (extract the code + explain for users)
− └── Podcast talking point (adapt the story for verbal delivery)
−\`\`\`
+Video-first source (YouTube/recording)
+ ├── Run automated clipping (OpusClip / Descript highlights)
+ ├── Produce short-form videos (vertical) and clips with captions
+ ├── Extract transcript → blog post skeleton → expand with code/metrics
−**Reverse waterfall (bottom-up):**
+ └── Create carousel and thread from transcript highlights
−Sometimes a short post performs well and warrants expansion:
−\`\`\`
+Reverse waterfall still applies: a viral short or thread can be expanded into a long-form blog, video, and documentation.
−Viral X post
− ├── Expand into X thread (add context, proof, steps)
− ├── Expand into blog post (add full code, benchmarks, alternatives)
− ├── Expand into video (screen-record the walkthrough)
− └── Expand into newsletter feature (add subscriber-exclusive insights)
−\`\`\`
−### Adaptation, not duplication
+## Adaptation, not duplication
−Repurposing means rewriting for the format, not reformatting the same text:
+Repurposing means rewriting for the format, not reformatting the same text. Automation helps with formats but requires editing and verification.
−| Duplication (bad) | Adaptation (good) |
+## Content freshness layers (unchanged but emphasized)
−|-------------------|-------------------|
−| Copy-paste X thread to LinkedIn | Rewrite as narrative with expanded context |
−| Paste blog post intro as newsletter | Write a personalized summary with a "why this matters to you" angle |
−| Read blog post verbatim in video | Screen-record the actual process with verbal commentary |
−| Embed entire thread in blog post | Expand each thread post into a full paragraph with code examples |
−
−### Content freshness layers
