There seems to be a fair bit of interest for using Lapwing theory with Typey Type and more beginners choosing Lapwing over Plover, so I've been thinking about how to make the Typey Type experience better for those new starters.
Dictionary
One small step could be to include the lapwing-base.json into the webapp and, with a setting, show hints directly from Lapwing instead of Typey Type dictionary for all existing lessons.
@aerickt has said yes in principle to including the Lapwing dictionary data in the Typey Type repos (CLI, data, webapp) as a git submodule or subtree under a GPL 2.0 license (same as Plover/dictionary). Next steps are for me to try out the first small step in the webapp and share the results. As Aerick makes lots of changes to the Lapwing dictionary, keeping Typey Type up to date raises maintenance/logistics questions.
Mockups for a rough idea:
fieldchicken/field said yes for me to use their Lapwing artwork under CC by 4.0
Lapwing lessons
Later, we could explore other options like adding "folding" lessons (https://lapwing.aerick.ca/Chapter-17.html) or a Collection of Lapwing lessons.
Perhaps if the Lapwing dictionary is selected, the Progress page could show that collection instead of fundamentals lessons.
Steno layout diagram
A Lapwing steno diagram with the # where the upper left-hand S key is on the current Ward Stone Ireland diagram:
It could appear under English layouts. It could be called Lapwing or in similar fashion to the others it could be something like Upper left number key (Lapwing).
More than 1 theory
As field points out:
there's benefit of having two theories on the website show up by default because then there's a higher chance beginners won't mislead themselves into thinking that there's one 'main' way to do things […] or like a 'correct' way
There seems to be a fair bit of interest for using Lapwing theory with Typey Type and more beginners choosing Lapwing over Plover, so I've been thinking about how to make the Typey Type experience better for those new starters.
Dictionary
One small step could be to include the
lapwing-base.jsoninto the webapp and, with a setting, show hints directly from Lapwing instead of Typey Type dictionary for all existing lessons.@aerickt has said yes in principle to including the Lapwing dictionary data in the Typey Type repos (CLI, data, webapp) as a git submodule or subtree under a GPL 2.0 license (same as Plover/dictionary). Next steps are for me to try out the first small step in the webapp and share the results. As Aerick makes lots of changes to the Lapwing dictionary, keeping Typey Type up to date raises maintenance/logistics questions.
Mockups for a rough idea:
fieldchicken/fieldsaid yes for me to use their Lapwing artwork under CC by 4.0Lapwing lessons
Later, we could explore other options like adding "folding" lessons (https://lapwing.aerick.ca/Chapter-17.html) or a Collection of Lapwing lessons.
Perhaps if the Lapwing dictionary is selected, the Progress page could show that collection instead of fundamentals lessons.
Steno layout diagram
A Lapwing steno diagram with the
#where the upper left-handSkey is on the current Ward Stone Ireland diagram:It could appear under English layouts. It could be called
Lapwingor in similar fashion to the others it could be something likeUpper left number key (Lapwing).More than 1 theory
As field points out: