Conversation
|
Preview URLs (4 pages)
External URLs (1)URL:
(comment last updated: 2026-03-27 16:43:51) |
chrisdavidmills
left a comment
There was a problem hiding this comment.
@pepelsbey a few comments for you, as I've got a keen interest in this content ;-)
Looking pretty good already; nothing too serious.
files/en-us/mdn/writing_guidelines/howto/creating_moving_deleting/index.md
Outdated
Show resolved
Hide resolved
files/en-us/mdn/writing_guidelines/howto/sunsetting_content/index.md
Outdated
Show resolved
Hide resolved
files/en-us/mdn/writing_guidelines/howto/sunsetting_content/index.md
Outdated
Show resolved
Hide resolved
files/en-us/mdn/writing_guidelines/howto/sunsetting_content/index.md
Outdated
Show resolved
Hide resolved
files/en-us/mdn/writing_guidelines/howto/sunsetting_content/index.md
Outdated
Show resolved
Hide resolved
files/en-us/mdn/writing_guidelines/howto/sunsetting_content/index.md
Outdated
Show resolved
Hide resolved
files/en-us/mdn/writing_guidelines/howto/sunsetting_content/index.md
Outdated
Show resolved
Hide resolved
|
|
||
| After the agreed sunsetting period has passed, the content can be removed from MDN Web Docs: | ||
|
|
||
| 1. **Archive the content.** Copy the section to the [MDN Museum repository](https://github.com/mdn/museum) for archival purposes. Keep the content in a directory that matches the original URL path. For example, content at `https://un5j2j18xhuv2emkwgjjkgb49yug.julianrbryant.com/en-US/docs/Games` would go in a `/docs/games/` directory in the museum repository. This preserves MDN's content history while keeping deprecated material off the active site. |
There was a problem hiding this comment.
Is this all the user needs to do? Are landing pages, menus, etc. handled automatically?
files/en-us/mdn/writing_guidelines/howto/sunsetting_content/index.md
Outdated
Show resolved
Hide resolved
|
I think it might be worth keeping "tombstones" for deleted content sections. I remember Josh once saying that just deleting content and redirecting somewhere like the home page is kind of gaslighting readers, and whenever content is removed we see confused readers showing up wondering where it has gone. So if there's already a GitHub discussion to record the decision, and you're already archiving the deleted content, then you could have a page that lists these decisions, just saying what was removed, quickly why, and linking to the discussion. Then the redirect could go to that page, and a reader landing on the deleted page would get context about what's going on and how to access the old content, if they still want to. |
Description
Adds the “How to sunset a section of content” guide.
Motivation
To describe the process for retiring entire sections of MDN Web Docs content.