docs: Clarify usage of archetypes provided by themes - hugo - [fork] hugo port for 9front
(HTM) git clone git@git.drkhsh.at/hugo.git
(DIR) Log
(DIR) Files
(DIR) Refs
(DIR) Submodules
(DIR) README
(DIR) LICENSE
---
(DIR) commit c7f67dd63c60ef88cd76d8497abff864690919ed
(DIR) parent b4404a955438b67c226dddfe9102456e44c50d3e
(HTM) Author: Eugene Brodsky <ebr@users.noreply.github.com>
Date: Sat, 10 Dec 2016 01:59:42 -0500
docs: Clarify usage of archetypes provided by themes
Diffstat:
M docs/content/content/archetypes.md | 2 ++
1 file changed, 2 insertions(+), 0 deletions(-)
---
(DIR) diff --git a/docs/content/content/archetypes.md b/docs/content/content/archetypes.md
@@ -146,3 +146,5 @@ file name) and the `date` in RFC 3339 format based on
The content type is automatically detected based on the file path passed to the
Hugo CLI command <code>hugo new <em>[my-content-type/post-name]</em></code>. To
override the content type for a new post, include the `--kind` flag during creation.
+
+> *Note: if you wish to use archetypes that ship with a theme, the theme MUST be specified in your `config.toml`.*