# Community forum Human Guide

## What This Is For
Guides forum promotion, community invitation, and vertical community marketing. It gives the agent a clearer input/output frame for social content: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Community forum agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for community forum.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Community forum guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- **Goal**: Leads, community growth, brand awareness
- **Platform fit**: Indie Hacker, HN, Reddit, Discord, vertical forums
- **Timeline**: One-time launch vs sustained (4-6 months for Indie Hackers)
- **Sustained engagement**: 4–6 months; not a one-time launch
- **Content**: Authentic journey posts; product "sprinkled within"; avoid heavy promotion
- **Result**: ~23% conversion vs Product Hunt ~3%; organic traffic from authentic sharing
- **Forum** selection and approach (HN vs IH vs industry)
- **Community invitation** plan (welcome email, CTA, banner, EDM, Discord)
- **Vertical channel** targeting
- **Content** strategy (authentic vs promotional mix)
- **Timeline** (launch vs sustained)
- **reddit-posts**: Reddit post copy, subreddit rules

## Decision Points And Nuance
The original skill emphasizes: Initial Assessment, Forum Types, Discourse (Self-Hosted Forum) SEO, Hacker News Launch, Indie Hackers Best Practices, Community Invitation Tactics, Vertical Community Channels, Natural Traffic (Complementary), Brand Basics (Encyclopedia, Q&A), Output Format.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- | **Topic structure** | First post carries SEO weight; write clear titles and substantive opening posts; avoid fragmented short topics |
- | **Subdomain vs subdirectory** | Discourse recommends subdomain for operational reasons; search engines do not inherently favor either for ranking—choose based on infrastructure, not SEO alone |
- | **Timing** | Tue-Thu; peak US hours; avoid weekends, Mon, Fri |
- **Content**: Authentic journey posts; product "sprinkled within"; avoid heavy promotion
- | **Niche over broad** | Industry-specific subgroups; avoid mass posting |
- | **Caution** | Mass posting risks removal; match community tone; choose wording carefully |

## Copy-And-Paste Prompt
```text
Use the Community forum human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the kostja94/marketing-skills skill entry for `community-forum`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Channels: Community & Forum Promotion

Guides forum promotion, community invitation, and vertical community marketing. Community-led growth (CLG) costs ~90% less than paid acquisition with ~3.2x higher customer LTV. Indie Hackers delivers ~23% conversion vs Product Hunt ~3%; HN and Reddit require sustained engagement. For cold start planning (first users, launch channels), see **cold-start-strategy**. For indie hacker strategy (first 100 users, Build in Public content framework, Indie Hackers tactics), see **indie-hacker-strategy**.

**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and brand voice.

Identify:
1. **Goal**: Leads, community growth, brand awareness
2. **Platform fit**: Indie Hacker, HN, Reddit, Discord, vertical forums
3. **Timeline**: One-time launch vs sustained (4-6 months for Indie Hackers)

## Forum Types

| Platform | Audience | Use |
|----------|----------|-----|
| **Indie Hacker** | Indie makers, founders | Sustained engagement; authentic journey posts; ~23% conversion vs PH 3% |
| **Hacker News** | Tech, startups | Show HN launch; ~1,300 posts/day; front page = luck + timing |
| **Hackernoon** | Dev, tech readers | Content distribution |
| **Industry forums** | Niche verticals | Discount codes for leads; search "[industry] forum"; post event/activity promotion; see **discount-marketing-strategy** for code strategy |
| **Reddit** | Subreddit-specific | See **reddit-posts**; 90/10 rule; 29+ posts for traction |
| **Discourse (self-hosted forum)** | Community-specific | Owned forum; full SEO/GEO control; see Discourse SEO section below |

## Discourse (Self-Hosted Forum) SEO

If you run a Discourse forum (or similar self-hosted forum), SEO/GEO considerations differ from posting on third-party platforms:

| Practice | Guideline |
|----------|-----------|
| **Guest access** | Allow anonymous reading for categories meant to attract traffic; login-only mode severely limits indexed pages |
| **Topic structure** | First post carries SEO weight; write clear titles and substantive opening posts; avoid fragmented short topics |
| **Sitemap & robots** | Discourse generates sitemaps automatically; monitor in GSC as a separate property (subdomain or subdirectory) |
| **Content quality** | Merge duplicates, mark resolved threads, surface FAQ topics—forum-level quality signals affect crawl and citation |
| **GEO** | Structured topic titles and well-formed opening posts are extractable by AI tools; forum format with timelines and accepted answers lends credibility |
| **Subdomain vs subdirectory** | Discourse recommends subdomain for operational reasons; search engines do not inherently favor either for ranking—choose based on infrastructure, not SEO alone |

## Hacker News Launch

| Practice | Guideline |
|----------|-----------|
| **Title** | "Show HN: [Product] - [specific problem solved]"; honest, no clickbait |
| **Timing** | Tue-Thu; peak US hours; avoid weekends, Mon, Fri |
| **First comment** | Invitation to engage; product status (beta/MVP); differentiated solution; try-it link |
| **Assets** | Live demo, GIFs, screenshots, 30-60s demo video |
| **Expectation** | Traffic spike, not sustained growth; partly luck-dependent |

## Indie Hackers Best Practices

- **Sustained engagement**: 4–6 months; not a one-time launch
- **Content**: Authentic journey posts; product "sprinkled within"; avoid heavy promotion
- **Result**: ~23% conversion vs Product Hunt ~3%; organic traffic from authentic sharing

For full Indie Hackers tactics, Build in Public content framework (40/30/20/10), first 100 users → **indie-hacker-strategy**.

## Community Invitation Tactics

| Channel | Method |
|---------|--------|
| **Welcome email** | Post-signup automation; 4x open, 5x CTR vs regular campaigns |
| **Homepage CTA** | Button, popup, banner; above-the-fold upgrade CTA |
| **In-site placement** | High-visibility areas; user-focused sections (e.g. dashboard, settings) |
| **Banner** | Homepage, carousel below hero |
| **Registration emails** | Success/confirmation email with community link |
| **EDM campaign** | Newsletter + banner, interview-for-membership |
| **Discord** | Post event/community info; founder engagement 2-3h/day |
| **Vertical forums** | Search "[industry] forum"; post event/activity promotion |
| **Post-login form** | In-app signup form shown after login; high-intent placement |

**Welcome email best practices**: One clear CTA per email; front-load value in subject; personalize (signup source, interests); link to best content, events; ask questions (~75% reply rate). Automated 2-4 email sequence.

## Vertical Community Channels

| Principle | Guideline |
|-----------|-----------|
| **Target** | Find channels where target audience gathers |
| **Niche over broad** | Industry-specific subgroups; avoid mass posting |
| **Caution** | Mass posting risks removal; match community tone; choose wording carefully |