Page Expiration / Update Content Manager #375

New Issue

OVERLORD · 2026-02-04T19:12:57+03:00

OVERLORD commented

2026-02-04 19:12:57 +03:00

Originally created by @Shackelford-Arden on GitHub (Jul 15, 2017).

Desired Feature

So, once you've added a lot of content to your site, I believe it can be difficult to know what content was last updated and when (on a large scale).

I would find it helpful if:

We could set a "field" on a page of when it's content needs to be updated or when it's marked as "outdated".
Have a view where we can see pages ranked by last modified date or their expiration date.

This view would help editors/admins know when pages need to be updated or potentially even removed.

Just a thought I had for myself and potentially groups who use Bookstack for content that changes on a frequent bases (like technical guides or documentation).

Originally created by @Shackelford-Arden on GitHub (Jul 15, 2017). # Desired Feature So, once you've added a lot of content to your site, I believe it can be difficult to know what content was last updated and when (on a large scale). I would find it helpful if: - We could set a "field" on a page of when it's content needs to be updated or when it's marked as "outdated". - Have a view where we can see pages ranked by last modified date or their expiration date. This view would help editors/admins know when pages need to be updated or potentially even removed. Just a thought I had for myself and potentially groups who use Bookstack for content that changes on a frequent bases (like technical guides or documentation).

OVERLORD added the 🛠️ Enhancement label 2026-02-04 19:12:57 +03:00

OVERLORD closed this issue

2026-02-04 19:12:59 +03:00

OVERLORD commented

2026-02-04 19:13:10 +03:00

@ghost commented on GitHub (Sep 19, 2017):

This would be a huge feature-- if a document could be flagged as Outdated or Needs Review by users. Then, users (but not writers) of the documentation can easily communicate where there was an issue either with accuracy, clarity of wording, or order of the process.

The comments section would be a sufficient place to leave appropriate feedback I should think-- it would be interesting maybe if there was an Issue comment type that could be marked as resolved and hidden from the main page (maybe just viewable in the revision history. personally, I don't like seeing comments that are out of date as much as I don't like seeing pages that are out of date).

@ghost commented on GitHub (Sep 19, 2017): This would be a huge feature-- if a document could be flagged as _Outdated_ or _Needs Review_ by users. Then, users (but not writers) of the documentation can easily communicate where there was an issue either with accuracy, clarity of wording, or order of the process. The comments section would be a sufficient place to leave appropriate feedback I should think-- it would be interesting maybe if there was an _Issue_ comment type that could be marked as resolved and hidden from the main page (maybe just viewable in the revision history. personally, I don't like seeing comments that are out of date as much as I don't like seeing pages that are out of date).

OVERLORD commented

2026-02-04 19:13:14 +03:00

@ssddanbrown commented on GitHub (Nov 8, 2022):

I'm going to go ahead and close this off since there's been little demand on this specific issue since it was opened.
Note, there have been some options added since this request:

You can filter search results based upon updated date.
You could apply tags, such as "Last Reviewed At: 20220511" then run a tag query such as [Last Reviewed At<=20220601]

@ssddanbrown commented on GitHub (Nov 8, 2022): I'm going to go ahead and close this off since there's been little demand on this specific issue since it was opened. Note, there have been some options added since this request: - You can filter search results based upon updated date. - You could apply tags, such as "Last Reviewed At: 20220511" then run a tag query such as `[Last Reviewed At<=20220601]`

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#375