@@ -5,32 +5,77 @@ As one might expect,
5
5
the documentation for Read the Docs is built using Sphinx and hosted on Read the Docs.
6
6
The docs are kept in the ``docs/ `` directory at the top of the source tree.
7
7
8
- .. TODO: expand this section explaining there the PR is automatically built and
9
- the author can visualize changes without installing anything on their system.
10
- However, if there is going to be periodic/bigger contributions, it may be a
11
- good idea to install the Sphinx requirements to build our docs.
8
+ Contributing through the Github UI
9
+ ----------------------------------
10
+
11
+ If you're making small changes to the documentation,
12
+ you can verify those changes through the documentation generated when you open a PR and can be accessed using the Github UI.
13
+
14
+ #. click the checkmark next to your commit and it will expand to have multiple options
15
+
16
+ #. right-click the "details" link next to the "docs/readthedocs.org:docs" item
17
+
18
+ .. image :: /img/details_link.png
19
+
20
+ #. navigate to the section of the documentation you worked on to verify your changes
21
+
22
+ Contributing from your local machine
23
+ ------------------------------------
24
+
25
+ .. note ::
26
+
27
+ You must use python 3.6 to generate the documentation.
28
+
29
+ If you're making large changes to the documentation,
30
+ you may want to verify those changes locally before pushing upstream.
31
+
32
+ #. clone the `readthedocs.org ` repository:
33
+
34
+ .. prompt :: bash
35
+
36
+ git clone --recurse-submodules https://github.com/readthedocs/readthedocs.org/
37
+
38
+ #. install documentation requirements
39
+
40
+ .. prompt :: bash
41
+
42
+ cd readthedocs.org
43
+ pip install -r requirements/testing.txt
44
+ pip install -r requirements/docs.txt
45
+
46
+ #. build the documents
47
+
48
+ .. prompt :: bash
49
+
50
+ cd docs
51
+ make livehtml
52
+
53
+ #. the documents will be available at http://127.0.0.1:4444/ and will rebuild each time you edit and save a file.
54
+
55
+ Guidelines
56
+ ----------
12
57
13
58
Please follow these guidelines when updating our docs.
14
59
Let us know if you have any questions or something isn't clear.
15
60
16
61
The brand
17
- ---------
62
+ ^^^^^^^^^
18
63
19
64
We are called **Read the Docs **.
20
65
The *the * is not capitalized.
21
66
22
67
We do however use the acronym **RTD **.
23
68
24
69
Titles
25
- ------
70
+ ^^^^^^
26
71
27
72
For page titles, or Heading1 as they are sometimes called, we use title-case.
28
73
29
74
If the page includes multiple sub-headings (H2, H3),
30
75
we usually use sentence-case unless the titles include terminology that is supposed to be capitalized.
31
76
32
77
Content
33
- -------
78
+ ^^^^^^^
34
79
35
80
* Do not break the content across multiple lines at 80 characters,
36
81
but rather break them on semantic meaning (e.g. periods or commas).
0 commit comments