Skip to content
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

docs: Docs button looks already pressed on homepage #183

Closed
rakyll opened this issue Sep 5, 2014 · 10 comments
Closed

docs: Docs button looks already pressed on homepage #183

rakyll opened this issue Sep 5, 2014 · 10 comments
Assignees
Labels
🚨 This issue needs some love. triage me I really want to be triaged.
Milestone

Comments

@rakyll
Copy link
Contributor

rakyll commented Sep 5, 2014

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.

@rakyll rakyll added the docs label Sep 5, 2014
@ryanseys
Copy link
Contributor

ryanseys commented Sep 5, 2014

+2 I thought this as well.

@stephenplusplus
Copy link
Contributor

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

@ryanseys
Copy link
Contributor

ryanseys commented Sep 6, 2014

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.

@stephenplusplus
Copy link
Contributor

@leomaia any ideas? :)

@leomaia
Copy link

leomaia commented Sep 6, 2014

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.

001-original-design
002-hover-state
003-alternative

@stephenplusplus
Copy link
Contributor

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".

@leomaia
Copy link

leomaia commented Sep 7, 2014

Cool! Even better.

@silvolu
Copy link
Contributor

silvolu commented Sep 8, 2014

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).

@leomaia
Copy link

leomaia commented Sep 8, 2014

Sure! No problem.

@ryanseys
Copy link
Contributor

Fixed?

@jgeewax jgeewax added this to the Core Stable milestone Feb 2, 2015
@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels Apr 6, 2020
sofisl pushed a commit that referenced this issue Sep 15, 2022
sofisl pushed a commit that referenced this issue Oct 13, 2022
- [ ] Regenerate this pull request now.

Committer: @summer-ji-eng
PiperOrigin-RevId: 434859890

Source-Link: googleapis/googleapis@bc2432d

Source-Link: googleapis/googleapis-gen@930b673
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiOTMwYjY3MzEwM2U5MjUyM2Y4Y2ZlZDM4ZGVjZDdkM2FmYWU4ZWJlNyJ9
sofisl pushed a commit that referenced this issue Nov 11, 2022
* test: use fully qualified request type name in tests

PiperOrigin-RevId: 475685359

Source-Link: googleapis/googleapis@7a12973

Source-Link: googleapis/googleapis-gen@370c729
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiMzcwYzcyOWUyYmEwNjJhMTY3NDQ5YzI3ODgyYmE1ZjM3OWM1YzM0ZCJ9

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this issue Nov 11, 2022
* fix(docs): reference docs should link to section of googleapis.dev with API reference

* fix(docs): make anchors work in jsdoc
sofisl pushed a commit that referenced this issue Nov 16, 2022
sofisl pushed a commit that referenced this issue Nov 16, 2022
* feat: support regapic LRO

Use gapic-generator-typescript v2.15.1.

PiperOrigin-RevId: 456946341

Source-Link: googleapis/googleapis@88fd18d

Source-Link: googleapis/googleapis-gen@accfa37
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiYWNjZmEzNzFmNjY3NDM5MzEzMzM1YzY0MDQyYjA2M2MxYzUzMTAyZSJ9

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this issue Nov 16, 2022
* docs: fix docstring formatting

Committer: parthea
PiperOrigin-RevId: 449545643

Source-Link: googleapis/googleapis@1bed8a0

Source-Link: googleapis/googleapis-gen@d4ccc5f
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiZDRjY2M1ZmM2MTJjMjYwNTQ2YmNlY2VmMjg3MzU3NTY4OGEwMmQ4YiJ9

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

* feat: allow users to disable spell check in search requests
feat: allow users to add labels in search requests
docs: deprecate indexable/searchable on the product level custom attributes
docs: keep the API doc up-to-date with recent changes

PiperOrigin-RevId: 452193046

Source-Link: googleapis/googleapis@4e0282f

Source-Link: googleapis/googleapis-gen@3fa3c84
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiM2ZhM2M4NGUzZGE4YzhlNjA0ZTEyOWMxNDEzNjdkZDA5MjY4NzhmMyJ9

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this issue Nov 16, 2022
🤖 I have created a release *beep* *boop*
---


## [2.0.0](googleapis/nodejs-retail@v1.8.1...v2.0.0) (2022-06-20)


### ⚠ BREAKING CHANGES

* update library to use Node 12 (#181)

### Features

* allow users to disable spell check in search requests ([#183](googleapis/nodejs-retail#183)) ([05005ea](googleapis/nodejs-retail@05005ea))


### Bug Fixes

* **deps:** update dependency @google-cloud/bigquery to v6 ([#186](googleapis/nodejs-retail#186)) ([fc07923](googleapis/nodejs-retail@fc07923))


### Build System

* update library to use Node 12 ([#181](googleapis/nodejs-retail#181)) ([809853f](googleapis/nodejs-retail@809853f))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
sofisl pushed a commit that referenced this issue Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚨 This issue needs some love. triage me I really want to be triaged.
Projects
None yet
Development

No branches or pull requests

7 participants