on master help sign in
Clarifies section on pull requests against the docs.

We don’t want people running pandoc against existing pages because it makes the diffs too hard to read. Also, newer pandocs respect the terminating --- in the yaml.

commitf868cd53e83e75b468b163e1be784456e91c5c23 authorDaryl Richter <daryl@ngzax.com> dateMon 24 Jul 2017, 20:46 (9 years ago) parentc96ea9c
1 file changed+13−5
docs/about/contributing.md+13−5
docs/about/contributing.md+13−5
@@ -22,8 +22,9 @@ source](https://github.com/urbit/arvo/blob/master/arvo/hoon.hoon).
2222
2323## Docs guidelines
2424
25−For documentation pull requests, acquire [pandoc](http://pandoc.org) and
26−format your edited files with the following flags:
25+For documentation pull requests, if you are making a brand new page, you'll want
26+it to conform to our general documentation standards. Acquire [pandoc](http://pandoc.org)
27+and make sure to format your edited files with the following flags:
2728
2829 $ pandoc --standalone \
2930 --from=markdown+yaml_metadata_block \
@@ -31,8 +32,15 @@ format your edited files with the following flags:
3132 -o output.md \
3233 input.md
3334
34−**Note:** Pandoc will convert the terminating `---` in YAML metadata to
35−`...`, which is grounds for termination. Run the following one-liner to
36−atone.
35+If you are editing an existing page, reformatting the entire page with pandoc
36+will make the diff hard to read so please don't do it. Just make sure that your
37+edits generally conform to the style of the existing docs around it. For exmaple,
38+you'll notice that the paragraphs mostly wrap at column 80.
39+
40+**Note:** If you have an old version of Pandoc, it may will convert the
41+terminating `---` in YAML metadata to `...`, which is grounds for termination.
42+Run the following one-liner to atone.
3743
3844 $ sed '1,/^$/ s/^\.\.\./---/g' input.md > output.md
45+
46+Newer versions of pandoc (1.19.2.1, for example) don't have this issue.