Where to go after "Get started"
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 128
- Forks
- 132
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 3
Description
The big Get Started call-to-action is wonderful. I'd like to cede more power to it.
It's in competition with the top line ("Install...Documentation"....). If the CTA is the only way into the site, people will press it gladly. If there are other ways, both alternatives lose out. Either readers won't see the top line, and they'll press the CTA and find it's not what they wanted, or they'll see both and wonder what Getting Started is if it isn't one of those other things.
The top line is hard to see on the home page, and as I argue in #238 space above the fold is at a premium. We might hand its job over to Get Started.
There would be no top line, and rather than forcibly landing the reader in Learn, Get Started would open up a menu of the options that are currently on the top line.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the home page's Get Started CTA and the top-line navigation described in the issue. Confirm how the CTA should expose the existing options and remove the competing top line; done means the home page presents one clear entry point without forcing readers into Learn.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100