readme files logo readme files: contents and highlights

1 2 3 4 5 6 7


There are a few important parts of a readme.

  1. You'll want to name your project and in a sentence explain what it does.
  2. You'll want to explain how to install it.
  3. You'll want to demonstrate basic usage. Full documentation is for someplace else.

Your readme should always have these three elements. Note that you're not just doing this for other people. You're also doing this for your future self.

If you are hosting an open source project it might also make sense to explicitly mention the license and to mention how people can contribute.

Just for reference.

A # indicates a header. A single # will turn into a large header (an h1 html tag to be precise).

The smallest header is started with six bangs ###### (which generates a h6 tag).

You can create code snippets with three ticks ```.