docs: Docs button looks already pressed on homepage

Docs button on the homepage is highlighted in a way that it looks already pressed and I'm reading "Docs". I looked around for a while to find a link to JSDocs, knowing that they are somewhere. A user will likely to close the page assuming there is nothing besides the homepage.

+2 I thought this as well.

What would help? Flipping the hover color from dark to light (current) to light to dark?

Easiest thing I can see is making the Docs button look like all the other
buttons. Or more complicated way is move it away from all the other buttons
eg up near the installation command.

@leomaia

@leomaia any ideas? :)

I totally understand what you guys are saying.

I designed this page to be prepared to house multiple docs pages from different programming languages. The main access to the page would be through a dropdown button next to the Google Cloud Platform logo which I would not remove it even with just one language. That would give a hint to users that more content will be added in the future.

The red button would be a second and redundant point of access and that would be inserted in a carousel where you would be able to see multiple sets of "red button + external links", one for each language and instead of just simply "Docs" as a label for the button you would have "Node.js Docs", "Python Docs" and so on. Also, I wanted to make the button much more prominent than the other links.

One simple fix would be to make the button's hover state more perceivable, maybe adding a darker border or a drop shadow.

Another solution would be to provisionally change things a little bit in this area, dropping the red button and changing the title with a link to the "Docs" page.

I attached some examples.

Thanks for the background info. I think I prefer the text example, "Check out the Docs," or some variant of that phrasing, maybe even just "API Documentation".

Cool! Even better.

@leomaia

Thanks @leomaia!
I don't think that keeping the language selector would make much of a difference: the problem here is that the prominency of the Docs button makes me think that it's the selected option, and all we have for docs is the landing page that I'm seeing ( I would not think of clicking it to go the API reference).
We need a more clear call to action (e.g. "Check out the Docs" as proposed by @stephenplusplus or "Go to the API reference"), or the button to appear as the other in the nav bar (so that I understand that I'll go somewhere else when I click it).