Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

A very (VERY) brief overview of what should (probably) go in a readme file

Root README file

Important status messages

  • Usually in the form of shields/badges

  • Shows status like builds passing/failing, code coverage, latest version etc

  • If it’s a user-facing project, links to properly rendered documentation should be included

Developer installation

  • Everything required for a new developer to get started with a working dev environment

  • Should include key commands needed to build, debug, run etc

User installation (if relevant)

  • Often not required if the project is being deployed as part of a larger stack

  • If deployed to a package index (e.g. pip, nom, yarn etc) then a quick comment on how to install/use the library or application

Developer notes

  • Any extra quirks, environment setup notes etc

  • Could include examples of IDE settings

  • Could include notes on how to create or build auxiliary files such as rendered documentation

  • No labels