content updates

doc_shuffle.html

@@ -6,7 +6,14 @@ keywords:
 summary:
 ---
 {% include linkrefs.html %}
-{% unless site.print == false %}
+
+This layout shows an example of a knowledge-base style navigation system, where there is no hierarchy, just groups of pages that have certain tags.
+
+{% if site.print == true %}
+{{note}} The content on this page doesn't display well on PDF, but I included it anyway so you could see the problems this layout poses if you're including it in PDF.  {{end}}
+{% endif %}
+
+{% unless site.print == true %}
 <script src="js/jquery.shuffle.min.js"></script>
 <script src="js/jquery.ba-throttle-debounce.min.js"></script>
 {% endunless %}
@@ -96,13 +103,15 @@ summary:
 <div class="panel panel-primary">
                <div class="panel-heading">Publishing</div>
                <div class="panel-body">
+                   <ul>
                 {% for page in site.pages %}
                 {% for tag in page.tags %}
                 {% if tag == "publishing" %}
                   <li><a href="{{page.url}}">{{page.title}}</a></li>
                 {% endif %}
                 {% endfor %}
-                {% endfor %} 
+                {% endfor %}
+                   </ul>
                </div>
             </div>
 
@@ -133,7 +142,10 @@ summary:
 
     </div><!-- /#grid -->
 
+{% unless site.print == true %}
 {% include initialize_shuffle.html %}
-
+{% endunless %}
+
+{{note}} This was mostly an experiment to see if there was a better way to document a long JSON code example. I haven't actually used this approach in my own documentation.{{end}}