861991 - Content Zones improvements

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: General, enhancement, P2)

Description

[John Karahalis [:openjck]]

What problems would this solve?
===============================
We would like to host major collections of content on MDN, but still allow the groups responsible for those collections to maintain some level of control over the branding and organization of that content.

Who would use this?
===================
Any group at Mozilla that has a major collection of documentation that could stand on it's own. Two examples are the DevHub team and the HTML5 game team we met with in April 2013.

What would users see?
=====================
These teams should have some level of control over content branding and organization. More detail is needed here. We will coordinate with the user experience team and Dan to determine exactly how these zones will work.

What would users do? What would happen as a result?
===================================================
See above.

Is there anything else we should know?
======================================
This is similar to, but will probably supersede the Content Curation idea (bug 839306)

Comment 1

[Eric Shepherd [:sheppy]]

To reiterate (as I've done on a related bug): each zone should be allowed to adjust its look only so much. We want to be sure that all the content is clearly still part of the MDN family. So colors and background art and the like should be able to change, but the overall layout of where sidebars and the like are should not.

Comment 2

[Daniel Buchner [:dbuc]]

(In reply to Eric Shepherd [:sheppy] from comment #1)
> To reiterate (as I've done on a related bug): each zone should be allowed to
> adjust its look only so much. We want to be sure that all the content is
> clearly still part of the MDN family. So colors and background art and the
> like should be able to change, but the overall layout of where sidebars and
> the like are should not.

The zones will not be restricted to the wiki layout or any of its constraints - that is a crucial requirement. Zones introduce the concept of static pages and content syndication from outside sources. Wiki/docs will be able to be shown within zones, and will maintain the same format, with subtle style tweaks as you mentioned.

Comment 3

[John Karahalis [:openjck]]

I went ahead and opened a new dependency for this bug: bug 906494. This will act as a collection for all Content Zone user stories documented by Dan and Ali.

More than anything, I wanted to get all of these user stories in one place so that we can discuss and evaluate our progress on each individually during the Toronto offsite. Some of these bugs might be duplicates of other open bugs, some might be complete, and so on. We can correct these issues when we look them over as a group--and the bugs will help us document those corrections.

Comment 4

[John Karahalis [:openjck]]

Renaming this bug to reflect its reality as a collection of Content Zones improvements. Please see bug 907234 for the features we will include in the MVP.

Comment 5

[Florian Scholz (Open Web Docs)]

Zones are deprecated