-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Update ROS Resources on Docs Index #3825
Conversation
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 extremely subjective, but the addition of all of this stuff on the front page makes it seem overwhelming to me. There are just so many links to different things here that it feels like a newcomer might get put off (this is kind of also a problem with the current page, but less so).
One idea: what if we moved most of this into the front page of "The ROS 2 Project", and then just had a link from the front page to there? At least it will be a bit more hidden and won't scare people away.
All of that said, if other maintainers think this is valuable to have on the front page, or have other ideas, I can be persuaded.
I do agree that the list is a bit long. Can I offer a counter proposal to reorganize it into a series of smaller lists? The intent here is to make sure the resources we have are easily found and up front. I think burying them deeper in the docs makes them more difficult to find. |
@clalancette I combined a few similar items and re-organized the lists. Take a look. |
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.
I think this is better, thanks. I've left a handful of things to consider changing.
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.
I've left one additional comment, but it really isn't blocking. This looks good to me now; @kscottz I'll let you merge it (and backport it) when you are ready.
* Update front page of docs to include more community resources, deprecate answers. * Clean up fussy RST. * Fix bad ref. * Fussy whitespace nitpick. * Reorganize and clarify. * Changes to wording. * remove prerelease. (cherry picked from commit 3358c49)
* Update front page of docs to include more community resources, deprecate answers. * Clean up fussy RST. * Fix bad ref. * Fussy whitespace nitpick. * Reorganize and clarify. * Changes to wording. * remove prerelease. (cherry picked from commit 3358c49)
* Update front page of docs to include more community resources, deprecate answers. * Clean up fussy RST. * Fix bad ref. * Fussy whitespace nitpick. * Reorganize and clarify. * Changes to wording. * remove prerelease. (cherry picked from commit 3358c49) Co-authored-by: Katherine Scott <[email protected]>
* Update front page of docs to include more community resources, deprecate answers. * Clean up fussy RST. * Fix bad ref. * Fussy whitespace nitpick. * Reorganize and clarify. * Changes to wording. * remove prerelease. (cherry picked from commit 3358c49) Co-authored-by: Katherine Scott <[email protected]>
This pull requests