Wednesday, May 13, 2009

OCS Research Report Versioning Guidelines

The OCS Research Report is not going to be a static document. Revisions and suggestions are always welcome. (If you have anything that you think needs to be added, email me.) As such, we need a versioning system. Partly so that I won't forget and partly so that it's more widely known, here's the plan: I don't anticipate leaving the 1.somethings any time soon, if ever. So, the syntax will be 1.section added.section revised. In practice, this means that the newest version (coming soon), with changes to the section on colour spaces, will be version 1.0.1. Good?

Labels: , ,

Friday, April 10, 2009

Style Guide

New and exciting! A handy, one page version of the OCS style book. Download the PDF or look at the version below.

Labels: ,

Thursday, March 19, 2009

OCS style: colour



OCS blue is #0099cc for web and CMYK 78 24 0 0 for print.

If grey must be used instead of blue, use #7c7c7c (CMYK 0 0 0 51).

Headers and links on the OCS website are always #0099cc.

Logotype, when in colour is black and OCS blue. When in greyscale, it is black and OCS grey.

Labels:

Tuesday, March 17, 2009

OCS style: logo and typography

The OCS logo, without typography, has a 1:1 aspect ratio, with typography, it becomes 100:79.5.
Logo with type looks like this:
Logo without type looks like this:
Type alone looks like this:
OCS uses FreeSans, bold and all caps for logotype.
OCS uses FreeSans for all non-HTML typography.

Labels:

Introduction to the OCS style book

Why does the Open Colour Standard need a book of style guidelines? It needs a defined style for the same reasons any other Open Source project should have one. A style book helps to define and create a unified look in a decentralized project. It helps new community members create on-message collateral and identity elements. It prevents the OCS look from becoming diffuse and meaningless. It prevents the misuse of OCS identity elements. What's more, it answer questions about the OCS look and guidelines.

In decentralized undertakings like Open Source projects, having something to tie contributors together is especially important. Since OCS has no physical culture or ties between community members, it must rely on tools like the style book to create and encourage unity.

Labels: