Scheduled maintenance and what will be unavailable

Scheduled maintenance and what will be unavailable Writing it up because I had to work it out twice and would rather nobody else did.

Nominating something for promotion into the documentation commons.

The topic in question keeps being re-asked, has a good marked solution, and contains a worked example that would be more useful on a page with a review date than buried in a reply. That is exactly the promotion criterion as written.

Objections welcome and genuinely wanted — the whole point of discussing promotions in public is that a bad promotion is harder to undo than a bad reply.

When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.

Coming back to the opening post, because the follow-up matters more than the original answer.

Practical note that does not fit anywhere else. Whatever you conclude from this topic, write down what you did and when. The single most useful thing in your own records is not any individual result; it is that they are dated and consecutive.

Picking up the opening post: that is the part I would want checked first.

Implementation timeline: announcements include when a change takes effect. Marking the date helps you know whether the change is already in effect.

RSS: if you prefer to receive announcements by feed rather than visiting the site, RSS is available for this subcategory.

Archives: older announcements are archived by date. Checking archives is useful if you want to know what changed when.

I read post #5 twice before replying, because I had assumed the opposite.

Staff-only posts: some announcements are visible only to staff (concerning internal operations). Members see public announcements.

I disagree with the reply above, and I think the disagreement is substantive rather than terminological.

The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.

Feedback to announcements: if you have feedback on an announced change (not a question, but your position) post it in the Meta category rather than here.

post #9 answers the question as asked. The question underneath it is different.

Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up.

Two things before anyone answers the substance.

First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.

Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.

I read post #12 twice before replying, because I had assumed the opposite.

Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions clarifying what was announced.