# Nested sections without \_index.md

**URL:** <https://discourse.gohugo.io/t/nested-sections-without-index-md/14166>\
**Category:** feature\
**Created:** [September 11, 2018, 5:03pm UTC](https://discourse.gohugo.io/t/nested-sections-without-index-md/14166 "2018-09-11T17:03:40Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![alexandros](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@alexandros](https://discourse.gohugo.io/u/alexandros)\
**Post date:** [September 11, 2018, 8:06pm UTC](https://discourse.gohugo.io/t/nested-sections-without-index-md/14166/8 "2018-09-11T20:06:30Z")

</div>

> [@b\_rad](#):
>
> In terms of portability, I just don’t understand why you’d need that file. Many times you’re simply adding it so that your subsections work, when the first sections work as expected.

Are you asking me about the rationale of Development decisions that were made after a process that took months?

Well… Here you go (it’s a bit of a long read):

> [@Feedback wanted: Nested sections: Content structure](https://discourse.gohugo.io/t/feedback-wanted-nested-sections-content-structure/6692/12):
>
> How is it limiting? How is it more intuitive to put a metadata.toml file with some configuration variables in it? Both need documentation, the “\_” is, I would say, easier to document than the TOML file. Not?

---

_[View the full topic](https://discourse.gohugo.io/t/nested-sections-without-index-md/14166)._