Hugo believes that you organize your content with a purpose. The same structure that works to organize your source content is used to organize the rendered site (see directory structure).
Following this pattern, Hugo uses the top level of your content organization as the content section.
The following example shows a content directory structure for a website that has three sections: “authors,” “events,” and “posts”:
. └── content ├── authors | ├── _index.md // <- example.com/authors/ | ├── john-doe.md // <- example.com/authors/john-doe/ | └── jane-doe.md // <- example.com/authors/jane-doe/ └── events | ├── _index.md // <- example.com/events/ | ├── event-1.md // <- example.com/events/event-1/ | ├── event-2.md // <- example.com/events/event-2/ | └── event-3.md // <- example.com/events/event-3/ └── posts | ├── _index.md // <- example.com/posts/ | ├── post-1.md // <- example.com/posts/post-1/ | ├── post-2.md // <- example.com/posts/post-2/ | ├── post-3.md // <- example.com/posts/post-3/ | ├── post-4.md // <- example.com/posts/post-4/ | └── post-5.md // <- example.com/posts/post-5/
Content Section Lists
Hugo will automatically create pages for each section root that list all of the content in that section. See the documentation on section templates for details on customizing the way these pages are rendered.
As of Hugo v0.18, section pages can also have a content file and front matter. These section content files must be placed in their corresponding section folder and named
_index.md in order for Hugo to correctly render the front matter and content.
Content Section vs Content Type
By default, everything created within a section will use the content type that matches the section name. For example, Hugo will assume that
posts/post-1.md has a
posts content type. If you are using an archetype for your posts section, Hugo will generate front matter according to what it finds in