Skip to content

Latest commit

 

History

History
84 lines (55 loc) · 6.74 KB

CONTRIBUTING.md

File metadata and controls

84 lines (55 loc) · 6.74 KB

How to Contribute

We welcome contributions.

By contributing, you must agree to release your contributions into the public domain with the CC0 license by waiving all copyright and related or neighboring rights to your contributed content.

Ways to Contribute

A free GitHub.com account is required to contribute using the methods below:

  1. If you'd like to discuss something, you may open a new discussion.
  2. If you found a problem and/or want to propose an edit, you may open a new issue.
    1. To propose an edit, navigate to a page in the code -- for example, the 'What is Steelmanning?' page -- click the pencil edit button, make your change, and click Commit changes, or
    2. Create a pull request.

We reserve the right to deny or accept (with or without changes) contributions for any reason.

Standards

Writing

We recommend using the free Visual Studio Code tool for writing along with the Spell Right extension. Spell checking with the extension is done automatically and errors are shown in the "Problems" view at the bottom. Any errors which are false positives should be added to the workspace dictionary by clicking on the word, then clicking the light bulb that shows above, and clicking "Add 'WORD' to workspace dictionary". If you accidentally choose to add to your "user dictionary," then delete it from .config/Code/User/spellright.dict.

Markdown

We use GitHub-flavored Markdown as the source of the content. Some tips:

  1. When using numbered lists, always use the number 1. These will be automatically numbered in the final output and avoiding manual numbering makes it easier to re-order things if needed. For example:
    1. First item
    1. Second item
    1. Third item
    

Citations

There should be a <!-- References --> section at the bottom of the Markdown file where references are placed (in alphabetic order). See an example on the methodology page. We use the APA style with Markdown characteristics which is the Author–Date Citation in square brackets, followed by a colon and space, then a link, then a space, then an apostrophe, then the APA citation, then a space, then the link again, and finally an apostrophe. If the link is a http://doi.org/ link, but there is a public download available, then the first link should be the public download link, and the final link should be the DOI link.

[Author–Date]: Link 'APA Citation. Link'

For example:

[Sanger et al., 1977]: https://www.pnas.org/doi/pdf/10.1073/pnas.74.12.5463 'Sanger, F., Nicklen, S., & Coulson, A. R. (1977). DNA sequencing with chain-terminating inhibitors. Proceedings of the national academy of sciences, 74(12), 5463-5467. https://doi.org/10.1073/pnas.74.12.5463'

The Author–Date will be converted to an anchor link so it should not include any characters other than a-z, A-Z, 0-9, &, !, $, ', (, ), *, +, ,, ;, =, -, ., _, ~, :, @, /, and ?. Most commonly, this means replacing characters with an accent with a close analog (e.g. ü with u). Such characters should be left in the APA Citation.

If a quote or comment is included, place it after the first apostrophe and follow it with &#013;&#013; (which may be used additionally at any point in the quote or comment as line breaks). If the first link is to a PDF, include the page number, if applicable, with #page=4. For example:

[Sanger et al., 1977]: https://www.pnas.org/doi/pdf/10.1073/pnas.74.12.5463#page=4 '"The method described here has a number of advantages over the plus and minus methods." (Page 4).&#013;&#013;Sanger, F., Nicklen, S., & Coulson, A. R. (1977). DNA sequencing with chain-terminating inhibitors. Proceedings of the national academy of sciences, 74(12), 5463-5467. https://doi.org/10.1073/pnas.74.12.5463'

Referencing citations

Reference citations within the text using the normal Author–Date Citation format. The reference should be a Markdown link with the link being # followed by the Author–Date Citation with spaces replaced with underscores. The most common case is to note the reference parenthetically; for example:

One of the articles on DNA Sanger sequencing ([Sanger et al., 1977](#Sanger_et_al.,_1977)) describes a faster and more accurate method than the original plus or minus method.

Originally, we used the reference-style links in Markdown (i.e. [Sanger et al., 1977][]). This had the nice feature that anything within the apostrophes of the citation was quickly seen as a hover tooltip with the mouse; however, we received feedback that, first, this doesn't work on mobile, and second, this means that citations aren't explicitly written which means they're not seen when printing. Therefore, we chose to have normal links that take the reader to the references section and from there they can go to the underlying reference link.

Citation tips

One common way to get the APA citation is to search for the resource on Google Scholar, click the "Cite" link and copy the APA section.

Images

We use a plugin for images instead of Markdown because we want to output explicit dimensions:

  • Without a link and underlying image is greater than 600px:
    {% imagesize /assets/images/image.png:img?width=600 alt="ALT TEXT" title="ALT TEXT" %}
    
  • Without a link and underlying image is less than 600px:
    {% imagesize /assets/images/image.png:img class="align-center" alt="ALT TEXT" title="ALT TEXT" %}
    
  • With a link and underlying image is greater than 600px:
    [{% imagesize /assets/images/image.png:img?width=600 alt="ALT TEXT" title="ALT TEXT" %}](/assets/images/image.png)
    
  • With a link and underlying image is less than 600px:
    [{% imagesize /assets/images/image.png:img class="align-center" alt="ALT TEXT" title="ALT TEXT" %}](/assets/images/image.png)