Fast by default
Say what the user gets. Then, in a second sentence, say what makes it possible.
One or two sentences that explain the project to someone who has never heard of it. Say who it is for and what it saves them — not how it is built.
Free and open source · No account required
Built with
A few of the things I'm working on. Cards are generated from
js/projects.js — add a project there and it appears here.
Write each card as a benefit to the reader, then explain the mechanism in the sentence below it.
Say what the user gets. Then, in a second sentence, say what makes it possible.
Nothing leaves the machine. Useful if privacy is a selling point for your project.
Show the exact command. People decide in seconds whether it is worth trying.
List the platforms explicitly. Ambiguity here costs you installs.
Mention the one setting power users always ask about.
Link your Discord or Discussions. Social proof converts better than adjectives.
Keep this honest. If setup takes five steps, show five — surprises cost you trust.
Give the copy-pasteable command, e.g. pip install projectname.
Point at the one config file and the two values that matter most.
Show the command and what the user should see when it works.
Answer real questions from your issue tracker. These pages rank well in search.
Answer plainly, including any limits. Vague pricing answers lose more users than high prices do.
List the hard requirements — OS, runtime version, GPU or RAM minimums.
Say exactly what leaves the machine and what does not. Link to the privacy policy.
Link the repository, the contributing guide, and the issues labelled good-first-issue.
One clear sentence restating the main benefit, then a single button. Do not offer three choices here.
View on GitHub