Skip to content

Commit 55ef2fd

Browse files
authored
Merge pull request #1723 from Uma-95/1696-writing-guidelines
#1696-writing guidelines
2 parents f9a2fe4 + 6a2a697 commit 55ef2fd

File tree

2 files changed

+35
-12
lines changed

2 files changed

+35
-12
lines changed

src/user/contributing.rst

Lines changed: 35 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -20,29 +20,36 @@ Improve the documentation
2020

2121
The ``conda-forge`` documentation is version-controlled in the
2222
`conda-forge.github.io repository
23-
<https://github.com/conda-forge/conda-forge.github.io>`_ on GitHub. The source
23+
<https://github.com/conda-forge/conda-forge.github.io>`__ on GitHub. The source
2424
text is stored in `the src/ subdirectory
25-
<https://github.com/conda-forge/conda-forge.github.io/tree/main/src>`_ of this repository
26-
(**not** the docs/ subdirectory) and
27-
is formatted using Python’s `reStructuredText
28-
<http://docutils.sourceforge.net/rst.html>`_ system.
25+
<https://github.com/conda-forge/conda-forge.github.io/tree/main/src>`__ of this repository and
26+
is formatted using Python's `reStructuredText
27+
<http://docutils.sourceforge.net/rst.html>`__ system.
28+
29+
Editing the documentation directly through Github
30+
-------------------------------------------------
2931

3032
You can propose quick edits directly through the GitHub website if you have
3133
a GitHub account — for instance, `this link
32-
<https://github.com/conda-forge/conda-forge.github.io/edit/main/src/user/contributing.rst>`_
34+
<https://github.com/conda-forge/conda-forge.github.io/edit/main/src/user/contributing.rst>`__
3335
will take you directly to a web-based editor for this very webpage. In
3436
general, the file corresponding to each page in the GitHub browser has a
3537
little pencil icon in its top-right corner that lets you open it up for editing.
3638

37-
We are glad to know that you would like to contribute to the ``conda-forge`` documentation. If you are new to the conda-forge community, follow the steps below to make your first contribution:
39+
Editing the documentation locally
40+
---------------------------------
41+
42+
We are glad to know that you would like to contribute to the ``conda-forge`` documentation.
43+
If you are new to the conda-forge community, follow the steps below to make your first contribution:
3844

39-
1. `Fork <https://help.github.com/articles/fork-a-repo/>`_ the
45+
1. `Fork <https://help.github.com/articles/fork-a-repo/>`__ the
4046
`conda-forge.github.io repository
41-
<https://github.com/conda-forge/conda-forge.github.io>`_.
47+
<https://github.com/conda-forge/conda-forge.github.io>`__.
4248

4349
2. Clone this fork onto your local machine:
4450

4551
- ``git clone https://github.com/<your-username>/conda-forge.github.io.git``
52+
- ``cd conda-forge.github.io``
4653

4754
3. Create a new branch deriving from ``main`` to do your work:
4855

@@ -59,13 +66,30 @@ We are glad to know that you would like to contribute to the ``conda-forge`` doc
5966

6067
- ``make html``
6168

62-
You can check the changes locally by opening the html files in ``src/_build/html``.
69+
You can check the changes locally by opening the html files in ``src/_build/html`` or running:
70+
71+
- ``python -m http.server --directory src/_build/html``
6372

6473
6. Add and commit your changes:
6574

6675
- ``git add .``
6776
- ``git commit -m "your commit message"``
6877

69-
7. Submit a `pull request <https://help.github.com/articles/about-pull-requests/>`_ to the main repository proposing your changes.
78+
7. Submit a `pull request <https://help.github.com/articles/about-pull-requests/>`__ to the main repository proposing your changes.
7079

7180
Happy contributing!
81+
82+
Writing guidelines
83+
------------------
84+
85+
Some basic writing guidelines should be kept in mind before you start contributing:
86+
87+
1. Identify your audience and understand their skill level.
88+
2. Match the technical language with the audience's skill level proficiency.
89+
3. Try to keep it simple. In case you have to use a lot of complicated terms, provide a glossary of key terms.
90+
4. Address the audience directly as the user(s).
91+
5. While mentioning an action, use the "command" form of the verb: "Choose an option from the menu and press Enter."
92+
6. For references, provide links to related content.
93+
7. Use headings and bullet points, which makes it easier to read.
94+
8. Avoid ambiguous titles. The title should include a clear description of the page's subject.
95+
9. Check your spellings and grammar.

src/user/introduction.rst

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,6 @@ conda-forge is a community effort that tackles these issues:
3030
- Many packages are updated by multiple maintainers with an easy option to become a maintainer.
3131
- An active core developer team is trying to also maintain abandoned packages.
3232

33-
3433
How can I install packages from conda-forge?
3534
--------------------------------------------
3635

0 commit comments

Comments
 (0)