From 58654c1068d5ea6e19d67aa57a8f9ce7ed131011 Mon Sep 17 00:00:00 2001 From: Joe Mooring Date: Sat, 1 Nov 2025 12:19:07 -0700 Subject: [PATCH] content: Fix archetype lookup order Closes #3240 Co-authored-by: Sardorbek Imomaliev <3041675+imomaliev@users.noreply.github.com> Co-authored-by: Michael Henderson --- content/en/content-management/archetypes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/content-management/archetypes.md b/content/en/content-management/archetypes.md index db0838504..5f7d1ece4 100644 --- a/content/en/content-management/archetypes.md +++ b/content/en/content-management/archetypes.md @@ -44,7 +44,7 @@ archetypes/ Hugo looks for archetypes in the `archetypes` directory in the root of your project, falling back to the `archetypes` directory in themes or installed modules. An archetype for a specific content type takes precedence over the default archetype. -For example, with this command: +For example, if you have enabled a theme named `my-theme` and you run this command: ```sh hugo new content posts/my-first-post.md @@ -53,8 +53,8 @@ hugo new content posts/my-first-post.md The archetype lookup order is: 1. `archetypes/posts.md` -1. `archetypes/default.md` 1. `themes/my-theme/archetypes/posts.md` +1. `archetypes/default.md` 1. `themes/my-theme/archetypes/default.md` If none of these exists, Hugo uses a built-in default archetype.