11.07.2015 Views

Bond brand guidelines, updated January 2010

Bond brand guidelines, updated January 2010

Bond brand guidelines, updated January 2010

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Bond</strong> <strong>brand</strong> <strong>guidelines</strong>Our <strong>brand</strong> onlineThis section is designed to give you broad creative guidance onour web site.Like all communications, our online <strong>brand</strong> must be consistent.When writing for the website, please use the house style guide and followthe writing for the web <strong>guidelines</strong>. Together, they will make sure that thecontent is consistent.Although these documents cover all aspects of how we write things like thedate and time at <strong>Bond</strong>, it is also important that web content reflects the<strong>Bond</strong> personality and tone of voice. This brings the <strong>brand</strong> to life and is oneof the cornerstones of our <strong>brand</strong> identity – see sections 1.5 and 1.6 for moreinformation.Colour on the website - <strong>Bond</strong> uses Beekeeper to update most of thewebsite content. Beekeeper makes the whole colour spectrum available tousers. However, the <strong>Bond</strong> website should only include the <strong>Bond</strong> primary orsecondary colour palette (see section 2.11 and 2.12).Using block colour, for instance to highlight text, is not allowed because itmakes the page look messy and inconsistent; use bold if you want to makecontent stand out. If you do want to use additional colour, please use thecolour codes detailed in 2.11 and 2.12 and confirm with theCommunications and Marketing Officer.When using colour, always check for accessibility, for example, white text ona <strong>Bond</strong> yellow background does not meet accessibility standards. Ask if youare not sure.Updated: <strong>January</strong> <strong>2010</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!