Open source
A maintainer’s front door that is not the GitHub tab
GitHub is the workshop. Journalists, designers, and security people still need one HTML page: what the project is, how to fund it, how to report a hole, and a human sentence.
GitHub is where the code lives. It is a bad homepage for a journalist on a deadline, a designer who saw a TikTok, or a security officer who searched a project name after a CVE. Those people need one HTML door: what this is, how to pay you, how to report a vulnerability without posting it in public, and evidence that a human maintains it. A link list full of Discord, merch, and a buried “star the repo” button trains them to leave.
The README stays the document for people who clone. The hub is the document for everyone else. Duplicate the one-line description. Do not duplicate the architecture diagram.
Four audiences, four doors
Users. First button: docs or quickstart, labeled with the outcome (“Install the CLI”). Not your personal patronage drama. A one-liner on the page: what it does, the license, the language and version floor, and maintenance status in words you will honor — active, best-effort, or looking for co-maintainers. “Active” while issues sit unanswered for a year is how trust dies. Say best-effort if that is the truth.
Sponsors. A button to GitHub Sponsors or Open Collective, plus the sentence about what money does not buy: it does not buy a merged pull request, a private feature, or your weekends. Companies sponsor to put a logo on a README. Show the logo sizes and the invoice path. Individuals sponsor because they like the work. Show one human sentence. One button labeled “Sponsor” can serve both if the destination explains the tiers. Mixing sponsorship with a token sale is how the company counsel closes the tab. Do not do it on the same page without a very explicit split, and probably do not do it at all if you want the company.
Security. A private path only: an email or a form that does not publish the report. Link SECURITY.md in the repo. Never a public Discord channel called #security. Never a bug bounty tweet that asks people to paste details. If you have a custom domain on Pro, you can host security.txt there; the hub should still point at the policy in human words. Do not put reproduction steps for an unpatched issue on the page. Do not put tokens, keys, or customer data in the bio — they would also be copied into llms.txt if that file is public.
Press and jobs. A 90-word bio, a headshot, and talks if you speak. Merch last, if ever. The press shape, if you get real requests, is a press room. A small project can keep the 90 words on this hub and skip a second site.
Put it where the single-link fields are
GitHub’s profile website field, a conference badge, a TikTok that unexpectedly blew up, and the package registry’s “homepage” URL should all be this hub. Publish it. Five free links match the four audiences plus a changelog. Pro at 7€/month is oss.yourname.com with SSL, which is also the host that makes security.txt look like it belongs to you.
The README’s first line links to the hub for “who maintains this and how to fund it.” The hub links to the README for “how to build it.” Neither tries to be the other.
Maintenance status is a feature
Write the status where a new issue-filer will see it, not only in a pinned issue from 2022. If you are paused, say what paused means: security fixes only, no features, looking for a maintainer. If you stepped down, name the new maintainer and link their hub or their profile. A project that looks maintained and is not will be cited as maintained. The file a crawler might quote mirrors your bio. Keep the status sentence in the bio so the mirror is honest. That mirror is llms.txt.
A changelog or release line (“2.4.1, March, fixes the date parser”) does more for a technical visitor than a mission statement. Link the releases page. On the hub, repeat the latest version in text.
What not to hero
A Discord you do not moderate. A Twitter feed. A course platform that implies the project is a funnel for the course — say it if it is true, and do not hide it. A personal political essay on the project’s front door. Your personal page can exist. The project page should let a user install the software without a loyalty test. Split URLs if both matter.
Also skip fake download counts. Technical readers notice, and a quoted number you invented will be the number that sticks. If you want a real figure, take it from the registry and date it (“PyPI, March 2026, about …”) only if you are looking at the registry when you type it. Otherwise omit it.
A release-day pass
When you tag a version, update the version sentence, confirm the docs button hits the new docs, and confirm the sponsor button still lands on the account that receives funds. Dead sponsor links are a particular kind of own-goal. Then ignore the urge to rebuild the hub in a new design tool. The users wanted the release notes.
The workshop stays on GitHub. The front door is one page a non-cloner can use: install, fund, report privately, and see that a person is still there.
Create my page — Pro is 7€/month (~$7)
Free to start. Pro is 7€/month (~$7 depending on exchange) for a custom domain and full SEO controls.