Border Radius Generator
Shape corners individually, including the elliptical slash syntax.
Fill in the fields and get a complete README.md in Markdown.
The README Generator turns a handful of fields into a complete README.md in the order people actually read one — what it is, whether it solves their problem, how to install it, what using it looks like — with empty sections left out entirely.
The README is the first thing anyone sees and usually the last thing anyone writes. This turns a handful of fields into a complete, conventionally ordered README.md, so the part you have to think about is the content rather than the scaffolding.
The order is not arbitrary. A visitor wants to know what this is in one line, whether it solves their problem, how to install it, and what using it looks like — in that order, and most of them leave before the fourth. So the tagline and description come first, features and installation next, and contributing, testing and licence at the bottom where people go looking for them. Empty sections are left out entirely rather than emitted as a heading with nothing under it.
Tagline, description, features, install, usage — most visitors leave before the fourth section, so the important ones come first.
A field you skip produces no heading at all, rather than a section title with nothing underneath it.
Licence, build status and npm version, generated from your repository path so they resolve rather than sitting as placeholders.
Generated with real anchors, and only offered once there are enough sections for it to be useful.
Install and usage examples are fenced with the right language, so they highlight on GitHub instead of rendering as grey text.
Add the title and a one-line description of what it does.
Features, install command, usage example, licence — anything left blank is skipped.
Build status, licence and npm version badges are generated from your repository path.
Save it as README.md in the root of your repository.
What the project is and who it is for, in language someone outside your team would understand. "A caching layer for Postgres queries in Node" tells a reader more than "A blazing fast, modern solution for your data needs" ever will.
Only if the README is long enough that someone would scroll looking for a section. Under about five sections it takes up the space where your first example should be.
The licence badge does. The build badge needs a workflow file at .github/workflows/ci.yml, and the npm badge needs the package published under that name — until then they render as "unknown".
Short enough to read at a glance and complete enough to paste and run. An example with an undeclared variable in it is worse than no example, because now the reader is debugging your README.
What people who use the README Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the README Generator. It takes half a minute and no account.
Write the first reviewShape corners individually, including the elliptical slash syntax.
Convert a duration between seconds, ISO 8601, clock time and words.
Every HTTP status code, searchable, with what it actually means.
Make every editor agree on indentation, line endings and charset.
Compare two semantic versions and test them against a range.
See a float’s sign, exponent, mantissa and its exact decimal value.
Generate time-ordered UUID v7 identifiers that index cleanly.
Explore a JSON document as a collapsible tree with paths you can copy.