In Hugo, your content should be organized in a manner that reflects the rendered website.
While Hugo supports content nested at any level, the top levels (i.e. content/<DIRECTORIES>) are special in Hugo and are considered the content type used to determine layouts etc. To read more about sections, including how to nest them, see sections.
Without any additional configuration, the following will automatically work:
The following demonstrates the relationships between your content organization and the output URL structure for your Hugo website when it renders. These examples assume you are using pretty URLs, which is the default behavior for Hugo. The examples also assume a key-value of baseURL = "https://example.org" in your site’s configuration file.
You can create one _index.md for your homepage and one in each of your content sections, taxonomies, and taxonomy terms. The following shows typical placement of an _index.md that would contain content and front matter for a posts section list page on a Hugo website:
The sections can be nested as deeply as you want. The important thing to understand is that to make the section tree fully navigational, at least the lower-most section must include a content file. (i.e. _index.md).
Single pages in sections
Single content files in each of your sections will be rendered as single page templates. Here is an example of a single post within posts:
The following concepts provide more insight into the relationship between your project’s organization and the default Hugo behavior when building output for the website.
A default content type is determined by the section in which a content item is stored. section is determined by the location within the project’s content directory. sectioncannot be specified or overridden in front matter.
The slug is the last segment of the URL path, defined by the file name and optionally overridden by a slug value in front matter. See URL Management for details.
A content’s path is determined by the section’s path to the file. The file path
is based on the path to the content’s location AND
does not include the slug
The url is the entire URL path, defined by the file path and optionally overridden by a url value in front matter. See URL Management for details.