mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-09 03:09:38 +03:00
Sub-Pages (more layers) #5470
Open
opened 2026-02-05 10:05:28 +03:00 by OVERLORD
·
3 comments
No Branch/Tag Specified
development
further_theme_development
l10n_development
release
llm_only
vectors
v25-11
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
pull-request
Mirrored from GitHub Pull Request
No Label
🔨 Feature Request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#5470
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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 @hailster17 on GitHub (Oct 23, 2025).
Describe the feature you'd like
Currently Bookstack has layers setup in this format Book->Chapter->Pages. Adding sub-pages or one more layer under Pages would be great.
Describe the benefits this would bring to existing BookStack users
Many users are leaving GitBook and some are switching to BookStack, GitBook offers more layers which allows for more organized data. One of the biggest complaints from our users is when we use collapsible blocks the search feature isn't as efficient as they need to go to the page, find the collapsible block and open the block to see the data. Having one more layer would allow for more organized and cleaner data.
Can the goal of this request already be achieved via other means?
Kind of- The only work around we have found is to use collapsible blocks. When the user uses the search feature it will find the data then the user needs to go to the page but then they must manually search through the page to find the collapsible block that contains the data they need.
Have you searched for an existing open/closed issue?
How long have you been using BookStack?
Under 3 months
Additional context
Overall bookstack has been great and we appreciate the work everyone has done to make it as good as it is.
@ssddanbrown commented on GitHub (Oct 23, 2025):
Hi @hailster17,
It's very unlikely there'd be anything below the current page level due to how the platform has been designed & built, which focuses on pages being the core base content layer.
Additional levels is a common request though, see #95 for some history in that regard.
Part of my video here, from about 11:05 is also very much relevant, and goes into the history (where I did original build the platform to have infinitely nestable pages) and where I think things may head (A new proper layer above books, shelves become a more flexible collection item).
@virgo77 commented on GitHub (Nov 4, 2025):
Hi!
I took a look at your video, and I totally understand what you mean about setting layer levels in this tool... a great tool btw.
But, recently, I had 10 months trainings with lots of modules and courses, and multiple practical exercises in each course. So, actually, I can't sort all these courses, and practical exercises in sub-chapters, and it's annoying and frustrating to me.
Just look:
You could say "Why not naming the shelf with the name of the training?". Yeah, true... but as I had another trainings, I can sort all these trainings in one shelf!
It's the same about all my own documentations, tutorials and all the fixes and solutions about issues I had on my home labs (or professional labs).
I'm stuck because I don't know how to sort these, any other way than this. So, to get rid of this, I give some name to chapters/pages to try to sort correctly, but it is not really comfy and readable nor logical.
So maybe you can let us to sort according to sub-chapters or sub-pages, like asked in this really old message? Maybe you can fix sublevels/layers to 4 or 5, whatever it is a sub-chapter or a sub-page, like this:
Shelf > Book > Chapter > Subchapter > page > subpage/subpage/subpageor this:
Shelf > Book > Chapter > Subchapter/Subchapter > page > subpage/subpageor this:
Shelf > Book > Chapter > Subchapter/Subchapter/Subchapter > page > subpageor maybe
Shelf > Book > Chapter > Page > Paragraph > "Sub-Paragraph/.../..."? (it makes more sense like this to me)Once we've reached the maximum number of sub-levels, we can't create any more. This allows for more flexibility. And as it is a recurring request, maybe you can give it a try?
It would be really great!
Best Regards,
V.
@sz-hunor commented on GitHub (Nov 30, 2025):
I recently found BookStack on my journey to find a replacement for OneNote and this is actually the closes bit of software that I found that you can self host and where you actually own your documents that isn't lacking anything from what I use OneNote for.
OneNote itself also only allows for 3 levels of indentation (page and 2 levels of sub-pages), and I feel like people don't complain about that being too limiting (I watched your video where you say that sub-pages is a re-occurring feature request). And their Notebook -> Section layout is pretty much analogous to Shelves -> Books.
Obviously, this is a different piece of software with a different goal, but I was wondering if it wouldn't be possible to simply have a toggle for layout style. With one option being your current, uncompromised vision and another that allows the use of a few levels of sub-pages.
Also, I'd love to be able to also toggle seeing the shelves level in the side-bar as well. And yes, I am shamelessly asking if it would be possible to customize this to be the perfect 1:1 transition path away from Microsoft training their AIs on all my notes.