control over theming via config

[DimitarChristoff]

Proposed change that will allow greater theming options.

.documentup.json

{
    "header": "docs/header.html",
    "footer": "docs/footer.html"
}

when supplied, use the files to produce the document.head and a superfluous code block before the end of the body tag of the document, overriding everything normally dispatched from the server.

an alternative syntax would be like this:

{ 
    "env": {
        "stylesheets": ["style1.css", "http://somedomain.com/style2.css"],
        "javascript": [
            "https://ajax.googleapis.com/ajax/libs/mootools/1.4.5/mootools-yui-compressed.js", 
            "js/docsDependencies.js", 
            "js/docs.js"
        ]
    }
}

used through iteration of env keys and injection in the head or bottom of the document.

Either way, it means you don't need to support themes and do ones that people don't like or want to change - a few out of the box will do and for everyone else, control methods will be supplied that can give whatever control is needed.

[jeromegn]

I like that.

At first I preferred option #1, but I think option #2 is simpler.

[jeromegn]

At the moment, the only option is to supply a theme (SCSS) in the correct directory (app/assets/stylesheets/themes/) and use the theme option in the config.

Theming is a complicated beast. I might tackle it.