organization section now nonfiction; misc small edits

Author: kwalrath

public/_includes/_util-fns.jade

@@ -2,7 +2,7 @@
 
 //- _docsFor: used to identify the language this version of the docs if for;
 //- Should be one of: 'ts', 'dart' or 'js'. Set in lang specific _util-fns file.
-- var _docsFor = ''; 
+- var _docsFor = '';
 
 //- Should match `_docsFor`, but in this case provides the full capitalized
 //- name of the language.
@@ -29,6 +29,10 @@
 - var _Promise = 'Promise';
 - var _Observable = 'Observable';
 
+//- Location of sample code
+- var _liveLink = 'live link';
+
+
 //- Used to prefix identifiers that are private. In Dart this will be '_'.
 - var _priv = '';
 
@@ -46,7 +50,7 @@ mixin adjExPath(path)
     | #{adjustExamplePath(path)}
   else
     | #{path}
-  
+
 mixin includeShared(filePath, region)
   - var newPath = translatePath(filePath, region);
   !=partial(newPath)
@@ -69,8 +73,8 @@ mixin makeExample(_filePath, region, _title, stylePatterns)
   code-example(language="#{language}" format="#{format}")
     != styleString(frag, stylePatterns)
 
-//- Like makeExample, but the first argument is a path that is 
-//- relative to the project root. Unless title is defined, 
+//- Like makeExample, but the first argument is a path that is
+//- relative to the project root. Unless title is defined,
 //- the project relative path will be used.
 mixin makeProjExample(projRootRelativePath, region, title, stylePatterns)
   - var relPath = projRootRelativePath.trim();
@@ -83,7 +87,7 @@ mixin makeProjExample(projRootRelativePath, region, title, stylePatterns)
   +makeExample(filePath, region, title, stylePatterns)
 
 //- Like makeExample, but doesn't show line numbers, and the first
-//- argument is a path that is relative to the example project root. 
+//- argument is a path that is relative to the example project root.
 //- Unless title is defined, the project relative path will be used.
 //- Title will always end with a phrase in parentheses; if no such
 //- ending is given, then the title will be suffixed with
@@ -164,7 +168,7 @@ script.
     el.style.display = isVerbose ? 'block' : 'none';
     var el = document.querySelector('button.verbose.on');
     el.style.display = isVerbose ? 'none' : 'block';
-    
+
     CCSStylesheetRuleStyle('main','.l-verbose-section', 'display',
       isVerbose ? 'block' : 'none');
   }

public/docs/dart/latest/_util-fns.jade

@@ -11,13 +11,14 @@ include ../../../_includes/_util-fns
 - var _Lang = 'Dart';
 - var _Promise = 'Future';
 - var _Observable = 'Stream';
+- var _liveLink = 'sample repo';
 
 mixin liveExampleLink(linkText, exampleUrlPartName)
   a(href='https://angular-examples.github.io/#{exampleUrlPartName}' target="_blank")= linkText
 
 mixin liveExampleLink2(linkText, exampleUrlPartName)
   - var liveExampleSourceLinkText = attributes.srcLinkText || 'view source'
-  | #[+liveExampleLink(linkText, exampleUrlPartName)] 
+  | #[+liveExampleLink(linkText, exampleUrlPartName)]
   | (#[a(href='https://github.com/angular-examples/#{exampleUrlPartName}' target="_blank") #{liveExampleSourceLinkText}])
 
 - var adjustExamplePath = function(_path) {
@@ -29,7 +30,7 @@ mixin liveExampleLink2(linkText, exampleUrlPartName)
 -   var baseName = getBaseFileName(path) || path; // TODO: have getBaseFileName() return path
 -   var baseNameNoExt = baseName.substr(0,baseName.length - (extn.length + 1));
 -   var inWebFolder = baseNameNoExt.match(/^(main|index(\.\d)?)$/);
--   // Adjust the folder path, e.g., ts -> dart 
+-   // Adjust the folder path, e.g., ts -> dart
 -   folder = folder.replace(/(^|\/)ts($|\/)/, '$1dart$2').replace(/(^|\/)app($|\/)/, inWebFolder ? '$1web$2' : '$1lib$2');
 -   // Special case not handled above: e.g., index.html -> web/index.html
 -   if(baseNameNoExt.match(/^(index|styles)(\.\d)?$/)) folder = (folder ? folder + '/' : '') + 'web';

public/docs/dart/latest/guide/index.jade

@@ -11,8 +11,3 @@ block example-links
     for the [Architecture](architecture.html) chapter's sample.
     A running version of that sample is at
     https://angular-examples.github.io/architecture/.
-
-    A few early chapters are written as tutorials and are clearly marked as such.
-    Most chapters are *not* tutorials.
-    They highlight key points in code rather than explain each step necessary to build the sample.
-    We can still get the full source from the sample repo.

public/docs/ts/latest/guide/index.jade

@@ -27,14 +27,16 @@ figure
 table(width="100%")
   col(width="15%")
   col
+  tr(style=top)
+    td <b>QuickStart</b>
+    td
+      :marked
+        The foundation for every chapter and sample in this documentation.
   tr(style=top)
     td <b>Tutorial</b>
     td
       :marked
-        A step-by-step, immersive approach to learning Angular.
-        It begins with the [QuickStart](../quickstart.html),
-        the foundation for every chapter and sample in this documentation,
-        followed by the [*Tour of Heroes* tutorial](../tutorial) that
+        A step-by-step, immersive approach to learning Angular that
         introduces the major features of Angular in an application context.
   tr(style=top)
     td <b>Basics</b>
@@ -52,16 +54,10 @@ table(width="100%")
       :marked
         Recipes for specific application challenges, mostly code snippets with a minimum of exposition.
   tr(style=top)
-    td <b>Reference</b>
+    td <b>API Reference</b>
     td
       :marked
-        Angular-specific reference material, most notably the [API Guide](../api)
-        with its authoritative details about each member in the Angular libraries.
-  tr(style=top)
-    td <b>Resources</b>
-    td
-      :marked
-        Other places to go for help and information.
+        Authoritative details about each member of the Angular libraries.
 :marked
   # Learning path
   We don't have to read the guide straight through.  Most chapters stand on their own.
@@ -108,18 +104,19 @@ block example-links
 
     The link launches a browser-based code editor where we can inspect, modify, save, and download the code.
 
-    A few early chapters are written as tutorials and are clearly marked as such.
-    Most chapters are *not* tutorials.
-    They highlight key points in code rather than explain each step necessary to build the sample.
-    We can always get the full source by way of the live link.
+:marked
+  A few early chapters are written as tutorials and are clearly marked as such.
+  Most chapters are *not* tutorials.
+  They highlight key points in code rather than explain each step necessary to build the sample.
+  We can always get the full source by way of the #{_liveLink}.
 
-  ## References
+  # Reference pages
 
   The [Cheat Sheet](cheatsheet.html) lists Angular syntax for common scenarios.
 
   The [Glossary](glossary.html) defines terms that Angular developers should know.
 
-  The [API Guide](../api/) is the authority on every public-facing member of the Angular libraries.
+  The [API Reference](../api/) is the authority on every public-facing member of the Angular libraries.
 
   # Feedback