Update template.md

Author: samselikoff

tests/dummy/app/pods/docs/patterns/template.md

@@ -2,16 +2,7 @@
 
 Here's a summary of the patterns we encourage addon authors to follow when documenting their work.
 
-{{! FIXME these links don't work  with the 'hash' locationType}}
-- [Document your addon using its dummy app](#document-your-addon-using-its-dummy-app)
-- [Author in Markdown](#author-in-markdown)
-- [Design for your audience](#design-for-your-audience)
-- [Write versioned guides](#write-versioned-guides)
-- [Write versioned API references](#write-versioned-api-references)
-- [Deploy your dummy app to GitHub Pages](#deploy-your-dummy-app-to-github-pages)
-- [Miscellaneous](#miscellaneous)
-
-## Document your addon using its dummy app
+## Using your dummy app as your docs site
 
 One of the more surprising results to come out of the addon community is the effectiveness of using an addon's dummy application as a full-fledged document site.
 
@@ -25,7 +16,7 @@ Every addon comes with a fully bootstrapped Ember application that can be found
 
   Once you document the new behavior on your doc site, you can now write an acceptance test against it, ensuring (1) that your code is functioning correctly, and (2) that your docs are accurate and up-to-date. Win-win!
 
-## Author in Markdown
+## Authoring in Markdown
 
 Authoring your docs pages in Markdown makes it easy for you and your contributors to read and edit your site.
 
@@ -65,19 +56,19 @@ The large main area is also useful for addons that need more space to illustrate
 
 Typography choices were made primarily for readability. Measure, a typographic term for the number of characters is a line of text, is also an important aspect of readability, so by default most of the layouts you see will be wrapped with an appropriate max-width. To reiterate one of our main goals for the project, we want addon authors to get these patterns for free so they can focus on actually documenting and testing their addons.
 
-## Write versioned guides
+## Versioning your docs
 
-Write this...
+Addon Docs provides versioned guides out of the box. You can see the version selector in the top-right part of this page. This is provided by the `<docs-header>` component, so your site will get this too assuming you use this component.
 
-## Write versioned API references
+If you look at the [`gh-pages`](https://github.com/ember-learn/ember-cli-addon-docs/tree/gh-pages) branch you'll see that this is where versioned builds of your docs app are stored. Versions are created at deploy time and Addon Docs manages this branch of your repository for you.
 
-Autogenerated for you as a route on `DocsViewer.nav`.
+New versions are created when a new tag is released. There is also a `master` version updated on every deployed commit, and a `Latest` alias that points to the most recent tag, unless it is force-updated to point to `master`.
 
-Write this...
+See the next section on {{docs-link 'deploy guides' 'docs.deploying'}} for more information about deploys.
 
-## Deploy your dummy app to GitHub Pages
+## Hosting on GitHub Pages
 
-We suggest deploying your dummy app to GitHub Pages, as it's a simple place available to every GitHub project to host your documentation site. Once you have this set up, you can even automate deployment as part of your Travis CI builds.
+Addon Docs is built for open-source addons deploying their docs sites to GitHub Pages. Once you have this set up, you can even automate deployment as part of your Travis CI builds.
 
 For more details, see the {{docs-link 'Deploying' 'docs.deploying'}} section of the guides.