Feature one
Describe the outcome, not the mechanism. One sentence the reader can repeat to a friend.
v__VERSION__
/
local-first
/
no account
Your product,
Your product,
finally yours.
__TAGLINE__ Built for macOS, Linux and Windows, without an account and without the cloud.
Download
$
brew install --cask __SLUG__
.dmgmacOS .deb / .rpmLinux .msiWindows MIT / Apache-2.0
What it does.
Three short promises beat one long paragraph. Keep each card about a single outcome.
Feature two
Swap this well for a real screenshot, a diagram or a number. The well is where proof lives.
Feature three
A card that says less is a card that gets read. Cut anything that repeats the heading.
Up and running in a minute.
Signed builds for macOS, Linux and Windows. The buttons below resolve the latest release automatically.
Each button queries the GitHub API and points at the latest release asset for its platform; if that fails it falls back to the releases page. The mechanism is in download/README.md.
Things you might ask.
Something else? Open an issue on GitHub.
Is it really free?
Say the license, then say what it costs to run. Honesty here buys trust everywhere else.
Do you collect any data?
If the answer is "no", make it specific: what never leaves the machine, and what (if anything) the website measures.
How do updates work?
Describe the update path in one sentence. If the app checks for updates, say how often and where it checks.
What platforms are supported?
List the platforms and the minimum versions. Update this answer the day a platform changes, not later.