Closed ericholscher closed 1 year ago
@agjohnson I'm confused, since you suggested the exact opposite on Slack: https://readthedocs.slack.com/archives/C1VM2ENUB/p1668462658520369 -- I originally suggested Product Overview, which I think is the right framing.
I'd just like to get this change out since the current implementation is confusing, so are you 👍 with Overview and we can iterate on a larger menu later?
My suggestion in that conversation was to put verbose options in a dropdown menu, which is in line with my suggestion above. Guessing this is missing from the context, as I thought you agreed with my suggestion for the dropdown in that conversation :shrug:
so are you +1 with Overview and we can iterate on a larger menu later?
I mean, I don't share the priority on renaming the about
page, so no. I would replace the top navigation with a dropdown first, which is what I described in that conversation:
https://readthedocs.slack.com/archives/C1VM2ENUB/p1668462728477219
Thinking farther ahead, "Overview" is okay title for the about
page, but I wouldn't reuse "Overview" for a dropdown later. So this would be a bad half-step. As a navigation link to a page, "Product" is horribly unclear -- it doesn't describe what to expect at all. But, as a dropdown, "Product" works better than other options, as these page links will be verbose submenu entries inside the dropdown anyways.
So to clarify, I would:
about
page yetIf you feel like managing this change and redirects twice, you can rename "about" to "product". Without the dropdown, this is a lateral move though, and doesn't seem any clearer. So seems like wasted effort.
OK. I will close this then, and wait for you to do a dropdown 👍
This makes it a bit more obvious what the page is about, and isn't confused with the
About us
page.Already put in a redirect:
:books: Documentation preview :books:: https://read-the-docs-site-community--174.com.readthedocs.build/en/174/