Bug with defaultDest

[marshallswain]

"home" override in the docConfig

To make publishing setup easier (when a separate home page isn't wanted), it would be nice to have a "home" config option to specify a site from the master branch's documentjs.json that we want to be promoted to the home page. This would basically override it to publish to "dest" : "." The example configs below would publish the "docs" site into the root folder of the gh-pages branch.

In master:

{
    "sites": {
        "docs": {
            "parent": "DocumentJS",
            "pageConfig": {"page":"docs"},
            "glob": {
                "pattern": "{docs,tags,lib,tasks}/**/*.{js,md}",
                "ignore": "lib/{configured,process,generate,find,generators/html}/test/**/*"
            }
        }
    }
}

In gh-pages:

{
    "versions": {
        "1.0": "git://github.com/marshallswain/can-stache-moment#master"
    },
    "defaultVersion": "1.0",
    "home":"docs"
}```

[marshallswain]

@jandjorgensen pointed out defaultDest here. Putting it in the gh-pages config caused the output to build into the project's parent folder (eg. running this inside the Sites/can-stache-moment folder built the docs into the Sites folder). I only put `"defaultDest" : "./" in the config.