Change documentation generator to Sphinx#577
Conversation
|
Dependent on #576 being merged with CI fixes. |
1 similar comment
|
I dropped the changes from #575 from this PR. |
|
@pradyunsg how/where do we publish the docs ? Does Github run a build for Sphinx docs too ? |
|
Huh. I swear I remember responding to this. I'll setup a readthedocs.org build for us, once this is merged. |
|
@pradyunsg I'm trying a build and am running into failures. Here's what I did - And the error is:
Please send help 😕 |
|
Uh, that'll probably install an old version of sphinx for you. Debian isn't exactly super fast in updating libraries. I'd suggest building documentation using a virtualenv with the latest sphinx and recommonmark. This too can be added to the suggestions made in getting started in a subsequent PR. We could even look for into adding automation for common development processes later. |
|
Poking this again. If there's no interest in this, I'll be happy to tackle this at a later time. |
|
Hey @pradyunsg lets take it up after a few weeks .. currently busy with other tasks in CFP |
|
Works for me! |
This is an initial draft of the "new" documentation for Junction.
Some of the changes made:
python-devandbuild-essentialare unrelated to setting up the project-specific environment.npmandNodeJSare installed together, no need to call them out separately.bowerandgruntget installed as we go, so no need to ask for them to be installed already.Making a PR early to get feedback on the changes.
Currently, the main "new" document is
docs/source/development/getting-started.rst.