Take a changelog entry down without deleting it

Until now a changelog entry had exactly one way off your changelog: delete it. That is fine for a mistake and wrong for everything else. A maintenance notice, a beta invite or a temporary workaround is only useful while it is true, and deleting it takes its content and its stats with it. Entries can now be archived instead: taken off your changelog while staying in your admin, intact. What you get An unpublish date. Set it next to the publish date and the entry takes itself down at that time, so a maintenance notice can retire itself once the window is over. It has to sit at least six hours after the entry's own publish date, so nothing disappears before anyone has read it. Unpublish by hand. Available on any live entry from its actions menu, and it takes effect straight away. Archived means gone from everywhere your users look. Your widget, your portal, the entry's public link, your RSS feed, your sitemap and your in-app announcements. If an email about it was still waiting in the notification queue, that email is not sent. The entry itself stays. It becomes read-only in your admin, keeping the views, reactions and email counts it collected while it was live, in a new Archived section and tab in your changelog list. Duplicate to publish again. Copy any entry into a fresh draft. Its title, body, category, audience, author, attachments and notification settings come along; its dates and its stats start clean. Running a recurring notice Publish the notice, take it down when the window is over, and duplicate it when the next one comes around. Your wording stays consistent and you never start from a blank editor. Archiving is deliberately one-way, and duplicating is how an entry goes back up. That way there is never a question about whether subscribers get emailed twice, or whether an old view count still belongs to the update your users are actually reading. Setting an unpublish date is available on Business and above. Unpublishing by hand works on every plan.