How to write a good README? #discuss

jmfayard profile image Jean-Michel Fayard πŸ‡«πŸ‡·πŸ‡©πŸ‡ͺπŸ‡¬πŸ‡§πŸ‡ͺπŸ‡ΈπŸ‡¨πŸ‡΄ ・1 min read

Since I released my first open source project in October, I did various iterations at improving the README of my project, but I'm not really satisfied just yet.

I have found surprisingly hard to put myself, who maintains the project and knows every detail of it, in the shoes of the casual developer who would stumble upon my project without any context and not an infinite amount of attention.

Ideally, I would like him after a short read to think either

  1. that's not for me but I know why
  2. that's something for me and I will give it a try.

Do you have any recommendations on how to write a better README?

That could be examples of things to avoid, or examples of projects that do it right.


Editor guide

I usually structure my READMEs like this:

  • Quick description of what the project is and what it does
  • A quickstart "tutorial" on how to start using it
    • Requirements
    • Installation
    • Configuration
    • How to use it
  • An update/upgrade guide (unless it's quite complex, then I'll just put a link to a wiki page or something)
  • Where to find the docs
  • How to contribute to the project
  • How to report bugs in the project
  • The license

The structure and content might vary depending on the project but that's the default "template" I use when I write a README.

I like it that way because users just need to take 5 minutes to read it and know what's what.


Hope some of this info adds to the discussion.

Often a gif can be super-helpful to show how a project functions.
Example: github.com/MichaelDimmitt/gh_reveal

An image can likewise provide benefit.
Example: github.com/JohnCoates/Aerial

Logos or other images are also nice, they make the document more fun and less of a pain to read.

Also, people often like the "shields" to show numbers like num downloads/week or tests passing.

Happy to add to the discussion further.
Mac app I like to use, Giphy Capture, for making gif's


I like to think of a README very much like a college essay. Very formulaic, with a rigid and proven structure, with the intent of getting your idea across as quickly as possible.

While I am by no means an expert (or even really that great at following my own guidelines), here is the general structure I tend to stick with:

  • Introduction
    • Project name and description
    • Badges. Everyone loves badges. They help establish the trust between the project and the end-user. Badges are colorful and catch their eye, and ones like code coverage and build status build reputation. But don't go crazy. Much more than 1 full line of badges on a desktop gets too cluttery, but too few just looks lazy. 3-6 different badges is a good number for me.
    • Close the introduction with a hook, something to get a passerby interested. It might be a screenshot, a video gif with basic functionality, or a very short code snippet. You want this to be the first thing someone notices when scanning your README, which should make them pause and be interested enough to actually read the description above it and spend their precious seconds scrolling to see what's below it.
  • Body
    • Your README is not your documentation. Let me repeat this: Your README is not your documentation. It is an overview of your project, and it should get people interested in using it more.
    • Definitely include a quick-start for the project. The shortest possible example that gets someone fully up-and-running. For a library, it might be how to add the dependency and a minimal integration into an existing project. For a framework, maybe a scaffold command followed by the most basic run command.
    • A brief overview of features. Again, this is not documentation, it is just enough information to get users interested. For each notable feature, a small code snippet might be nice, and links to the full documentation page are a must. A project with a CLI might simply show a few of its commands, a library could do with a high-level overview of its API.
    • Basic configuration. What is the entry-point into tweaking the quick-start example to suit their needs. Again, this is not full documentation, but simply the first place someone should look to start changing stuff. Link back to the full API docs from here.
    • Next steps. After a user has completed the quick-start and has a basic idea of how to work with the API, it's time to lead them toward being a fully dedicated user. Link to the issue tracker, maintainer chat rooms, tags on Stack Overflow, and anything else they will need to keep going back to get get ongoing help or instruction.
  • Conclusion
    • This is the last stuff you want end-users to see. If they made it this far, it's time to bring it all home. This should primarily be targeted at contributors and maintainers rather than end-users, but should be a good reassurance to the end-users of the quality of the project and its development progress. Here are some examples of good things to put in your README conclusion, in no particular order:
    • Project license (although a link to the license is probably better, to keep the README shorter)
    • Contributor guidelines (again, a link is better). Code of conduct, how to set up and build the project for development, that kind of stuff that prospective contributors need to know.
    • References to other projects that inspired or are used in your project. Give credit where credit is due.
    • For small projects, a list of all contributors might be nice, especially in rapidly-growing projects.
    • Who's using this project?

My main point to all of the stuff above is that your README should be a springboard to everything that anyone needs to know about your project. It should primarily work to get new users intersted in trying it out, aid existing users in getting to the right channels for help, and hold the important bookmarks that maintainers will keep coming back to. And above all, Your README is not your documentation, but it should link out to the relevant pages in your full documetation whenever possible.


That makes a lot of sense, and I would have probably fallen into the "Your README is not your documentation" trap if you hadn't point it out that clearly. Thanks a lot!


You're welcome! It's definitely a temptation to use the README for documentation, since it is right there and Github displays it nicely for you. But dumping full docs into a README is just going to make it too huge for a new user to easily scan and they will leave disinterested, and it is too difficult to navigate for existing users to easily find what they need.

Github's Wiki is just as easy to use and gives you proper navigation for small, flat documentation needs. For larger and more complex docs, it's probably better to keep your markdown in the project and integrate it with a static site generator1, so that the release of the project also publishes the docs to Github Pages or something like that. Either way, it's better for everyone than putting it in your README.

  1. Orchid is a great choice of SSG for documentation. It can generate full Java or Kotlin API docs along with wikis and blogs and publish it all to Github Pages automatically, and it integrates seamlessly into your Gradle build
    </shameless-self-promotion> ↩


I always thought of README as a quick look over a project: what is it about and how to set it up quickly with some examples and a link to the documentation in case I need it. In this area, after a quick look on yours, I think it does it perfectly.


This article is pretty good about about the structure of README files: medium.com/@meakaakka/a-beginners-...

It also contains a template that you can reuse.

I especially like it when the contributors with avatars are listed at the bottom. It adds a great human touch.

  • I actually put the full license in a dedicated file and the "license" section of the README only contains a link to it. That's probably a bit redundant but it's an old habit from the time when GitHub did not include the license in the project page header.

  • That's usually something I put in the full documentation to keep the README more lightweight and free of unnecessary technical details.


Conciseness is key. My experience of READMEs has been when I need to learn something and being able to pull out the essentials. I think the README you linked is way too wordy and would suggest trimming it down.


Writing README along side with source code/feature development.
If you separate README development from source code development, you're doing it wrong.

Treat README like source code, it's an art.

So the answer is: it actually depends on the project itself.


Here is a really nice Readme Template


I just came across this README generator that might be useful you:



how do you guys think that we could improve our README ?


This may seem to be a weird question to ask, but it is not and here is WHY.

I am sure you have noticed that a lot of technical documentation is poorly written and frustrating.
Why is it so?
As it turns out, writing for users is hard work.
When you publish a project, it's because you are passionate about the topic.
Once you are ready pushing the "publish" button, you have learned even more about it, you know all the jargons, the implementation details, ...
The danger to write for you instead of writing for your users is very much present, and avoiding it is hard.
It would have been easy for me for example to write something like "Oh and by the way, don't forget to add the Gradle plugin portal in your settings file if you need too". And then my target audience (who is not ME) is like: what???
This is why I was interested by the wisdom of people that faced the same problems.
Thanks to everybody for their replies!


I use this as a rough template for many of my projects:

I also love adding shields: