You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+32-15
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ First off, thanks for your interest in helping out with the documentation for Sp
6
6
For more information about Spyder, please see the [website](https://www.spyder-ide.org/), and for the core Spyder codebase, visit the [main repo](https://github.com/spyder-ide/spyder).
7
7
You can view the live documentation for current and past Spyder versions at [docs.Spyder-IDE.org](https://docs.spyder-ide.org).
8
8
9
-
Spyder-Docs is part of the Spyder IDE Github org, and is developed with standard Github flow.
9
+
Spyder-Docs is part of the Spyder IDE GitHub org, and is developed with standard GitHub flow.
10
10
If you're not comfortable with at least the basics of ``git`` and GitHub, we recommend reading beginner tutorials such as [GitHub's Git Guide](https://github.com/git-guides/), its [introduction to basic Git commands](https://docs.github.com/en/get-started/using-git/about-git#basic-git) and its [guide to the fork workflow](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project).
11
11
However, this contributing guide should fill you in on most of the basics you need to know.
12
12
@@ -20,13 +20,15 @@ Let us know if you have any further questions, and we look forward to your contr
20
20
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
21
21
22
22
-[Reporting Issues](#reporting-issues)
23
-
-[Cloning the repository](#cloning-the-repository)
23
+
-[Cloning the Repository](#cloning-the-repository)
24
24
-[Setting Up a Development Environment with Nox (Recommended)](#setting-up-a-development-environment-with-nox-recommended)
25
25
-[Setting Up a Development Environment Manually](#setting-up-a-development-environment-manually)
26
26
-[Create and activate a fresh environment](#create-and-activate-a-fresh-environment)
27
27
-[Install dependencies](#install-dependencies)
28
28
-[Installing the Pre-Commit Hooks](#installing-the-pre-commit-hooks)
29
-
-[Building the docs](#building-the-docs)
29
+
-[Building the Docs](#building-the-docs)
30
+
-[Build with Nox](#build-with-nox)
31
+
-[Build manually](#build-manually)
30
32
-[Deciding Which Branch to Use](#deciding-which-branch-to-use)
31
33
-[Making Your Changes](#making-your-changes)
32
34
-[Pushing your Branch](#pushing-your-branch)
@@ -49,9 +51,9 @@ If referring to a particular word, line or section, please be sure to provide a
49
51
50
52
51
53
52
-
## Cloning the repository
54
+
## Cloning the Repository
53
55
54
-
First, navigate to the [project repository](https://github.com/spyder-ide/spyder-docs) in your web browser and press the ``Fork`` button to make a personal copy of the repository on your own Github account.
56
+
First, navigate to the [project repository](https://github.com/spyder-ide/spyder-docs) in your web browser and press the ``Fork`` button to make a personal copy of the repository on your own GitHub account.
55
57
Then, click the ``Clone or Download`` button on your repository, copy the link and run the following on the command line to clone the repo:
56
58
57
59
```shell
@@ -208,39 +210,54 @@ Once you're satisfied, ``git add .`` and commit again.
208
210
209
211
210
212
211
-
## Building the docs
213
+
## Building the Docs
212
214
213
-
To build the docs locally with Sphinx, if you've installed Nox you can just run
215
+
The documentation is built with [Sphinx](https://www.sphinx-doc.org/), which you can invoke either using [Nox](https://nox.thea.codes/) or manually.
216
+
217
+
218
+
### Build with Nox
219
+
220
+
To build the docs using Nox, just run
214
221
215
222
```shell
216
223
nox -s build
217
224
```
218
225
219
-
For manual installations, you can invoke Sphinx yourself with the appropriate options:
226
+
and can then open the rendered documentation in your default web browser with
If using Nox, you can open the rendered documentation in your default web browser with
232
+
Alternatively, to automatically rebuild the docs when changes occur, you can invoke
226
233
227
234
```shell
228
-
nox -s serve
235
+
nox -s autobuild
229
236
```
230
237
231
-
and to additionally automatically keep rebuilding the docs when changes occur, you can invoke
238
+
You can also pass your own custom [Sphinx build options](https://www.sphinx-doc.org/en/master/man/sphinx-build.html) after a ``--`` separator which are added to the default set.
239
+
For example, to rebuild just the install guide and FAQ in verbose mode with the ``dirhtml`` builder (our noxfile automatically prepends the source directory for you, so typing the full relative path is optional):
Otherwise, navigate to the ``_build/html`` directory inside the ``spyder-docs`` repository and open ``index.html`` (the main page of the docs) in your preferred browser.
254
+
Then, navigate to the ``_build/html`` directory inside the ``spyder-docs`` repository and open ``index.html`` (the main page of the docs) in your preferred browser.
238
255
239
256
240
257
241
258
## Deciding Which Branch to Use
242
259
243
-
When you start to work on a new pull request (PR), you need to be sure that your work is done on top of the correct branch, and that you base your PR on Github against it.
260
+
When you start to work on a new pull request (PR), you need to be sure that your work is done on top of the correct branch, and that you base your PR on GitHub against it.
244
261
245
262
To guide you, issues on GitHub are marked with a milestone that indicates the correct branch to use.
0 commit comments