## TL;DR

Turn a good forum answer into a blog post by expanding it: add the context the thread assumed, show the full working solution, and link back to the original thread. The post must stand alone and add value beyond the answer; a copy-paste is duplicate content that helps nobody. Canonicalize to your post if versions exist elsewhere.

```text
turning forum answers into blog posts without duplicating
```

## Use this when

- You wrote a forum answer worth preserving
- The same question keeps coming up
- Building searchable content from community work

## Not for this skill when

- The answer is two sentences (nothing to expand)
- The thread is the better home for it (link, do not copy)
- You would publish it verbatim (do not)

## Steps

1. Pick answers with expansion potential. The best candidates solved a real problem and left follow-up questions unanswered. Expected: a shortlist, not every reply.

2. Expand with missing context. The thread knew the setup; the post must explain it. Add background, the full solution, and verification steps. Expected: a stranger learns from the post alone.

3. Rewrite, do not copy. New structure, fuller explanations, your own examples. Expected: the post reads as an article, not a pasted reply.

```
expansion checklist:
  context the thread assumed: added
  full solution: shown and verified
  follow-ups from thread: answered
  link back to thread: included
```

4. Link back to the original thread. Credit the discussion and give readers the deeper context. Expected: the thread gets a pingback or mention, the post gets credibility.

5. Canonicalize if the answer exists elsewhere. If you also posted it on another platform, pick the canonical. Expected: one version search engines rank.

## Variant phrasings

### from forum reply to blog post

Expand the context, rewrite fully, link back, canonicalize.

### repurposing community answers as articles

Pick expandable answers, add what the thread assumed, stand alone.

### blog posts from support threads

The post must teach without the thread; the thread gets the credit link.

## Why it happens

Forum answers are concise by necessity and buried by design: threads age, search within forums is weak, and the same questions recur. A proper article preserves the knowledge where search engines and future readers can find it.

## Edge cases / pitfalls

- Get the tone right; a blog post lecturing where the thread discussed feels off.
- If others contributed key insights in the thread, credit them by name or handle.
- Do not strip-mine a community; a few expanded posts beat a content farm.
- Update the post when the answer goes stale; threads show their age, posts should not.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_KUaZnlXwRo80pRwjGYOcfQ