Turn a GitHub README into a landing page

A README and a landing page do different jobs

The README answers "how do I build this, and how do I use it?" The landing page answers "is this for me, and what do I do next?" People who already cloned the repository do not need the landing page. People who might try it will not read a long README, a badge row, and the contributor graph.

If you paste the README into a page and change the font, you still have a README. The job is to choose.

Lift four things

Start from the README, then keep only what a stranger needs before they decide to click.

• The one sentence you would keep if you had to delete the rest.
• The problem, in the words a user would use. Not the architecture.
• Three features a person can picture. "Drop a folder of CSVs and get a monthly close" is a feature. "Uses SQLite" is a detail for the repository.
• One next step: the project homepage, a demo, or the repository. An install command can be the second step. It should not be the headline unless the product is the command.

Leave the rest in the repository

CI badges, the license badge, the table of contents, the full API, and "star this repo" do not belong above the fold. The license can be one FAQ line. The stack can be one line, not a grid of logos. A screenshot belongs if it shows the product. A screenshot of the README does not.

Nothing on the page should surprise a person who then opens the repository. If the page says it is local-first, the README should say that too. Fix the README when the page is clearer. The repository is still the source.

One action

The page needs one primary button. If the project has a homepage, that button goes there. If it does not, it goes to the repository. A second button can offer the source. Extra buttons for docs, chat, and sponsors are how a page loses the visit.

Repo2Launch keeps links on the repository or the project's own homepage. It does not turn a model-written URL into a link. That is deliberate. A generated page should not send someone to a host you did not put in the README.

Check it like a visitor

Read only the headline and the button. Do you know what it is and what to click? Then narrow the window to a phone width. The headline should wrap in a few lines, the button should be easy to hit, and the text should not be gray on gray.

The title and the description in the page head are what a chat preview and a search result will quote. They should match the headline, not a different pitch you abandoned.

Templates, not a new layout every time

Repo2Launch fills one of three fixed templates: signal, paper, or terminal. You can see all three on the examples page, built from fixture repositories rather than from customer launches. The model writes the slots: headline, features, steps, and a short FAQ. It does not invent the HTML. That keeps the page on one accessible structure and stops a bad generation from shipping a broken document.

The free preview shows the copy and a watermarked page. Nothing is deployed. $19 once removes the watermark, gives you a ZIP with index.html, vercel.json, and LAUNCH.md, and includes two regenerations. When deploy is turned on, the paid page is hosted. Read the page before you send anyone to it. A template cannot know the caveat you meant to add.