Expand the section on features a bit.

It's not exactly clear from the documentation (or the book) that
features can be used to defer resource evaluation, something that can be
extremely useful for certain providers.
Break down PE and Communtiy versions of PuppetDB

This changes the index for PuppetDB to differentiate between community and PE
versions for our older documentation. This avoids confusion that I've received
where we are stating for example 1.6.x community is marked as stable, but in
reality this is only true for PE packages.

This also starts us on the road for making PE more of a first class citizen
in the rest of our documentation.

Signed-off-by: Ken Barber <ken@bob.sh>
Merge pull request #324 from kbarber/maint/master/pdb-change-statement-about-stable

Break down PE and Community versions of PuppetDB
Merge pull request #317 from daenney/povider-feature-example

Expand the section on features a bit.
Layouts: Move quick-nav to sidebar in frontpage layout
Layouts: Kick promo images out into an include file
Add home page to quick nav

I don't know why this wasn't there before.
Adjust spacing on promos and add a HR to separate them from nav content
(MKOPS-512) Promos: Add PuppetConf 2014 promo
(DOC-869) Mco can't filter by environment in PE

Since the fact file is populated by a script that runs facter instead of a
Puppet file resource that can access the full Puppet scope, mco on PE can't
filter by environment. This commit removes misleading examples from the
relevant orchestration page.
(PUP-2365) Fix instructions for adding geotrust CA on windows

This was wrong; running Windows Update isn't actually sufficient, and you need
to actually visit the Forge with a web browser.
Remove quantal quetzal from platforms list

This OS is EOL, so we're removing it from the puppetlabs repos.
Remove Debian "Sid" (aka unstable) from docs

We are no longer building packages for sid/unstable. This is because
these package builds will often fail, and block successful build for
other platforms that we support. Additionally, this OS target is of
questionable value, given we already build against Debian testing.
Merge pull request #339 from melissaanne/master

Remove Debian "Sid" (aka unstable) from docs
Removed a bad comma
Update PDF targets

New approach this time: I'm ignoring all potential updates to existing versions
of these documents, and instead just making fresh PDFs for new versions.

NOTE: In case I go looking here next time: the two pages that caused the puppet
3.6 reference to corrupt were config_ssl_external_ca.html and the type reference.
Facter 2.1.0 release notes
Update version number in facter doc
(DOC-891) some corrections to back up and restore from support
Problem:

The documentation uses `/etc/puppet/hieradata/` in some places and
`/etc/puppet/hiera/` in others. We must choose one or the other.

As a result, many of the examples on this page do not work. To test,
simply run through the examples in order and note that hiera is unable
to find anything including the keys in common.yaml:

```
[root@puppet3 puppet]# cat hiera.yaml

---
:backends:
  - yaml
:yaml:
  :datadir: /etc/puppet/hieradata
:hierarchy:
  - "nodes/%{::fqdn}"
  - "virtual/%{::virtual}"
  - "osfamily/%{osfamily}"
  - common
[root@puppet3 puppet]# ls hiera
common.yaml  nodes  osfamily  virtual
[root@puppet3 puppet]# head hiera/common.yaml
vmwaretools::version: 8.6.5-621624
[root@puppet3 puppet]# service puppetmaster restart
Stopping puppetmaster:                                     [  OK  ]
Starting puppetmaster:                                     [  OK  ]
[root@puppet3 puppet]# hiera vmwaretools::version
nil
[root@puppet3 puppet]#
```

Solution:

Standardize on `/etc/puppet/hieradata/`, since that seems to be the most
common path in the other PuppetDocs documentation. Replace
`/etc/puppet/hiera/` with `/etc/puppet/hieradata`.