Heartly Readme Boilerplate 💕

This repository is a README boilerplate. It's open source. Updates and suggestions are appreciated.

---

Setup   Stardards   Headers   Navigation   API Documentation   Testing   Cites & Thanks

---

Readmes are used to describe the contents of code repositories. Besides the title, description, and code directory, readmes are the first thing users see. This boilerplate contains items to assist in writing readmes.

Setup

Install Heartly Readme Boilerplate

1npm i heartly-readme-boilerplate --save-dev

Copy DEFAULT_README.md

1npx copy-heartly-default-readme

Edit DEFAULT_README.md to work as needed.

Standards

The standard section is the core section of the readme-boilerplate. It contains definitions and context for the rest of the readme-boiler-plate.

Headers

Headers for readme's should include a title h1, a sub-description h5, and a description p. After the header, the readme should contains sections that contain titles h2 and sub-titles h3.

---

The readme boiler plate writes out the title with the h1 tag rather than markdown so that the element is centered using the align attribute once marky-markdown issue 404 is fixed.

1<h1>This a header 💕</h1>

The pre-description is added before a full description. It is written on like this so that the element can be centered (see here for why it is not currently).

1<h5>This is a pre-description</h5>

The description should describe the product. It follows and linebreak ---.

1---
2
3A description

---

All together, this is a header that can be copied.

1<h1 align="center">This a header 💕</h1>
2
3<h5 align="center"This is a pre-description</h5>
4
5---
6
7A description

Navigation

Navigation can be provided if the is more than 1 section to a readme or document. Navigation links to sections within the readme and document.

Here is how navigation is written.

1<p align="center">
2  <a href="#section">section</a>&nbsp;&nbsp;
3  <a href="#section">section</a>&nbsp;&nbsp;
4  <a href="#section">section</a>
5</p>

API Documentation

There is more than 1 way to approach API documentation. For smaller APIs, readmes can document APIs using tables or lists.

Table Format

Name	Default	Description
initiate	function(){}	it is initiated
start	function(){}	it is started

1| Name | Default | Description |
2|---|---|---|
3| initiate | `function(){}` | it is initiated |
4| start | `function(){}` | it is started |

List Format

• API
  • initiate: f
    • function(){}
    • example: an example
    • a description
  • start: f
    • function(){}
    • example: an example
    • a description

1- **API**
2  - **initiate:** `f`
3     - `function(){}`
4     - _example:_ an example
5     - a description
6  - **start:** `f`
7     - `function(){}`
8     - _example:_ an example
9     - a description

---

Testing

Currently readme render testing is manual.

Manual Testing

• Github Github renderer via Elijah Insua
• NPM's marky-markdown renderer via Revin Guillen

---

Contributing

Contributing guidelines can define how to file issues, contributors, submitting pull requests, and defining how

Cites & Thanks

The Heartly project is a set of lists and tools to help make the online code discussions more friendly. It moves forward with inspiration from discussions with Brian Gonzalez, Jason Farmer, Patrick Fisher, and Arjan Singh.