-
Notifications
You must be signed in to change notification settings - Fork 17
Improve Navigation Menu Readability with Shortened Labels & Tooltips #169
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,6 @@ | ||
| label: How To Guide | ||
| label: How-To | ||
| position: 10 | ||
| link: | ||
| type: generated-index | ||
| type: generated-index | ||
| customProps: | ||
| full_name: How To Guide | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,2 +1,4 @@ | ||
| label: Maintainer Retainer Program (MRP) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is a program under the Paid Open Source Model (POSM), The OSC might need to weigh in when it comes to reducing the Title. If there were multiple maintainer programs, that would make sense to reduce, otherwise while the focus is retained on MRP, I am not sure that this should change, Maybe the page needs to move?
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That makes sense. My goal with the change was purely to improve sidebar readability and layout consistency, especially on smaller screens. There was no intention to reduce the formal identity or visibility of the Maintainer Retainer Program (MRP). Given that this falls under POSM governance and may carry formal significance, I completely understand that shortening the title could introduce ambiguity. I Can: • Revert the Maintainer Retainer Program (MRP) title change, Please let me know the preferred direction, and I’ll adjust accordingly.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would suggest exploring UX improvements and CSS-only solutions if possible. That way, the full official title remains intact and we avoid any wording changes that could alter the context or formal meaning.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would like the DA's to weigh in. Originally this is here as there was drafting for CONTRIBUTING.md changes related to MRP. There are likely other POSM programs that should have suggested documentation updates and thus be listed here on devex. I value your contribution, Thanks! Just noting that some gaps should be addressed when we find them, as opposed to making small fixes that have to be done iteratively. |
||
| label: Maintainer Program | ||
| position: 3 | ||
| customProps: | ||
| full_name: Maintainer Retainer Program (MRP) | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,7 @@ | ||
| label: Developer Experience Working Group | ||
| label: Dev Experience WG | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As is common with other references, If one is shortened, so the other should be too. EX: Dev Ex |
||
| position: 30 | ||
| link: | ||
| type: doc | ||
| id: readme | ||
| customProps: | ||
| full_name: Developer Experience Working Group | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hi @chiztechnology |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Kindly ensure that package-lock.json or yarn.lock is not part of your changes unless there is a specific reason to update it. |
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.
Maybe a question for the DA's is this a single page to explain the site, or something that linkes to multiple guides? Maybe it would read How-To's in the latter example.