Apple Support Community is already read-only and will permanently close on November 20, 2026, according to the notice on Apple's forum. If a thread contains a fix you depend on, preserve the explanation and its conditions while you can still read it. The notice does not promise a public archive after closure.
The change was reported on the evening of November 10 in Pacific time by MacRumors. The originating Verge story followed on November 11. Those reporting dates are separate from the November 20 closure deadline.
Posting has ended; the archive question remains open
Apple's banner says the site no longer accepts new posts. The immediate loss is therefore the ability to ask a fresh question or add a reply, even while existing discussions remain readable. Apple's message directs visitors to its official support site and thanks contributors.
It does not describe what will happen to individual thread URLs after November 20. Treating every old link as certain to disappear would go beyond that evidence; assuming it will keep working would also be a gamble. The useful response is to reduce dependence on a single bookmark without predicting Apple's hosting decision.
Save an answer together with the conditions that made it useful
For a small set of threads you actually use, a manual record is more useful than a collection of isolated tips:
Save the page or print it to a PDF using your browser, retaining the original URL and date for reference.
Keep the device model, software version, symptoms and replies that qualify the proposed fix. An accepted answer can still concern a different configuration.
Check whether a current Apple Support article addresses the same issue before applying an older procedure.
These are TechKili's preservation suggestions, not an export service announced by Apple. Keep any saved copy for reference and avoid including other people's personal details in a new public support request.
For an unresolved problem, use Apple's contact options and describe the exact device, software version, error and steps already attempted. A community discussion can help explain the history of an issue, but its closure does not remove the separate official support route. Readers need a durable reference for useful knowledge and a working route for their next question.