mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 12:56:59 +00:00
[GH-ISSUE #4282] [FR] Outline for subpages #1911
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#1911
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PeterHero on GitHub (Jan 2, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4282
Description
Outline for page can be created using
/outline. It uses headlines.The same functionality should be for creating the outline for sub pages. It would allow easy navigation in nested documents structure.
It could look like this:


Impact
Easy navigation through sub documents.
I like to have a nested structure of smaller documents. This would enable to have the top document as a overview of the structure. One could easily navigate to the specific document.
Additional Context
I don't have a good idea for the keyword when using '/'.
Maybe 'structure', 'overview'? Any suggestions?
@LucasXu0 commented on GitHub (Jan 2, 2024):
How about the 'hierarchy' or 'directory'?
@Jayaprakash-dev commented on GitHub (Jan 7, 2024):
Hey @LucasXu0 @annieappflowy,
I would like to work on this issue!
@LucasXu0 commented on GitHub (Jan 8, 2024):
Hey, @Jayaprakash-dev. Do you already have any idea on how to implement it? If so, please share it here.
@PeterHero commented on GitHub (Jan 8, 2024):
It could be useful to change the depth of the outline. Could that be please added as a functionality?
@Jayaprakash-dev commented on GitHub (Jan 8, 2024):
Hey @LucasXu0, I haven't fully figured out the optimal solution yet; currently, I'm surfing through the code base. Sure, I'll reach out to you once I've found a solution for it.
@Jayaprakash-dev commented on GitHub (Jan 8, 2024):
Hey @PeterHero, Could you please provide more details? Currently, the
/outlinecommand outputs all headings, including subheadings up to level 3. Are you suggesting it should only display headings at a certain depth, such as only top-level headings or outputs up to subheadings levels 1 or 2? Your clarification on this would be super helpful.@PeterHero commented on GitHub (Jan 8, 2024):
The comment was connected to this issue. I meant the depth of the outline for subpages. There could be a selection next to the '/hierarchy' (or what it'd be called) where you could select the depth as a number. Hierarchy would be generated only to this depth.
Usecase: it is useful to create overview of subpages but not contain all of them because then it would become bloated and not clear.
@Jayaprakash-dev But yes, it could be applied to
/outlineas well.@Jayaprakash-dev commented on GitHub (Jan 10, 2024):
Hey @LucasXu0 & @PeterHero,
I've successfully implemented the feature that controls the depth of the
OutlineBlockComponentblock. Now, when a depth H1 is selected, the app displays headings up to level 1, and similarly for H2, it shows headings up to level 2, extending to subsequent H3 headings.As of now, the app only supports options up to Heading 3, and that's why I limited this feature to H3 Heading.
However, I'm facing a challenge in generating
Localkeysfor lang translation in this implementation. If you have any guidance or suggestions on how to proceed, it would be helpful. If necessary, I can share the relevant code snippet here for your review.Looking forward to your response and guidance on this matter.
https://github.com/AppFlowy-IO/AppFlowy/assets/68953739/63f0ea8e-c4f8-413d-9db8-e9cf2e57f4cc
https://github.com/AppFlowy-IO/AppFlowy/assets/68953739/e9d66143-ce55-4e05-b76f-34e9decb1c78
I understand the issue involves creating an outline-like structure for the pages. However, when @PeterHero commented about the possibility of implementing depth control for the
Outline, I thought it would be relatively easier to implement.@PeterHero commented on GitHub (Jan 10, 2024):
@Jayaprakash-dev, I created a new issue where this feature could be tracked. It is better to have separate issues for separate features.
@Jayaprakash-dev commented on GitHub (Jan 19, 2024):
Hey @LucasXu0,
I've successfully implemented the feature and submitted a pull request. Now, users can create an outline/overview for the workspace folder and its sub-pages.