[GH-ISSUE #4372] [FR] Auto reference/index sub pages in parent page #1953

Closed
opened 2026-03-23 21:18:30 +00:00 by mirror · 3 comments
Owner

Originally created by @Disar on GitHub (Jan 11, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4372

Description

A function that allows us to create an index of references to all sub pages in the parent page.

Impact

I use empty pages as separators for projects which usually end up with nothing in them.
It would be great if it's possible to auto generate an index of references to all child documents, recursively.

This way you don't have to scroll through your outliner and expand every sub page. It gives you a quick overview what is available in the parent doc.

Additional Context

  • Give the user the option to choose the depth of references to create ( i.e 1 = only create an index for immediate child pages but not the child pages of those pages.
  • Maybe give the option to choose the root to start from. The root must be one of the sub pages of the page the index will be generated in. Being able to create multiple indexes might give a more impactful oversight of the important docs when dealing with many of them.
  • references should be a simple bullet list with indentation for every depth.
Originally created by @Disar on GitHub (Jan 11, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4372 ### Description A function that allows us to create an index of references to all sub pages in the parent page. ### Impact I use empty pages as separators for projects which usually end up with nothing in them. It would be great if it's possible to auto generate an index of references to all child documents, recursively. This way you don't have to scroll through your outliner and expand every sub page. It gives you a quick overview what is available in the parent doc. ### Additional Context * Give the user the option to choose the depth of references to create ( i.e 1 = only create an index for immediate child pages but not the child pages of those pages. * Maybe give the option to choose the root to start from. The root must be one of the sub pages of the page the index will be generated in. Being able to create multiple indexes might give a more impactful oversight of the important docs when dealing with many of them. * references should be a simple bullet list with indentation for every depth.
Author
Owner

@Jayaprakash-dev commented on GitHub (Jan 19, 2024):

Hey @Disar, I've submitted a PR that will fix this issue.

<!-- gh-comment-id:1900692880 --> @Jayaprakash-dev commented on GitHub (Jan 19, 2024): Hey @Disar, I've submitted a [PR](https://github.com/AppFlowy-IO/AppFlowy/pull/4420) that will fix this issue.
Author
Owner

@lalomartins commented on GitHub (Oct 12, 2024):

This was never merged, so maybe the FR shouldn't be closed until that happens?

<!-- gh-comment-id:2408631667 --> @lalomartins commented on GitHub (Oct 12, 2024): This was never merged, so maybe the FR shouldn't be closed until that happens?
Author
Owner

@Xazin commented on GitHub (Oct 12, 2024):

This was never merged, so maybe the FR shouldn't be closed until that happens?

This is a duplicate of #4282 thus it doesn't need to stay open, the PR also links to the original issue.

<!-- gh-comment-id:2408665371 --> @Xazin commented on GitHub (Oct 12, 2024): > This was never merged, so maybe the FR shouldn't be closed until that happens? This is a duplicate of #4282 thus it doesn't need to stay open, the PR also links to the original issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#1953
No description provided.