-
Notifications
You must be signed in to change notification settings - Fork 490
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
Restructure docs and split into versioned and unversioned #782
Restructure docs and split into versioned and unversioned #782
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: youngnick The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold To allow multiple people to review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a huge improvement! Thanks @youngnick!
Signed-off-by: Nick Young <ynick@vmware.com>
Signed-off-by: Nick Young <ynick@vmware.com>
Signed-off-by: Nick Young <ynick@vmware.com>
22bfc29
to
5dda19f
Compare
I folded in the above suggestions plus the ones from the call, ready for a final (hopefully!) look. |
Looks great, thanks @youngnick! /lgtm |
I think it's probably safe to remove the hold on this since it seems like we reached consensus on this approach during the community meeting earlier today. If no one objects, I'll remove the hold in a few hours. |
/hold cancel |
Signed-off-by: Nick Young ynick@vmware.com
What type of PR is this?
/kind documentation
What this PR does / why we need it:
This document updates the docs site structure to have less things versioned, and adds top-level navigation. Basically, only the API Types, Guides and API reference are versioned now, since I don't think we've been changing the other things along version boundaries.
I've tried to make the navigation make a bit more sense, but haven't touched the content of the files too much (although I did notice heaps of things to fix, I'll keep those for followups).
This is a first cut, intended to set us up to be in the best place we can be without substantially changing the docs flow (by adding
mike
into the mkdocs flow, moving to Hugo, or other big change).Does this PR introduce a user-facing change?: