Footers
Last updated: October 8, 2015 at 20:28 pm

Information that is displayed consistently at the bottom of each page on your site.


Visual example of the element:


What problem does this element or pattern solve?
If not defined clearly, this useful area can become a poorly organized, inconsistent catch-all for legal disclaimers, links to privacy policies, copyright information, and worst of all SEO spam links. However, if a user reaches the bottom of your page without taking action, you should ask yourself, “What do we want our visitors to do now?” Therefore, your footer should be as carefully considered as your header.
It applies to these platforms:

Desktop Web, Tablet Web, Smartphone Web,

An example of this element or pattern in production:

http://www.yourcompany.com



Detailed specifications

Specifications To Consider

  • It is possible to split footers into two sections: A “page variable” and “global fixed” sections. Within the variable section, page creators have the ability to customize the content and make it relevant for a particular page or section. Below that, the global footer can display mutually agreed upon items site wide. This structure addresses footer customization requests as well as minimizing one-off code, as the “variable” area is actually part of the individual page—it is only styled to look like part of the footer. Would this structure benefit your site?
  • Users frequently check for particular items in the footer, so it is important to remember recognized conventions. Expected footer content may include: contact us, careers and hiring, privacy policies, FAQs, site maps, email sign up and ppt-out links, social media, office locations, terms and conditions, etc.
  • Like the header, footer layout and content may vary dramatically from device to device. Provide examples of behaviors and styling for all devices.


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:


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

Leave a Reply