-
Notifications
You must be signed in to change notification settings - Fork 206
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
Getting started: finding kata #61
Conversation
…ewars/docs into getting-started_finding-kata
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.
reviewed. Some changes will depend on #74 last question
'forgot about the picture: in the first picture, I'd use "Training setup" rather than "Trainer setup" (it clashes with cw's "trainer". That's part of the reason I changed the title in one of the suggestions above) |
emphasize easy tasks and not difficult ones Co-authored-by: Blind4Basics <[email protected]>
Co-authored-by: Blind4Basics <[email protected]>
I think it's good enough as a first draft. We'll update as we add more linked docs. Also, we should open issues for improvements on existing pages. By the way, when merging a pull request with many commits like this one, use "Squash and merge": This will keep the commit history of the master branch clean, while keeping the incremental history here. I might make this the only option. |
#40
Most of this page is reused content of original "getting started" pop-up presented currently to newbies. I reused it because I assumed that if it's still there, then it's good enough, but maybe you;d like to have it completely redone?