From ced5292c8d9634643cfeee3b171e90007b3ff4df Mon Sep 17 00:00:00 2001 From: zemzelett Date: Sun, 7 May 2023 17:16:17 +0200 Subject: [PATCH] Align permalinks examples (#2073) --- content/en/content-management/urls.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/content/en/content-management/urls.md b/content/en/content-management/urls.md index ebfd84690..c65d6c15a 100644 --- a/content/en/content-management/urls.md +++ b/content/en/content-management/urls.md @@ -111,7 +111,8 @@ content/ Create a date-based hierarchy, recursively, for regular pages within the `posts` section: {{< code-toggle file="config" copy=false >}} -posts = '/posts/:year/:month/:title/' +[permalinks] + posts = '/posts/:year/:month/:title/' {{< /code-toggle >}} The structure of the published site will be: @@ -133,7 +134,8 @@ public/ To create a date-based hierarchy for regular pages in the content root: {{< code-toggle file="config" copy=false >}} -'/' = '/:year/:month/:title/' +[permalinks] + '/' = '/:year/:month/:title/' {{< /code-toggle >}} {{% note %}} @@ -143,7 +145,8 @@ A URL pattern defined for the content root is not recursive. Use the same approach with taxonomies. For example, to omit the taxonomy segment of the URL: {{< code-toggle file="config" copy=false >}} -'tags' = '/:title/' +[permalinks] + 'tags' = '/:title/' {{< /code-toggle >}} Front matter `url` values take precedence over URL patterns defined in `permalinks`.