Rework the landing page to not just be a TOC #113
Conversation
This file contains hidden or 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
|
Lift some information out of the introduction onto the landing page.
tmadlener
force-pushed
the
restructure
branch
from
7e2fafc to
27a8e56
Compare
Contributor
|
Can there be a link directly to the |
Member
Author
|
I have added it in a sentence Quick Start section. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
BEGINRELEASENOTES
ENDRELEASENOTES
This is the (very) first (of probably many) step(s) towards a revamped documentation. This doesn't do too much restructuring yet, but it makes the landing page a bit more usable by providing some high level information instead of just being a TOC.
One thing that I am also curious about is: Should we keep the current version around during the restructuring and put a link to that on to the main page, until we are done?