Skip to content

Commit 6410e3f

Browse files
committed
readmedocs
1 parent 38d7bcf commit 6410e3f

File tree

1 file changed

+17
-2
lines changed

1 file changed

+17
-2
lines changed

src/README.md

Lines changed: 17 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,18 @@
1-
To build the docs here locally: make sure you have Sphinx, the Cloud Sphinx Theme, and the sphinxcontrib-fulltoc Sphinx extension installed (`conda install sphinx cloud_sptheme sphinxcontrib-fulltoc`), then run `make html` (Unix) or `./make.bat html` (Windows). This will create the output files in `_build/html`.
1+
To build the docs here locally:
2+
* Make sure you have Sphinx, the Cloud Sphinx Theme, and the sphinxcontrib-fulltoc Sphinx extension installed (``conda install sphinx cloud_sptheme sphinxcontrib-fulltoc``).
3+
* Then run ``make html`` (Unix) or ``./make.bat html`` (Windows).
4+
* This will create the output files in ``_build/html``.
5+
6+
7+
* The docs are built on GitHub Actions and run the ``.ci_scripts/update_docs`` script.
8+
To build the docs locally, follow the steps mentioned below:
9+
1. Clone the repository into your local machine.
10+
2. Go into the main folder.Run the following commands.
11+
3. ``conda env create -f ./.ci_scripts/environment.yml``
12+
4. ``conda activate conda-forge-docs``
13+
5. ``cd newsfeed && pip install --no-deps .``
14+
6. ``cd ../src``
15+
7. ``make html``
16+
17+
* Once merged to ``master``, you can find the auto-generated html file in ``docs`` directory.
218

3-
Documentation update PRs should only change this source; once merged to `master`, [`.ci_scripts/update_docs`](../ci_scripts/update_docs) will then automatically build it into the `docs` directory.

0 commit comments

Comments
 (0)