Merge pull request #72 from RichardLitt/mention-relation-to-node-and-npm

Add mention of relation to Node and npm
This commit is contained in:
Richard Littauer 2017-11-14 19:18:43 -05:00 committed by GitHub
commit 764aeca383
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 0 deletions

View File

@ -14,6 +14,8 @@ This repository contains:
4. [A badge](#badge) to point to this spec. 4. [A badge](#badge) to point to this spec.
5. [Examples of standard READMEs](example-readmes/) - such as this file you are reading. 5. [Examples of standard READMEs](example-readmes/) - such as this file you are reading.
Standard Readme is designed for open source libraries. Although its [historically](#background) made for Node and npm projects, it also applies to libraries in other languages and package managers.
## Table of Contents ## Table of Contents

View File

@ -2,6 +2,8 @@
A compliant README must satisfy all the requirements listed below. A compliant README must satisfy all the requirements listed below.
> Note: Standard Readme is designed for open source libraries. Although its [historically](readme.md#background) made for Node and npm projects, it also applies to libraries in other languages and package managers.
**Requirements:** **Requirements:**
- Be called README.md (with capitalization). - Be called README.md (with capitalization).
- If the project supports i18n, the file must be named accordingly: `README.de.md`, where `de` is the BCP 47 Language tag. For naming, prioritize non-regional subtags for languages. - If the project supports i18n, the file must be named accordingly: `README.de.md`, where `de` is the BCP 47 Language tag. For naming, prioritize non-regional subtags for languages.