anchor.diff:    Routers can take advantage of this exception by composing in-application route
     URLs with hashes.  Here's a "hash URL" that routes to the *Crisis Center*
   
  -code-example(format=".", language="bash").
  +code-example(format="nocode").
     localhost:3002/src/#/crisis-center/
   
   :marked
  
positive.code: :marked
    Parse it out.
  
    * The first item in the array identifies the parent route ('/crisis-center').
    * There are no parameters for this parent route so you're done with it.
    * There is no default for the child route so you need to pick one.
    * You're navigating to the `CrisisListComponent`, whose route path is '/', but you don't need to explicitly add the slash
    * Voila! `['/crisis-center']`.
  
    Take it a step further.
    This time you'll build a link parameters array that navigates from the root of the application
    down to the "Dragon Crisis".
  
    * The first item in the array identifies the parent route ('/crisis-center').
    * There are no parameters for this parent route so you're done with it.
    * The second item identifies the child route for details about a particular crisis ('/:id').
    * The details child route requires an `id` route parameter
    * You added the `id` of the *Dragon Crisis* as the second item in the array (`1`)
  
    It looks like this!
  
  +makeExcerpt('app/app.component.3.ts', 'Dragon-anchor', '')
  
  :marked
    If you wanted to, you could redefine the `AppComponent` template with *Crisis Center* routes exclusively:
  
negative.code: 
    Those developers may still use HTML 5 URLs by taking two remedial steps:
  
    1. Provide the router with an appropriate [APP_BASE_HREF][] value.
    1. Use _root URLs_ for all web resources: css, images, scripts, and template html files.
  
    [APP_BASE_HREF]: ../api/common/index/APP_BASE_HREF-let.html
  
  :marked
    ### *HashLocationStrategy*
  