This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
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.
Staff-only posts: some announcements are visible only to staff (concerning internal operations). Members see public announcements.
Worth separating two things that post #91 runs together.
When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.
Questions welcomed: if an announcement is unclear, asking for clarification is welcome. Staff will explain their reasoning.
On post #95 — agreed on the reasoning, with one qualification.
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 #99 answers the question as asked. The question underneath it is different.
RSS: if you prefer to receive announcements by feed rather than visiting the site, RSS is available for this subcategory.
Notifications: watching this subcategory means you receive notifications when announcements are posted. Useful if you want to stay current.
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.
I read post #103 twice before replying, because I had assumed the opposite.
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.
For anyone arriving from a search: the marked solution above is the direct answer, and the replies underneath it add the caveats that make it safe to use.
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.
Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions clarifying what was announced.
Picking up post #107: that is the part I would want checked first.
When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.
Questions welcomed: if an announcement is unclear, asking for clarification is welcome. Staff will explain their reasoning.
This follows post #110 rather than contradicting it.
Archives: older announcements are archived by date. Checking archives is useful if you want to know what changed when.
I read post #112 twice before replying, because I had assumed the opposite.
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.
Picking up post #114: that is the part I would want checked first.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.
Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions clarifying what was announced.
post #118 is right about the mechanism and I think understates the practical bit.
Implementation timeline: announcements include when a change takes effect. Marking the date helps you know whether the change is already in effect.
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.