Skip to content

Homepage CTA buttons: replace GH by Learn more#305

Merged
chalin merged 2 commits intomainfrom
chalin-homepage-cta-2021-05-22
May 25, 2021
Merged

Homepage CTA buttons: replace GH by Learn more#305
chalin merged 2 commits intomainfrom
chalin-homepage-cta-2021-05-22

Conversation

@chalin
Copy link
Copy Markdown
Contributor

@chalin chalin commented May 22, 2021

  • CTA buttons should be just that, call-to-action. We have a link to GH in the footer of every page, so we don't need it to take up a CTA button slot. Instead it makes more sense to link to the latest docs. This PR makes that change and switches the order of the buttons so that Quickstart is second (but keeps its icon so it is more eye-catching the "Learn more" before it).
  • In the second section of the page, now that we have a "Learn more" in the hero section, it makes sense to have the "Learn more" that appears there be less prominent (saving homepage vertical real estate).
  • UX / navigation contribution to New IA implementation #267

@chalin chalin added design/style Front-end site design / styling ux labels May 22, 2021
@chalin chalin requested a review from nate-double-u May 22, 2021 15:23
chalin added 2 commits May 22, 2021 11:53
@chalin chalin force-pushed the chalin-homepage-cta-2021-05-22 branch from 8a2f10d to cdd5630 Compare May 22, 2021 15:53
Copy link
Copy Markdown
Contributor

@nate-double-u nate-double-u left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with the change to the CTA buttons. One small nit, do we want to find another, appropriate, icon for the Learn More button?

It's a small change, but I appreciate the space saving on the home page. It brings the page together without crowding it.

@chalin
Copy link
Copy Markdown
Contributor Author

chalin commented May 22, 2021

Most other sites I know don't have such icons. I only included it here to catch-the-eye for the Quickstart button, which is now second.

If you feel strongly about consistency, I'd prefer dropping the icon for the Quickstart button.

@nate-double-u
Copy link
Copy Markdown
Contributor

Given the choice, I think I'd rather have the eye-catch than consistency in this case.

@chalin chalin merged commit cb7f6d6 into main May 25, 2021
@chalin chalin deleted the chalin-homepage-cta-2021-05-22 branch May 25, 2021 16:42
@chalin chalin mentioned this pull request May 25, 2021
21 tasks
@hexfusion
Copy link
Copy Markdown
Contributor

I dont have a problem with this directly but GH link should be very easy to access. It feels a little hidden now on the bottom.

@chalin
Copy link
Copy Markdown
Contributor Author

chalin commented May 25, 2021

I dont have a problem with this directly but GH link should be very easy to access. It feels a little hidden now on the bottom.

True (that the links to GH aren't prominent), and that is by design. From a documentation-website design / UX point of view, it is quite conventional to have links to the GH repo in the footer, rather than a Call-To-Action (CTA) button. CTA buttons are precious real estate used to direct readers to where they (most of them) need to go. For example, see https://kubernetes.io/.

Looking at Google Search Console results, the most popular etcd search is "etcd", which returns etcd.io followed by the link to the etcd repo, as top hits. The assumption is that if a reader clicks on the docs site, they want docs, not the repo. If they want the repo, then it's the second result in Google Search (for example) and the assumption is that they'd have clicked that link directly. Of course, there are other ways that readers can reach the site, but let's stop there for now.

Unless you feel strongly about this, I'd suggest we keep it as is. Still, thanks for the feedback @hexfusion.

@chalin
Copy link
Copy Markdown
Contributor Author

chalin commented May 25, 2021

@hexfusion - I'm not against making the link to GH more prominent, though it might be easier to assess the best way to do so once we've landed more of the new IA (#267). If you still feel that this is worth fighting for :), ... could you please open an issue? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

design/style Front-end site design / styling ux

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants