Training Page Updates

* Sectioned h2 into menu items: Tips, Tools etc
* Demoted old h2 subsections to h3 accordingly

README.md

@@ -9,9 +9,12 @@ Web pages for [dreymar.colemak.org](https://dreymar.colemak.org)
 
 TODO/WIP for the BigBag Forum & web content (mostly for DreymaR's use):
 -----------------------------------------------------------------------
+- Anchor links on the same page only need "#anchor", not the page url.
+
+
 - Training page:
-	- Mention EnterTrained next to CopyType under Type-Reading
-	- Add a section on burst training; mention 15 s MT tests, and BurstType. Emphasize varied training.
+	- Main headings: Tips, Training/Learning, Tools/Links. Reflected in more menu choices, for ease of navigation.
+	- Add a section on burst training? Mention 15 s MT tests, and BurstType. Emphasize varied training.
 
 - Alt layout writeup!
 	- Make it the first section under Layers. Update other sections to be more layout inclusive.

docs/_config.yml

@@ -47,11 +47,11 @@ links:
   - title: learning
     url: learning.html
     sub:
+      - title: Tips
+        url: training.html#training-tips
       - title: Training
         url: training.html
         sub:
-          - title: Tips
-            url: training.html#training-tips
           - title: Type-read
             url: training.html#type-reading
           - title: Lessons
@@ -62,12 +62,15 @@ links:
             url: training.html#pangram
           - title: Tarmak
             url: training.html#tarmak
+      - title: Tools
+        url: training.html#tools
+        sub:
           - title: Monkeytype
             url: training.html#monkeytype
           - title: Amphetype
             url: training.html#amphetype
           - title: Links
-            url: training.html#tools
+            url: training.html#links
       - title: Tarmak
         url: tarmak-intro.html
         sub:

docs/index.html

@@ -84,7 +84,7 @@ <h3 class="anchor" id="faq">FAQ</h3>
         <div class="spoiler-body">
             <h3>Platform Games?</h3>
             <p>
-                Selecting a platform affects the platform-specific purple boxes found here and there. For more info, see the <a href="/index.html#platform-info">Platforms section</a> below.
+                Selecting a platform affects the platform-specific purple boxes found here and there. For more info, see the <a href="#platform-info">Platforms section</a> below.
             <p></p>
                 The platform boxes on other pages generally hold info on settings etc for the implementations. Not all pages have a box (yet); some have several.
             </p>
@@ -94,7 +94,7 @@ <h3>Get a Load of This!</h3>
             </p><p>
                 You may be eager to try them out, in which case you want one of my <i>Big Bag implementation</i> repositories like the <a href="https://github.com/DreymaR/BigBagKbdTrixXKB">XKB/Linux</a> one, or <a href="https://github.com/DreymaR/BigBagKbdTrixPKL">EPKL/Windows</a>.
             </p><p>
-                Which download you want, depends on your platform/OS. So again: Have a look in the <a href="/index.html#platform-info">platform</a> box further down on this page.
+                Which download you want, depends on your platform/OS. So again: Have a look in the <a href="#platform-info">platform</a> box further down on this page.
             </p>
         </div>
     </div><br>

docs/layers-main.html

@@ -174,10 +174,12 @@ <h2 class="anchor" id="deadkeys">ENHANCED DEAD KEY MAPPINGS</h2>
 <h2 class="anchor" id="sequences">SEQUENCING</h2>
 <p>
     Modifiers like <kbd>Shift</kbd>, <kbd>Control</kbd> and <kbd>Extend</kbd> are <b>chording modifiers</b>: You hold them down while hitting the keys they modify, to access other layers. Dead keys and sticky/one-shot modifiers are <b>sequencing</b> or <b>leader keys</b> that modify following output. The <kbd>Compose</kbd> key is another sequencing key, that's pressed either before or after typing a sequence that you want translated into specific output.
+</p><p>
+    Sequences aren't really layers, but they fill a similar role. Dead key layers are layers mapped to leader keys (which may themselves be mapped on layers), so the two really are quite intertwined.
 </p><p>
     As described in an interesting article by <a href="http://xahlee.info/kbd/banish_key_chords.html">Xah Lee</a>, chording isn't always the best answer. For one-shot output like a special symbol or a single command, key sequences are generally better. The Alt key in Windows for instance, lets you access menu items by tapping a letter sequence like <b>{Alt,F,T}</b> (<u>F</u>ile → <u>T</u>ab) to open a new tab, which is intuitive and easily learnt by looking at the menus the first few times. Another good example is the <b>Compose</b> method used in Linux that can be activated either by any desired key combination similar to Autocorrect, or by a designated sequencing key such as a dead key or the Compose key.
 </p><p>
-    Even a "tap-dance" of several key strokes can be preferable to chording for many one-shot needs. Holding down keys is more tiring than tapping out a sequence, and the more contorted a chord gets the worse it will be. All tap-dances aren't created equal either, and I much prefer ones that use easily reachable keys and no same-finger bigrams. Tapping the same key several times is not the best of ideas.
+    Even a "tap-dance" of several key strokes can be preferable to chording for many one-shot needs. Holding down keys is more tiring than tapping out a sequence, and the more contorted a chord gets the worse it will be. All tap-dances aren't created equal either, and I much prefer ones that use easily reachable keys and no same-finger bigrams. Tapping the same key several times is not the best of ideas even though it is being used out there.
 </p><p>
     Sequences can be more mnemonic than layers. Let's say I want to map the old English letter <a href="https://en.wikipedia.org/wiki/Hwair">Hwair (a /ʍ/ sound like in the Scottish pronounciation of 'who')</a> to my layout for occasional use. With layers I'd have to remember where I had put it and on which layer ... hmmm, tricky. Help images like in the EPKL program can be very helpful there for sure, but only to some extent. If, on the other hand, I implement it as a Compose sequence I could for instance just type 'hw' and hit a Compose key to get a 'ƕ'. That's much easier to remember, don't you think? But only practical if it's not used all the time. If I were writing a book about Old English, I'd have the letters Ƕƕ Ȣȣ Ȝȝ and Ƿƿ somewhere in a handy layer for sure, and from frequent use I'd quickly learn where I'd put them.
 </p><p>

docs/learning.html

@@ -3,11 +3,11 @@
 title: Learning & Training
 ---
 
-<h2 class="anchor" id="training">THE BIG TYPING TRAINING BAG</h2>
+<h2 class="anchor" id="training">THE TRAINING BAG</h2>
 <p>
      The Big Bag holds a bunch of training gear. On the <b><a href="/training.html">Big Bag Training page</a></b> you'll find good tips both from the experts and me. Whether you're a seasoned veteran or fairly new to typing training, it's a recommended read.
 </p><p>
-    One example: <b><a href="https://gitlab.com/franksh/amphetype">Amphetype</a></b> is a cross-platform, layout agnostic typing program written by Frank S. Hestvik. I think it's very nice for typing texts, analyzing weaknesses and generating lessons. It's one of the training tools mentioned in the Training Topic.
+    One example: <b><a href="https://gitlab.com/franksh/amphetype">Amphetype</a></b> is a cross-platform, layout agnostic typing program written by Frank S. Hestvik. I think it's very nice for typing texts, analyzing weaknesses and generating lessons. I use it for offline type-reading.
 </p>
 
 <br><img alt="Amphetype 1 Typer" src="res/div/SpeedTraining/Amphetype_1-Typer.png" />