Closed Bug 724672 Opened 14 years ago Closed 12 years ago

[One Mozilla clean-up] Accessibility Content

Categories

(www.mozilla.org :: Legacy PHP system, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
Future

People

(Reporter: christine.brodigan, Assigned: bensternthal)

References

()

Details

(Keywords: qawanted, Whiteboard: u=user c=redirect p=1 r=115438)

Attachments

(3 files, 1 obsolete file)

David/Accessibility Team, We're getting ready to pack up the mozilla.org/firefox site and migrate to a new platform. Before any move, it's always important to have a yard sale to make sure we only move the good stuff (necessary stuff like that red velvet couch, not that ugly sculpture from the that we never used ... you get the point). Here is an inventory of pages on the mozilla.org site that I need you to review for: *necessary - high priority, must be ported to the new platform *unnecessary - retire & redirect *nice-to-have - (will migrate to the new codebase, but more slowly) Deadline: Monday, February 13, 2012 Content Inventory: https://etherpad.mozilla.org/one-mozilla-migration-access
Unfortunately, I won't be able to contribute directly, since I cannot read that Etherpad. Etherpads we use at Mozilla are still inaccessible. So if someone sighted from the team needs to know something from me regarding this inventory, please ping me on IRC or here in the bug.
Marco, let me know if this works better than an etherpad.
Marco, .txt attached, let me know if this works better than an etherpad.
Yes thanks, either of these will work fine!
Attached file A first pass (obsolete) —
This is a first pass. The ones I left at the bottom I absolutely am not sure what to do with, since I believe this stuff is duplicated in MDN somewhere already. This may also be true for some of the stuff that's currently in section "must have", but since Surkov did that documentation work a while ago, I'd ask him to give a better judgement on that.
Let's use something with version control. I rushed Marco's first pass over to: https://wiki.mozilla.org/Accessibility/WebMess/724672
Martijn just told me that he no longer needs those test files, so moved them to a "remove without substitution" under "unnecessary".
Attachment #595040 - Attachment is obsolete: true
FWIW I agree with Marco's first pass and comment 7.
What's left for this bug?
Hey David. Chrissie no longer works at Mozilla, so we may need to regroup on this a bit. Does the doc from comment #7 include your final thoughts in response to the original bug request? If so, it might be time for Mike or James (cc'd) to weigh in with the next step.
(In reply to John Slater from comment #10) > Hey David. Chrissie no longer works at Mozilla, so we may need to regroup on > this a bit. > > Does the doc from comment #7 include your final thoughts in response to the > original bug request? Yes. > If so, it might be time for Mike or James (cc'd) to > weigh in with the next step. Over to you Mike/James :)
Assignee: dbolter → malexis
OS: Mac OS X → All
Hardware: x86 → All
Target Milestone: 1.7 → 2.5
Howdy folks, I am undertaking the project to migrate the old mozilla.org content once and for all. The combination of supporting old platforms/content and a massive amount of redirects is no longer workable.... so we are going directory by directory which brings us to /access I looked at the wiki plan for this and here are my thoughts: - I suggest the new home for all this content be MDN https://developer.mozilla.org/en-US/docs/Accessibility - We can implement a single redirect from http://www.mozilla.org/access to https://developer.mozilla.org/en-US/docs/Accessibility redirecting all requests to that page - The accessibility group can update MDN content or we can work to get a contributor to help This content gets very little traffic (281 visit last week) and is rarely updated (2 single line edits in the past 2 years), so I would suggest pushing ahead with the redirect as-soon-as and populating MDN when you have time. I'd like to implement the redirect the week of sept 3.
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
Can you let me know if the above plan works for you? If the folks on this bug are not able to sign off can you point me in the direction of who could so I may contact them. Thanks.
All -> moving this to PHP legacy migration and will implement in the next sprint. Unless I hear otherwise the plan from webprod is to: - Implement a single redirect from http://www.mozilla.org/access to https://developer.mozilla.org/en-US/docs/Accessibility redirecting all requests to that main page We wont move any content over and will leave this in the hands of the accessibility folks.
Assignee: malexis → nobody
Component: General → Legacy PHP system
Whiteboard: u=user c=redirect p=1
Target Milestone: 2.5 → Future
Assignee: nobody → bsternthal
Depends on: 793827
> We wont move any content over and will leave this in the hands of the > accessibility folks. I've been off of the planet for awhile, sorry. So you'll just be doing a redirect for http://www.mozilla.org/access to MDN correct? Where will the http://www.mozilla.org/access pages be archived to/accessible from? There were plans to at least have a landing page on mozilla.org (with a new URL mozilla.org/accessibility) and move the current (desirable) contents to the mozilla wiki and MDN) but it took a back burner. I'd like to try and resurrect that plan. Accessibility pertains to a minority of Mozilla product users, same applies elsewhere unless the company/organization specializes in accessibility products, but that's why the page views are low.
No prob, thank you for getting back to me. Based on the above I think the best approach is to do the following: 1. Redirect the top /access page to MDN https://developer.mozilla.org/en-US/docs/Accessibility 2. Redirect individual pages to wherever you move them (wiki or mdn) 3. If at some point in the future a new page exists on mozilla.org we can redirect the /access link to that page I think the above is a good compromise as #3 does not prevent us from moving forward. We are trying to retire this old codebase by the end of the year. 1 & 2 would need to happen at the same time to prevent broken links. Thoughts?
Ken -> we can do a 'landing page' on mozilla org with links to the other content. This can be basic to start, perhaps some intro text and just a bullet list of links. Once that's done you can iterate on it. If you can provide the text you would like for the page, I can move forward.
Hi Ken and Ben, is there any update here? Ben's comments #16 and #17 suggest the very next step is to get content from Ken -- is that still the case? Thanks!
Flags: needinfo?
Justin, yep you are correct. Looks like when we last looked at this I was waiting for content from ken and that is still the case.
Flags: needinfo?
Hi Ken- We need to begin this work in April 2013. If we don't hear from you by then, we will proceed with the plan outlined in 793827. We can always work with you later to make the changes you've proposed. Thx, Jen
I'm back from planet fuzz. I've contacted Jen with some details. The following is a very raw page but it can serve as a guide to what we can use for an accessibility landing page. At least as far as the layout, style and content. The mozilla.org/access pages will have to be moved before finalizing the links. http://www.accessfirefox.org/moz-a11y/Mozilla-Accessibility.htm I'll also need to get feedback from the accessibility team on the content. Please consider me as being very green. I'll need all the help that y'all can offer with getting things done.
Hi Ken and Ben- I've decided that it is best if we move forward with the plan outlined by Ben above in October: 1. Redirect the top /access page to MDN https://developer.mozilla.org/en-US/docs/Accessibility 2. Redirect individual pages to wherever you move them (wiki or mdn) MDN is really the correct home for accessibility content: 1. the audience for this content is developers, same as MDN 2. accessibility is an ever-evolving field requiring up-to-date content, and MDN is better position to allow for regular content updates. Ben - please move forward with the redirects. Thx, Jen
Added rewrite for top page only. As other pages are migrated we should open up new bugs to redirect those. RedirectMatch permanent ^/access(?:/(?:index.html)?)?$ https://developer.mozilla.org/en-US/docs/Accessibility r=115438
Keywords: qawanted
Whiteboard: u=user c=redirect p=1 → u=user c=redirect p=1 r=115438
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: