gimpf
commented
4 years ago Well, I recently added the command history and the help system, and I think those two should definitely stay. Learning how to read the help is almost always well-spent time.
Everything else already depends on the preferred style:
- Start with purpose made commands for any single thing you can do (the current approach).
- Start with teaching the alphabet and key-chords (that was my approach).
I don't know what is more popular. It's legitimate to want to start either way. Given how fast knausj develops, approach 1 might be good enough for the first few weeks, especially when used w/eye-tracking.
However, because of my choices, I don't really know what first commands are really useful -- I still use almost none of those. Keychords all the way!
As a datapoint, the famous intro at whalequench https://whalequench.club/blog/2019/09/03/learning-to-speak-code.html is de facto approach 2.
This is the issue for discussing what to include on the Getting Started page.
TLDR: getting started should include everything necessary to get a basic working installation of Talon on all three operating systems such that when you say 'help alphabet' the alphabet appears
A set of basic commands
Lots of links to other pages where appropriate, such as links to tutorials, links to more advanced installation guides, links to troubleshooting, etc.
Now feel free to make proposals about what 'everything necessary' means, what basic commands should be included, and other things to nail down what ought to be in Getting Started.