Open andybroomfield opened 1 year ago
The initial use case was to ensure that content always had a review date, but I can see the desire to disable the review date for some content.
2 ways to do this occur to me:
The first option would be the simplest, but maybe not the best UX.
One question, would there need to be a permission that allows users to disable the content review date so only certain users can do this?
Something to take to our comms team / product group, though my instict is to have a seperate boolean that is 'does not require further review'
Can you give an example of content that should never be reviewed ? All of our content has a review date. Even if its a policy type page that doesn't change for 3 years.
@davidupjohn In our case the original content was news articles that got accidently tagged as needing review. However there may be historic pages that shouldn't be reviewed was published as they refer to a singular event. It wouldn't be to suggest all items should get this, but an option to deal with variuous edge cases that come up.
Follow up to #48 but may have utility elsewhere. Would it be possible to mark content as reviewed, but then not set a new review date. This would help with our content that got accidently added to the review queue issue, but also apply for static content that needs to be added once but would never be updated, so no review is needed.