Paid Content & Media Guidelines
Last updated: September 11, 2015 at 22:58 pm

Positions and display rules for paid media or content such as ads or sponsored listings.


Visual example of the element:


What problem does this element or pattern solve?
Paid content is often pulled from external networks and will undoubtedly violate many of your scaffolding standards, particularly your grid and modules. Therefore, if your site accepts paid content or media from external sources, you should clearly address those discrepancies here. This is particularly important on responsive sites, as the individual ad sizes, formats, and display rules may need to change from device to device.
It applies to these platforms:

Desktop Web, Tablet Web, Smartphone Web

An example of this element or pattern in production:


Detailed specifications

Specifications To Consider

  • Does your site accept paid content? If so, what types? You may want to define all the different types of paid content first, then break out the details for each in the detailed specification area.
  • If your site accepts traditional banner ads, are there restrictions on where those ads may appear? Are the restrictions based on the page type? Position within the page itself? How do they align to the grid? Provide links to your company’s detailed media guidelines for the most current information.
  • If you accept premium search results, provide visual examples of their formatting for designers creating mockups and prototypes.
  • Do you create dedicated landing or advertorial style pages for advertisers? Again, provide links and examples.
  • If nothing else, include a link to your company’s detailed advertising and media kit so that anyone creating a new page can access the most current guidelines.


Location of assets to build this element or pattern
Location of UX or visual design assets
Location of development code repository


Additional details
Information on research, user testing, or usability reports:

Not Applicable (Remember: no field should be blank!)

This element or pattern may also be known as:
Not Applicable (Remember: no field should be blank!)
Related elements within this Style Framework:

Not Applicable (Remember: no field should be blank!)



Owners and governance
UX or design 0wner
John Designowner
Email: design.owner@yourcompany.com
Business or marketing owner
Mary Businessowner
Email: business.owner@yourcompany.com
Development owner
Mike Devowner
Email: development.owner@yourcompany.com


Other information
Please include any other relevant information about this element or pattern:
Not Applicable (Remember: no field should be blank!)


Comments & Questions