Recategorizes most "Hubs Cloud" docs as "Administration" #207
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
|
Cursory review, LGTM. Following the philosophy of Voltaire in that "the best is the enemy of the good" so I agree that this should be updated ASAP to reduce issues in Discord. Vote for calling this "Hubs Admin Panel" |
…e sense Why: Kubernetes administration is distinct, and "Admin Panel" is used all over. The headings on some pages did not create a useful navigation outline on the right.
|
LGTM. Thanks. This will be a nice improvement. |
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.
What?
Why?
Hubs Cloud proper is gone, but most admin tools are present in Community Edition. What people see right now is confusing, or appears irrelevant:
This pull request fixes that — we won't have to tell people "read this page, but ignore some of it..." We will have fewer people asking questions on Discord (or, worse, not asking questions and giving up) that could be answered by the docs.
It's also a large chunk to review. I'd rather polishing each page was a separate, later, pull request, so this pull request doesn't get any larger.
How to test
cd website
npm ci
npm run start
navigate to localhost:3000; observe revised navigation menu
skim Administration section
Limitations
Only a few screenshots were updated. The unchanged screen shots in the Admin section don't quite match the current UI, but are still quite useful.
After we've corrected all the incorrect info in the site, add added CE setup, we should move the Admin section to immediately after the CE setup pages.
We'll need new pages corresponding to a number of the pages that are currently hidden from navigation.