Draft a launch announcement (Show HN / r/learnpython / r/Python)

[abhiksark]

Part of the 0.3.0 adoption roadmap — Discovery.

Why (adoption impact)

A single good launch post (Show HN / r/learnpython / r/Python) can drive the first real wave of human users. We should have a tight, honest, demo-led announcement ready.

Scope / acceptance criteria

• Draft a launch post (markdown in this issue or docs/launch/) covering: what it is, who it's for (beginners), the Rustlings lineage, the demo GIF, and the one-liner to try it.
• Variants/titles for: Show HN, r/learnpython, r/Python.
• Honest framing (alpha, 292 exercises, feedback wanted) — no overclaiming.
• Checklist of "before posting": README/badges fixed (Welcome to pylings Discussions! #1, Improve pylings interaction model #2), demo GIF current (Submit pylings to awesome-python #8), install paths verified.

Out of scope

• Actually posting (maintainer's call on timing).

Difficulty

help wanted — writing task; coordinate with maintainer before publishing.

[stevesagronegocios673-ux]

Quick launch-copy note after reading the issue and README: the strongest launch angle is not “Python learnings, Rustlings-style” by itself. It is the loop: fix a tiny broken Python program, checks rerun as you type, and the learner stays in the terminal with hints/docs nearby. That is much easier for HN/Reddit readers to picture.

I would make the first paragraph demo-led and beginner-specific:

Pylings is a Rustlings-inspired way to practice Python: 292 small broken programs, hidden checks, and a live terminal UI that reruns feedback as you edit. It is for beginners who want short active exercises instead of another passive tutorial.

Then immediately show the one-liner path, but I would avoid leading with the future PyPI name in the launch post. The README correctly explains the python-learnings package-name situation, but in a launch post it can distract. Keep the post route simple:

pipx install "git+https://github.com/abhiksark/pylings.git@v0.1.0"
pylings init --path ./learn-python
cd learn-python
pylings

For titles, I would use different hooks per channel:

• Show HN: “Show HN: Pylings — Rustlings-style Python exercises in your terminal”
• r/learnpython: “I built a terminal practice app for learning Python by fixing small broken programs”
• r/Python: “Pylings v0.1: 292 Rustlings-style Python exercises with live checks and local docs”

One wording adjustment: “292 exercises across 31 topics” is impressive, but it should sit next to “alpha” so expectations stay honest. Something like: “This is an alpha release with 292 exercises; I am especially looking for feedback on beginner flow, confusing exercises, install friction, and terminal UX.”

For the launch body, I would keep it in this order:

1. What it is: active Python practice in a terminal TUI.
2. Who it is for: beginners / Rustlings fans / terminal learners.
3. What makes it different: live checks, hidden tests, hints, local Python docs, progress state.
4. Demo GIF.
5. Install commands.
6. Honest alpha feedback request.

The “before posting” checklist should put install verification before copy polish: if the GitHub install path, first pylings init, and demo GIF are all current, the launch post will feel trustworthy even if the wording is simple.

Want the fuller pass? I can send a tightened Show HN post draft + 5 concrete edits for the README/launch flow.