By default, Hugo searches for Markdown files in the `content` directory, and the structure of the directory determines the final output structure of your website.
Take the example site as an example:
{{<filetree/container>}}
{{<filetree/foldername="content">}}
{{<filetree/filename="_index.md">}}
{{<filetree/foldername="docs"state="open">}}
{{<filetree/filename="_index.md">}}
{{<filetree/filename="getting-started.md">}}
{{<filetree/foldername="guide"state="open">}}
{{<filetree/filename="_index.md">}}
{{<filetree/filename="organize-files.md">}}
{{< /filetree/folder >}}
{{< /filetree/folder >}}
{{<filetree/foldername="blog"state="open">}}
{{<filetree/filename="_index.md">}}
{{<filetree/filename="post-1.md">}}
{{< /filetree/folder >}}
{{< /filetree/folder >}}
{{< /filetree/container >}}
Each of the `_index.md` files is the index page for the corresponding section. The other Markdown files are regular pages.
The sidebar navigation is generated automatically based on the content organization alphabetically. To manually configure the sidebar order, we can use the `weight` parameter in the front matter of the Markdown files.
```yaml {filename="content/docs/guide/_index.md"}
---
title: Guide
weight: 2
---
```
{{<calloutemoji="ℹ️">}}
It is recommended to keep the sidebar not too deep. If you have a lot of content, consider **splitting them into multiple sections**.
{{</callout>}}
## Configure Content Directory
If we need to use a different directory for our content, we can do so by setting the [`contentDir`](https://gohugo.io/getting-started/configuration/#contentdir) parameter in our site configuration file.