948438 - Make all translations of a zone use the same CSS

Status: RESOLVED DUPLICATE of bug 943979

(developer.mozilla.org Graveyard :: General, defect)

Description

[Eric Shepherd [:sheppy]]

What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
Currently, when a localized version of a page is turned into a zone, it needs its own CSS configured. This will easily lead to zones being broken or out of sync with style guidelines. Instead, all localizations of the same zone should share the same CSS.

What problems would this solve?
===============================
This would make it much easier to create localized zones, since the CSS wouldn't need to be configured separately. Also, this will keep us from having localized zones get out of sync with each other as styles and artwork change.

Who would use this?
===================
Admins.

What would users see?
=====================
Consistent zones, and more localized zones.

What would users do? What would happen as a result?
===================================================
All CSS changes would be done in one place. Awesome!

Is there anything else we should know?
======================================

Comment 1

[Les Orchard [:lorchard]]

This could get complicated.

Currently, a DocumentZone is a modifier attached to a Document. That modifier augments the page and all its topic children with zone features - ie. shared CSS, zone navigation, URL root remapping.

Thus, since pages are per-locale, so are zones.

If we want features of a zone to affect translations across locales, we need to work out the implications.

* If both an en-US page and a fr translation have zones attached - how do the zone features apply? Use one locale's CSS over another? Concatenate the CSS? Which takes precedence for navigation & URL remapping?

* If an en-US page has a zone attached, but *not* the fr translation - how do the zone features apply? Just use all the en-US features, including en-US navigation & URL remap?

* Should en-US be the only locale where zones are created?

Comment 2

[Eric Shepherd [:sheppy]]

If the en-US page is a zone, we would not want to force the French version to be one too, because it might not have content updates required to work properly as a zone. So it would still need that switch flipped. But once it's a zone, the CSS changes for the English version should apply to all translations of that zone.

Comment 3

[Les Orchard [:lorchard]]

(In reply to Eric Shepherd [:sheppy] from comment #2)
> If the en-US page is a zone, we would not want to force the French version
> to be one too, because it might not have content updates required to work
> properly as a zone. So it would still need that switch flipped. But once
> it's a zone, the CSS changes for the English version should apply to all
> translations of that zone.

Yes, but what if the French zone has its own CSS also? Just ignore it & use the parent translation zone CSS?

Comment 4

[Eric Shepherd [:sheppy]]

The French zone shouldn't have its own CSS. That's the point. All translations of the same zone should use the same CSS.

Comment 5

[Eric Shepherd [:sheppy]]

OK, let's try this on:

All localizations of a zone should pull in the CSS from the translation parent *PLUS* from the translated zone. That way, localized zones get the CSS that they probably want automatically, but have the ability to customize it.