907248 - Migrate existing content to zones that will be launched in Q3

Status: RESOLVED INVALID

(Developer Documentation Graveyard :: General, defect)

Description

[John Karahalis [:openjck]]

Team: Please add detail to this bug based on our discussion in Toronto.

Specific questions to consider:

* Which Zones will we launch in Q3? Just App Center?
* Who will be responsible for migrating this content?

Comment 1

[John Karahalis [:openjck]]

> As a user, I expect all content I interact with in a zone
> adhere to that zone’s flow, styles, and experience, regardless
> of whether it originates from another MDN location.

Comment 3

[Eric Shepherd [:sheppy]]

We need site-wide find/replace to do this correctly. This will involve a lot of cleanup and hierarchy revision work that can't be done properly without it.

Comment 4

[Les Orchard [:lorchard]]

Do we absolutely need site-wide search & replace to get the first zone(s) in? I think bug 671761 is probably a big & very dangerous project and not feasible in Q3.

Also, what *is/are* the first zone(s)? I was mainly assuming just the Apps zone.

Comment 5

[Daniel Buchner [:dbuc]]

(In reply to Les Orchard [:lorchard] from comment #4)
> Do we absolutely need site-wide search & replace to get the first zone(s)
> in? I think bug 671761 is probably a big & very dangerous project and not
> feasible in Q3.
> 
> Also, what *is/are* the first zone(s)? I was mainly assuming just the Apps
> zone.

The only Zone we need to get on MDN this quarter is App Center. I'm not sure how search/replace is relevant to App Center (or zones?), what is the functionality? I can't imagine they are linked...

Comment 6

[Les Orchard [:lorchard]]

Also, assuming Apps is one of the Q3 zones to be launched... do we have a content inventory? Who's going to start creating pages and carrying over content?

Comment 7

[Les Orchard [:lorchard]]

Removing bug 671761 as a dependency for now

Comment 8

[John Karahalis [:openjck]]

We have only committed to launching with the App Center Zone, and Mark is working that in bug 918130. No need to keep this bug around.