New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hugo new theme fails #4450

Closed
bep opened this Issue Feb 25, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@bep
Member

bep commented Feb 25, 2018

▶ hugo new theme foo
Error: Unable to locate Config file. Perhaps you need to create a new site.
       Run `hugo help new` for details. (Config File "config" Not Found in "[/Users/bep/sites]")

@bep bep added the Bug label Feb 25, 2018

@bep bep added this to the v0.38 milestone Feb 25, 2018

@bep bep modified the milestones: v0.38, v0.39 Mar 20, 2018

@bep bep modified the milestones: v0.39, v0.40 Apr 9, 2018

@bep bep modified the milestones: v0.40, v0.41 Apr 20, 2018

@bep bep modified the milestones: v0.41, v0.42 May 4, 2018

@bep bep modified the milestones: v0.42, v0.43 Jun 5, 2018

bep added a commit to bep/hugo that referenced this issue Jun 10, 2018

bep added a commit to bep/hugo that referenced this issue Jun 10, 2018

bep added a commit to bep/hugo that referenced this issue Jun 10, 2018

bep added a commit to bep/hugo that referenced this issue Jun 10, 2018

bep added a commit to bep/hugo that referenced this issue Jun 10, 2018

bep added a commit to bep/hugo that referenced this issue Jun 10, 2018

bep added a commit to bep/hugo that referenced this issue Jun 10, 2018

Add support for theme composition and inheritance
This commit adds support for theme composition and inheritance in Hugo.

With this, it helps thinking about a theme as a set of ordered components:

```toml
theme = ["my-shortcodes", "base-theme", "hyde"]
```

The theme definition example above in `config.toml` creates a theme with the 3 components with presedence from left to right.

So, Hugo will, for any given file, data entry etc., look first in the project, and then in `my-shortcode`, `base-theme` and lastly `hyde`.

Hugo uses two different algorithms to merge the filesystems, depending on the file type:

* For `i18n` and `data` files, Hugo merges deeply using the translation id and data key inside the files.
* For `static`, `layouts` (templates) and `archetypes` files, these are merged on file level. So the left-most file will be chosen.

The name used in the `theme` definition above must match a folder in `/your-site/themes`, e.g. `/your-site/themes/my-shortcodes`. There are  plans to improve on this and get a URL scheme so this can be resolved automatically.

Also note that a component that is part of a theme can have its own configuration file, e.g. `config.toml`. There are currently some restrictions to what a theme component can configure:

* `params` (global and per language)
* `menu` (global and per language)
* `outputformats` and `mediatypes`

The same rules apply here: The left-most param/menu etc. with the same ID will win. There are some hidden and experimental namespace support in the above, which we will work to improve in the future, but theme authors are encouraged to create their own namespaces to avoid naming conflicts.

A final note: Themes/components can also have a `theme` definition in their `config.toml` and similar, which is the "inheritance" part of this commit's title. This is currently not supported by the Hugo theme site. We will have to wait for some "auto dependency" feature to be implemented for that to happen, but this can be a powerful feature if you want to create your own theme-variant based on others.

Fixes gohugoio#4460
Fixes gohugoio#4450

@bep bep closed this in #4467 Jun 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment