What problems would this solve? =============================== Macros will eventually need to be able to detect if they're in a zone and if so which one. This will be used for things like tweaking the appearance of a macro's output to blend into zones better and adjusting generated text and/or tooltips to match zones when appropriate. Who would use this? =================== Template authors (and the users who the output improves the user experience for). What would users see? ===================== My guess is a page.zone property which exposes an object that includes the useful data from the DocumentZone object. Certainly at least the zone's landing page path. I'd like to also be able to get at at least some CSS information. I could see it being useful to be able to get at key colors like the header background color and image for the zone, for macros that generate custom colors for things that would benefit from being adapted based on the zone's default color scheme. What would users do? What would happen as a result? =================================================== Simply access this field to get the relevant information. Is there anything else we should know? ======================================
To be absolutely clear, unless someone has a need I'm not aware of, this is not needed for launch of zones or the redesign.
Zones will go away.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.