Setting to ignore Chapters/Pages on Export #4231

New Issue

OVERLORD · 2026-02-05T08:18:11+03:00

OVERLORD commented

2026-02-05 08:18:11 +03:00

Originally created by @ATroschke on GitHub (Sep 22, 2023).

Describe the feature you'd like

We would like to be able to document Software and organize it in a way so that our internal documentation and the external/public documentation a customer may get are in the same place.

Ideally, this would be done by setting a page as not Exportable/Exportable so that consecutive Exports do not need to be reconfigured every time.

Describe the benefits this would bring to existing BookStack users

This would make internal documentation (for example for alpha/beta features) easier to manage, so our documentation can be properly revised as the feature develops and when it's all done, it can just be marked as "Exportable" to be in the next Version of our Docs.

Can the goal of this request already be achieved via other means?

This can probably be achieved using the API and/or manually exporting every needed page individually and stitching it together again.

Have you searched for an existing open/closed issue?

I have searched for existing issues and none cover my fundamental request

How long have you been using BookStack?

3 months to 1 year

Additional context

No response

Originally created by @ATroschke on GitHub (Sep 22, 2023). ### Describe the feature you'd like We would like to be able to document Software and organize it in a way so that our internal documentation and the external/public documentation a customer may get are in the same place. Ideally, this would be done by setting a page as not Exportable/Exportable so that consecutive Exports do not need to be reconfigured every time. ### Describe the benefits this would bring to existing BookStack users This would make internal documentation (for example for alpha/beta features) easier to manage, so our documentation can be properly revised as the feature develops and when it's all done, it can just be marked as "Exportable" to be in the next Version of our Docs. ### Can the goal of this request already be achieved via other means? This can probably be achieved using the API and/or manually exporting every needed page individually and stitching it together again. ### Have you searched for an existing open/closed issue? - [X] I have searched for existing issues and none cover my fundamental request ### How long have you been using BookStack? 3 months to 1 year ### Additional context _No response_

OVERLORD added the 🔨 Feature Request label 2026-02-05 08:18:11 +03:00

OVERLORD commented

2026-02-05 08:18:15 +03:00

@ssddanbrown commented on GitHub (Sep 22, 2023):

Thanks for the request @ATroschke.
Personally, I'm not too keen to add something like that requested, since it would be introducing something quite use-case specific at the cost of complexity, while focused on the idea of publishing exports being the end result of BookStack content whereas we typically aim to be a living documentation store.

That said, content should only end up in the export if visible to the exporting user.
Therefore you could effectively do this via permission controls, limiting access for an "Exporter" role & user.
Then, when needing to export, use that account to run the export (Either via the UI or the API).

@ssddanbrown commented on GitHub (Sep 22, 2023): Thanks for the request @ATroschke. Personally, I'm not too keen to add something like that requested, since it would be introducing something quite use-case specific at the cost of complexity, while focused on the idea of publishing exports being the end result of BookStack content whereas we typically aim to be a living documentation store. That said, content should only end up in the export if visible to the exporting user. Therefore you could effectively do this via permission controls, limiting access for an "Exporter" role & user. Then, when needing to export, use that account to run the export (Either via the UI or the API).

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#4231