Restructues Sidebar, Highlights What to Build and Why It's Different #15
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.
This PR continues to evolve the structure of the docs.
Chris and I were unhappy with the name "Developer Keys". In fact, the whole section felt out of place. It has been removed, the content there condensed, and put right after the Welcome page.
It replaces the "Design Goals", which never attracted that much attention anyway. This way, you get introduced to SUAVE, you see what cool stuff you could build, you begin to understand how that cool stuff could even be possible from a developers' perspective, and then dive into tutorials and how to guides.
I like the idea of having those novel use cases up front, because they should be the page we update most regularly as people do awesome things and the adjacent possible expands.
Work to do: