-
Notifications
You must be signed in to change notification settings - Fork 386
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
start: Reorganize into Trails (Candidate #1, Take #2) #3444
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's first keep even simpler - two trails, no need to change any content (split into separate section - it looks a bit strange). We can iterate after that if needed.
Yeah, it was interesting to see all the small pages, but I don't think our engine is currently very conducive to using such short one-pagers -- maybe if we had a better <PREVIOUS, NEXT> navigation UI. Also it's very hard to review the PR with so many file changes so for a quick proposal just 2 or 3 pages with the existing content in a different order would be better indeed. I realize it will be pretty long for just 2 trails but let's try it (we can call it candidate #2) and take it from there. p.s. there's a problem in the formatting of the GS index page. |
I guess we can review the deployment. As for the order of sections (focusing on left-side nav), here's my general feedback:
But also, let's finish #3050 first! So it can be included in this. |
Closing in favor of #3455 |
Due to branching error in #3442, I renewed the PR.
This PR updates the whole Get Started section into a "trail format" we discussed in #2496. It's an example to present the GS section into a less scary way.