Bjørn Erik Pedersen e9c7b6205f Allow themes to define output formats, media types and params ... This allows a `config.toml` (or `yaml`, ´yml`, or `json`) in the theme to set: 1) `params` (but cannot override params in project. Will also get its own "namespace", i.e. `{{ .Site.Params.mytheme.my_param }}` will be the same as `{{ .Site.Params.my_param }}` providing that the main project does not define a param with that key. 2) `menu` -- but cannot redefine/add menus in the project. Must create its own menus with its own identifiers. 3) `languages` -- only `params` and `menu`. Same rules as above. 4) **new** `outputFormats` 5) **new** `mediaTypes` This should help with the "theme portability" issue and people having to copy and paste lots of setting into their projects. Fixes #4490		2018-03-21 09:22:19 +01:00
..
baseURL.go
baseURL_test.go
content.go
content_renderer.go
content_renderer_test.go
content_test.go
emoji.go
emoji_test.go
general.go	hugolib: Extract date and slug from filename	2018-03-11 18:26:18 +01:00
general_test.go
hugo.go	releaser: Prepare repository for 0.38-DEV	2018-03-07 17:58:48 +00:00
hugo_test.go	Properly handle -DEV suffix when comparing Hugo versions	2018-02-22 17:16:42 +01:00
language.go
language_test.go
path.go	Allow themes to define output formats, media types and params	2018-03-21 09:22:19 +01:00
path_test.go	Run gofmt -s with Go 1.10	2018-02-21 09:59:33 +01:00
pathspec.go
pathspec_test.go
processing_stats.go	Run gofmt -s with Go 1.10	2018-02-21 09:59:33 +01:00
pygments.go
pygments_test.go
testhelpers_test.go
url.go
url_test.go