# Making Documentation to a top-level category?

**URL:** <https://discuss.python.org/t/making-documentation-to-a-top-level-category/13620>\
**Category:** Discourse Feedback\
**Created:** [February 9, 2022, 3:37pm UTC](https://discuss.python.org/t/making-documentation-to-a-top-level-category/13620 "2022-02-09T15:37:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![encukou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/encukou/32/2461_2.png) [@encukou](https://discuss.python.org/u/encukou)\
**Post date:** [February 9, 2022, 3:37pm UTC](https://discuss.python.org/t/making-documentation-to-a-top-level-category/13620/1 "2022-02-09T15:37:37Z")

</div>

Hi!  
On the [inaugural Docs WG meeting](https://github.com/python/docs-community/issues/15), it was noted that having the Documentation category nested in Core Development makes it hard to find and a bit alienating to people who’d like to contribute.  
Is there a reason for the nesting? Could the category be moved up?

---

<div class="post-metadata">

**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Post date:** [February 9, 2022, 8:27pm UTC](https://discuss.python.org/t/making-documentation-to-a-top-level-category/13620/2 "2022-02-09T20:27:44Z")

</div>

> [@encukou](#):
>
> Is there a reason for the nesting?

I vaguely remember it was requested to be added that way.

> [@encukou](#):
>
> Could the category be moved up?

The admin UI suggests it’s technically possible.