diff --git a/c/todo.txt b/c/todo.txt
index 64f45063f..726f3526e 100644
--- a/c/todo.txt
+++ b/c/todo.txt
@@ -36,14 +36,15 @@ TOP OF LIST
   o docs:
     - manpage is now autogenned
     - precedence & semantics docs
+    - HTML pages are now PDF-renderable
 
-* full-int64 I/O & math:
-  o visually check all precedence stackings (horiz/vert) in the grammars
-    against the operator prec/assoc table
-  o dsls bake deps
+* visually check all precedence stackings (horiz/vert) in the grammars
+  against the operator prec/assoc table
+* dsls bake deps
 
 ----------------------------------------------------------------
 * etc feature:
+-> or maybe just cookbook entry ... and/or xref to estdonetime
   - in1 optional: t (epoch seconds); default systime()
   - in2: nleft
   - in3 optional: target #/field name
diff --git a/doc/build.html b/doc/build.html
index 3439707a2..0b68963db 100644
--- a/doc/build.html
+++ b/doc/build.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> Compiling, portability, dependencies, and testing </titleinbody> </center>
     <p/>
     
diff --git a/doc/contact.html b/doc/contact.html
index d4e89edd5..c72c90e17 100644
--- a/doc/contact.html
+++ b/doc/contact.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> Contact information </titleinbody> </center>
     <p/>
     
diff --git a/doc/css/poki-callbacks.css b/doc/css/poki-callbacks.css
index 41634d130..a89a918c1 100644
--- a/doc/css/poki-callbacks.css
+++ b/doc/css/poki-callbacks.css
@@ -9,7 +9,6 @@
   padding-bottom: 10px;
   padding-left:   10px;
   padding-right:  10px;
-  overflow-y:     scroll;
   height: 1500px;
 }
 
diff --git a/doc/data-examples.html b/doc/data-examples.html
index 7f26f8fca..11afcd7e1 100644
--- a/doc/data-examples.html
+++ b/doc/data-examples.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> Data examples </titleinbody> </center>
     <p/>
     
diff --git a/doc/etymology.html b/doc/etymology.html
index 15042792d..3803e5a12 100644
--- a/doc/etymology.html
+++ b/doc/etymology.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> Why call it Miller? </titleinbody> </center>
     <p/>
     
diff --git a/doc/faq.html b/doc/faq.html
index ac67eddc0..a2191b457 100644
--- a/doc/faq.html
+++ b/doc/faq.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> FAQ </titleinbody> </center>
     <p/>
     
diff --git a/doc/feature-comparison.html b/doc/feature-comparison.html
index db5c434a8..c063552d9 100644
--- a/doc/feature-comparison.html
+++ b/doc/feature-comparison.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> Miller features in the context of the Unix toolkit </titleinbody> </center>
     <p/>
     
diff --git a/doc/file-formats.html b/doc/file-formats.html
index 3927a4cf1..eb9d5c9aa 100644
--- a/doc/file-formats.html
+++ b/doc/file-formats.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> File formats </titleinbody> </center>
     <p/>
     
diff --git a/doc/index.html b/doc/index.html
index 451549421..bcca94836 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> About Miller </titleinbody> </center>
     <p/>
     
diff --git a/doc/internationalization.html b/doc/internationalization.html
index 3ad75db55..6bab59a81 100644
--- a/doc/internationalization.html
+++ b/doc/internationalization.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> Internationalization </titleinbody> </center>
     <p/>
     
diff --git a/doc/originality.html b/doc/originality.html
index 075eca4cf..8b1e5b8b4 100644
--- a/doc/originality.html
+++ b/doc/originality.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> How original is Miller? </titleinbody> </center>
     <p/>
     
diff --git a/doc/performance.html b/doc/performance.html
index e69e1b5c0..768eea5aa 100644
--- a/doc/performance.html
+++ b/doc/performance.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> Performance </titleinbody> </center>
     <p/>
     
diff --git a/doc/record-heterogeneity.html b/doc/record-heterogeneity.html
index db408674c..64049ae94 100644
--- a/doc/record-heterogeneity.html
+++ b/doc/record-heterogeneity.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> Record-heterogeneity </titleinbody> </center>
     <p/>
     
diff --git a/doc/reference.html b/doc/reference.html
index a0bc1dade..bad897afe 100644
--- a/doc/reference.html
+++ b/doc/reference.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> Reference </titleinbody> </center>
     <p/>
     
diff --git a/doc/release-docs.html b/doc/release-docs.html
index 4a29c1c7f..0065f5c0c 100644
--- a/doc/release-docs.html
+++ b/doc/release-docs.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> Documents by release </titleinbody> </center>
     <p/>
     
diff --git a/doc/template.html b/doc/template.html
index 30b06317a..48a4cac16 100644
--- a/doc/template.html
+++ b/doc/template.html
@@ -68,7 +68,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> POKI_PUT_TITLE_HERE </titleinbody> </center>
     <p/>
     POKI_PUT_BODY_HERE
diff --git a/doc/to-do.html b/doc/to-do.html
index 79f9c6cb2..823b35cdd 100644
--- a/doc/to-do.html
+++ b/doc/to-do.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> Things to do </titleinbody> </center>
     <p/>
     
diff --git a/doc/whyc.html b/doc/whyc.html
index 7def55d60..70b183010 100644
--- a/doc/whyc.html
+++ b/doc/whyc.html
@@ -88,7 +88,46 @@ Miller commands were run with pretty-print-tabular output format.
 
   <!-- page body -->
   <td>
-    <div style="overflow-y:scroll;height:1500px">
+    <!--
+      This is a visually gorgeous feature (here & in the CSS): it allows for
+      independent scroll of the nav and body panels. In particular the nav
+      stays on-screen as you scroll the body.
+
+      However, two problems:
+
+      (1) In Firefox & Chrome both I get janky end-of-body scrolls: there is
+      more content but I can't scroll down to it unless I repeatedly retry the
+      scrolldown. Which is weird.
+
+      (2) Worse, only the first page renders in PDF (again, Firefox & Chrome).
+
+      For now I'm disabling this separate-scroll feature. A frontender, I am
+      not ... maybe someday I'll find a config which gets *all* the features
+      I want; for now, it's a tradeoff.
+    -->
+
+    <!-- Implementation details: one bit is right here:
+
+    div style="overflow-y:scroll;height:1500px"
+
+    and the other bit is in css/poki-callbacks.css:
+
+    .pokinav {
+      display:        inline-block;
+      background:     #e8d9bc;
+      border:         1;
+      box-shadow:     0px 0px 3px 3px #C9C9C9;
+      margin:         10px;
+      padding-top:    10px;
+      padding-bottom: 10px;
+      padding-left:   10px;
+      padding-right:  10px;
+      overflow-y:     scroll;  < - - - - - - here
+      height: 1500px;
+    }
+
+    -->
+    <div>
     <center> <titleinbody> Why C? </titleinbody> </center>
     <p/>