-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert Docs from .rst to .md, remove Sphinx and related python #1456
Comments
Please do not delete https://github.com/INN/largo/wiki/Sites-Using-Largo |
I agree on removing python from the theme, but I also think that keeping the theme and the docs at the same version number in the same repository is better than having docs be separate from the code.
|
Discovered while working on #1359, reviewing https://largo.readthedocs.io/developers/setup-documentation.html, the following commands do not run:
Other items:
The md docs can be served from github; what we really need here is a working apidocs function to make the php docblocs into markdown or rst. |
The ReadTheDocs GitHub hook has been updated for #1616, but the build is failing for the branch that allows the new ReadTheDocs build to build. (#1616). Our API docs are generated by The https://github.com/INN/largo/blob/d395c395f425351e528c123a5de207e12fb74899/Gruntfile.js#L94-L98
That python script tl;dr: it's https://github.com/avalanche123/doxphp , last updated ... 6 months ago. huh. That's earlier than I thought. |
Okay, can fix that step in the build by upgrading to latest doxphp. The PEAR server isn't available, so I've filed a bug about that: avalanche123/doxphp#14 The PR for #1616 will have an update to the install instructions to solve the install problem. |
And the ReadTheDocs build now passes, with the changes in #1680. |
Currently the theme docs are hosted in the theme in the
/docs
folder, using RST files that are parsed into html files using Python and hosted at http://largo.readthedocs.io/This ticket will achieve 3 things:
ToDo:
The text was updated successfully, but these errors were encountered: