Skip to content

Latest commit

 

History

History
77 lines (51 loc) · 1.86 KB

Contributing.md

File metadata and controls

77 lines (51 loc) · 1.86 KB

Document Title

Table of Contents

  1. Section

  2. Section with Subsections [ First Subsection ] [ Second Subsection ]

  3. Code Examples [ JavaScript ] [ Handlebars ] [ CSS ]

    Example:

  • Primary section links should be in bold
  • Basic markdown links can be linked to the dasherized name of the section title (links are not case-sensitive, so to save keystrokes and for consistency, use lowercase)
     1. **[Section](#section)**
    
     ## Section
  • Subsection links should be inline with their parent section link and contained in square brackets with surrounding spaces [ ]
  • Markdown links to sections with floating point numbers in the title can be written in the dasherized format of the title, omitting special characters such as decimals and colons
     2. **[Section with Subsections](#section-with-subsections)**
       [ [First Subsection](#21-first-subsection) ] 
       [ [Second Subsection](#22-second-subsection) ]
     
     ## Section with Subsections
     
     ### 2.1: First Subsection
     
     ### 2.2: Second Subsection

Section

Provide overall description of this section.

Why? Provide reason that ASH adheres to this section of standards.

Section with Subsections

2.1: First Subsection

2.2: Second Subsection

Code Examples

3.1: JavaScript

When writing code examples, use four spaces for indentation when needed.

Why? Within the context of code examples, indentation with four spaces makes code blocks easier to read.

// Provide Bad example


// Provide Good example

3.2: Handlebars

<!-- Provide Bad example -->


<!-- Provide Good example -->

3.3: CSS

/* Provide Bad example */


/* Provide Good example */