Skip to content

docs: paste-ready launch copy for LinkedIn + 3 subreddits#33

Closed
OfirHaim1 wants to merge 1 commit into
mainfrom
docs/launch-copy
Closed

docs: paste-ready launch copy for LinkedIn + 3 subreddits#33
OfirHaim1 wants to merge 1 commit into
mainfrom
docs/launch-copy

Conversation

@OfirHaim1

Copy link
Copy Markdown
Member

Single docs/launch-copy.md with four pieces tuned to their audiences, plus a posting checklist.

Piece Length Tone
LinkedIn ~280 words first-person, vulnerable hook in first 2 lines (LinkedIn truncates), MP4 attachment, ends on a question to invite engagement
/r/git ~250 words name-checks prior art (includeIf, gh auth switch, the trailing-slash gotcha), respects the audience's expertise
/r/commandline ~120 words terse, two-sentence what-it-does, no marketing copy
/r/golang ~200 words Go-stack-focused (cobra, lipgloss, GoReleaser, release-please), shows off the auto-release pipeline, asks for honest critique on tests + style architecture

Plus a posting checklist:

  • Stagger across days, don't fire same hour
  • Tuesday/Wednesday morning, sit in comments 4hrs after each
  • LinkedIn: upload MP4 (renders inline), not GIF (gets flattened)
  • Skip /r/programming + Show HN until traction from these proves out

One thing to change before posting

The "forty-seven commits" number in the LinkedIn post is mine, not yours. Replaced in the file with a flag — replace with your real number, even if it's just "a few times." Specificity beats invented specificity.

This is docs: only — no version bump, no release fires.

🤖 Generated with Claude Code
EOF
)

One file, four pieces:

  1. LinkedIn      ~280 words, hook-in-first-2-lines for the
                   "see more" cutoff, vulnerability-led, GIF/MP4
                   placeholder, ends on a question to invite
                   replies (LinkedIn surfaces posts that get
                   conversation early).

  2. /r/git        Technical/community framing — name-checks the
                   prior art (includeIf, gh auth switch,
                   IdentitiesOnly yes, the trailing-slash gotcha)
                   so the audience feels respected. Ends on a
                   question to bait engagement.

  3. /r/commandline  Terse, no-nonsense. Two-sentence what-it-does,
                   four-line setup block, no marketing copy.

  4. /r/golang     Go-stack-focused — cobra/lipgloss/huh/GoReleaser
                   /release-please. Shows off the auto-release
                   pipeline since that audience cares. Asks for
                   honest critique on tests + style-package
                   architecture.

Plus a posting checklist:
  - stagger across days, don't fire same hour
  - Tuesday/Wednesday morning, sit in comments 4hrs
  - LinkedIn: upload MP4 (renders inline), not GIF (often flattened)
  - skip /r/programming + Show HN until traction proves out

The "forty-seven commits" number is mine, not the maintainer's —
flagged in the LinkedIn section so it gets replaced before posting.
Specificity beats invented specificity.

This is a docs change only — no version bump, no release fires.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@OfirHaim1 OfirHaim1 closed this May 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants