Closed
Bug 1336859
Opened 9 years ago
Closed 9 years ago
Remove or archive Persona-related content on MDN
Categories
(Developer Documentation Graveyard :: Mozilla Platform, defect)
Developer Documentation Graveyard
Mozilla Platform
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rfkelly, Assigned: sheppy)
References
(Blocks 1 open bug)
Details
Persona has been shut down, so we can safely remove all the content under:
https://developer.mozilla.org/en-US/Persona
I'm not sure what the policy is for old content like that so I figured I'd better file a bug rather than try to dive in and do anything with it myself...
Comment 1•9 years ago
|
||
I think the content team's preference would be to move them to the archive, such as:
https://developer.mozilla.org/en-US/Archive/Persona
Archive pages get a warning UI, like:
https://developer.mozilla.org/en-US/docs/Archive
This is blocked by bug 1331643, which prevents most page moves.
Depends on: 1331643
Updated•9 years ago
|
Component: Wiki pages → Mozilla Platform
Product: Mozilla Developer Network → Developer Documentation
| Assignee | ||
Comment 2•9 years ago
|
||
I'm archiving the Persona sections for each locale that has one to https://developer.mozilla.org/<locale>/Archive/Mozilla/Persona. I'm also updating each locale's Persona zone to use the default URL instead of the custom one previously used. Tthe result is that the content is properly archived, but links to it are almost certainly broken and will need to be updated.
Languages which need to be done:
* en-US
* it
* fa
* fr
* ru
So far, English and Italian are finished. Having some strange issues with Farsi so I'm working through that.
Assignee: nobody → eshepherd
| Assignee | ||
Comment 3•9 years ago
|
||
I've done Russian and French now. All that's left is Farsi, which I'm running into issues with.
| Assignee | ||
Comment 4•9 years ago
|
||
And Farsi has moved to https://developer.mozilla.org/fa/docs/Archive/Mozilla/Persona. All done now.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•