[GH-ISSUE #8297] [FR] P0 ! ! Dockable Document Outline (Table of Contents) Panel #3708

New issue

Open

opened 2026-03-23 21:32:36 +00:00 by mirror · 0 comments

mirror commented

2026-03-23 21:32:36 +00:00

Owner

Originally created by @1439522180 on GitHub (Oct 15, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8297

Description

This is a suggestion to introduce a document outline (or table of contents) panel that can be toggled on/off and docked to either the left or right side of the main editing area. This panel should display the hierarchical structure of headings (H1, H2, H3...) from the current article in real-time. Users should be able to pin this panel to the left or right, set it to a floating mode, or hide it completely. As the user scrolls the article, the outline panel should highlight the current section. Clicking any title in the outline should instantly jump to the corresponding part of the article.

Primary Use Cases:

Long-form Writing and Editing: When users are writing or reviewing long reports, technical documentation, or project plans, the persistent outline provides an overview of the entire structure and allows for quick navigation between sections, significantly improving writing and editing efficiency.

Knowledge Base Reading and Navigation: When team members browse complex documents in a company knowledge base, the outline on the side allows them to quickly grasp the document's structure and jump directly to sections of interest, much like using a book's table of contents.

Impact

Content Creators and Writers: Users who work with long-form content, such as bloggers, journalists, novelists, and technical writers.

Researchers and Students: Users who frequently need to read long academic papers and materials, and who write their own research papers.

Knowledge Managers and Teams: Teams that build, maintain, and read structured knowledge bases, such as product managers, developers, and operations personnel.

All Efficiency-Focused Users: Any user who works with long, structured documents would benefit from the time saved by avoiding excessive scrolling and searching.

Additional Context

No response

Originally created by @1439522180 on GitHub (Oct 15, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8297 ### Description This is a suggestion to introduce a document outline (or table of contents) panel that can be toggled on/off and docked to either the left or right side of the main editing area. This panel should display the hierarchical structure of headings (H1, H2, H3...) from the current article in real-time. Users should be able to pin this panel to the left or right, set it to a floating mode, or hide it completely. As the user scrolls the article, the outline panel should highlight the current section. Clicking any title in the outline should instantly jump to the corresponding part of the article. Primary Use Cases: Long-form Writing and Editing: When users are writing or reviewing long reports, technical documentation, or project plans, the persistent outline provides an overview of the entire structure and allows for quick navigation between sections, significantly improving writing and editing efficiency. Knowledge Base Reading and Navigation: When team members browse complex documents in a company knowledge base, the outline on the side allows them to quickly grasp the document's structure and jump directly to sections of interest, much like using a book's table of contents. ### Impact Content Creators and Writers: Users who work with long-form content, such as bloggers, journalists, novelists, and technical writers. Researchers and Students: Users who frequently need to read long academic papers and materials, and who write their own research papers. Knowledge Managers and Teams: Teams that build, maintain, and read structured knowledge bases, such as product managers, developers, and operations personnel. All Efficiency-Focused Users: Any user who works with long, structured documents would benefit from the time saved by avoiding excessive scrolling and searching. ### Additional Context _No response_