# Better support for content editors to create a structured document

**URL:** <https://community.fibery.io/t/better-support-for-content-editors-to-create-a-structured-document/3573>\
**Category:** Ideas & Features\
**Created:** [November 21, 2022, 6:49am UTC](https://community.fibery.io/t/better-support-for-content-editors-to-create-a-structured-document/3573 "2022-11-21T06:49:03Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [November 21, 2022, 5:53pm UTC](https://community.fibery.io/t/better-support-for-content-editors-to-create-a-structured-document/3573/4 "2022-11-21T17:53:41Z")

</div>

Hmm, I agree that it can be hard to be sure what Header level one is seeing/using (sometimes I quickly try applying a level to my current header to see if it changes as a form of diagnoses/identification 😄). I think the issue of navigability for readers is also important, but separate.

> [@\[DONE\] Table of Contents block or other function](https://community.fibery.io/t/table-of-contents-block-or-other-function/2235):
>
> I was surprised to not find an existing feature request for this one, but I did search a bit and only found brief mentions in otherwise unrelated discussions. So the request is simple: some kind of Table of Contents feature, for docs, certainly, but perhaps even just overall for Rich Text. Maybe even as a kind of Block in the upcoming [[IN DEV] Migrate Entity View to Blocks](https://community.fibery.io/t/in-dev-migrate-entity-view-to-blocks/2005) paradigm. Personally, though, I’d love to see it as something that can optionally “float” or exist outside/alongside the ma…

You have titled this Feature Request rather broadly, and within it I only really identify the one general request: make it more clear what Headers users are Applying, and which level their current text is at. If that is the extent of the feature request, can I suggest changing the Title to more clearly reflect that? If there is more that needs to be done for “creating a structured document”, let’s elaborate further. 🙂

As to the specific request to make Headers more clearly identified, both for authors and readers, I think your suggestion of putting the e.g. H1, H2, etc. next to the text is good, except I’d say it should only show _on-hover_/mouseover, just as Collapse and Anchor Link already do. To me this would completely solve the ambiguity issue in a very simple, clean way.

For _readers_ (and, to some degree, editors) to better understand where they are within text as they read, e.g. say you’ve scrolled past the H2 that identifies the section you’re in, so you can’t easily mouseover it to know where you are in hierarchy, I think the best solution is a floating Table of Contents (which I describe in my feature request above). An alternative could be to have some “level” indicator in e.g. the left margin/gutter, outside of the text, which just shows a little number or maybe e.g. “H2”, but it starts to make things look busy I think. It could perhaps only show if you move your cursor outside the text, or maybe if you hold Alt as-in my more broad “Modal block vs. text editing” concept described here (which is to say only the concept of holding a modifier key to invoke additional info/context, so this is partly just an excuse to link my write-up 😄):  
[https://garden.oshyan.com/t/a-proposal-to-enhance-usability-of-block-based-tools-for-writing-and-layout/56](https://garden.oshyan.com/t/a-proposal-to-enhance-usability-of-block-based-tools-for-writing-and-layout/56)

---

_[View the full topic](https://community.fibery.io/t/better-support-for-content-editors-to-create-a-structured-document/3573)._