Move general dev docs to nengo.github.io #1251
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
|
Yay! Centralized documentation! LGTM. |
These parts of the documentation will apply to all of the projects relating to Nengo.
tbekolay
force-pushed
the
move-dev-docs
branch
from
3f339b7
to
d693858
Compare
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.
Motivation and context:
Some of the text in the dev guide applies to all Nengo projects, not just this one. By moving it, we reduce duplication across repositories, and hopefully make it faster to iterate on those docs (since building Nengo docs takes a lot of time and is released when Nengo is released).
How has this been tested?
I've build the documentation locally and it looks a-okay.
How long should this take to review?
Types of changes:
Checklist: