-
Notifications
You must be signed in to change notification settings - Fork 50
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
Prepare initial version of Sphinx user docs #5
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Initial commit, more work pending
4 spaces indentation recommended.
Add section relating to hyperlinks and substitutions
Initial commit of images used in the docs. Needs cleaning up.
These have now been converted to rst.
The .txt extension makes it more intuitive to interact with the files. The default system text editor can be used.
Sphinx is now using a different theme, a lighter one. The README.md has almost all style guides necessary.
Modify main TOC in index.txt
SPHINXOPTS is now taken from the environment.
Missing colon made a recursive variable assignment.
Add developers directory to the build.
The links in the main index.txt should be only visible if compiling with HTML output.
joshmoore
referenced
this pull request
in joshmoore/ome-documentation
Aug 15, 2012
joshmoore
referenced
this pull request
in joshmoore/ome-documentation
Aug 16, 2012
To build the plone styled docs use: make html SPHINXOPTS="-D html_theme=plonematch"
In discussion with Blazej, this is ready to go. |
joshmoore
added a commit
that referenced
this pull request
Aug 17, 2012
Prepare initial version of Sphinx user docs
snoopycrimecop
pushed a commit
to snoopycrimecop/ome-documentation
that referenced
this pull request
Apr 28, 2016
Roger's corrections to TIFF wording
jburel
pushed a commit
that referenced
this pull request
Jun 12, 2019
Make the scope of in place import more explicit (edits)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial commits with content from plone and trac. A conventions doc (README) has been created for anyone wanting to create reST documents.