Closed
Bug 1088233
Opened 10 years ago
Closed 7 years ago
Create zone-specific footer announcements slot
Categories
(developer.mozilla.org Graveyard :: Wiki pages, enhancement)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: hoosteeno, Unassigned)
References
Details
(Whiteboard: [specification][type:feature])
What problems would this solve? =============================== Allow us to present product announcements to people visiting a specific zone (for example, the devtools zone) Who would use this? =================== Product engagement teams would use it to make targeted announcements of product developments. Developers interested in the zone might use it to learn more about a product very aligned with the zone. What would users see? ===================== Near the footer, below all the main body of the content, an announcement resembling a banner ad. What would users do? What would happen as a result? =================================================== Developers would learn about Mozilla products that help make web development better. Is there anything else we should know? ====================================== Can you identify the specs for the slot? Height, width, content types?
Reporter | ||
Comment 1•10 years ago
|
||
:jezdez says... "...there are a few variables available in the document.html (set on top): {% set zone_stack = document.find_zone_stack() %} zone_stack is a list of zone objects starting from the current document going up till the root document. Each zone object has an attached wiki document you can work with if needed. {% set is_zone = zone_stack|length %} Is a boolean-ish object to say if the current document is even in a zone. {% set is_zone_root = is_zone and zone_stack[0].document == document %} Is a boolean object to say if the current docoument is the root document of a zone. PS: Please don’t call document.find_zone_stack() a lot, it’s *super* ineffective, a O(n) function, making one db query for each zone level in the stack"
Comment 2•10 years ago
|
||
Some thoughts on specs: The flame ads are responsive and were created using a wide and narrow image as guidelines. Doing this again is dependent on team time though. It's about 4 hours of work. We could offload that work onto creative by using img with srcset or picture to load different sizes for different break points. In which case we would need ones that are: 320, 480, 768,
Comment 3•10 years ago
|
||
Well that ^^^ sure magically submitted while I was in the middle of writing it. Some thoughts on specs: The flame ads are responsive and were created using a wide and narrow image as guidelines. Doing this again is dependent on team time. It's about 4 hours of work. 320 and 768 pixels wide were good for these purposes. We could offload that work onto creative by using img with srcset or picture to load different sizes for different break points. In which case we would need ones that are: 320, 480, 768, 1024, 1200, and 1400 pixels wide. Height is dictated mostly by how obtrusive we want to get and how much info we have to share. The site is built with grid-spacing of 20 pixels, so a multiple of 20 pixels high would be a nice to have.
Updated•10 years ago
|
Component: General → Wiki pages
Updated•10 years ago
|
Severity: normal → enhancement
Updated•9 years ago
|
Blocks: mdn-zone-fixes
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•