HTML5 Muy LOGO!
HTML5 ||Validates||
There has been a lot of discussion as a result of W3C's HTML5 logo release two days ago. (See 2 Feb update)
- I was especially encouraged by the diverse support for the HTML5 logo and I'm happy with the reception, even if not universally positive- W3C Blog Post
- HTML 5
- CSS 2.1
- CSS Selectors
- CSS Medias
- CSS Text
- CSS Backgrounds
- CSS Colors
- (updated)
- Over the last six months or so,
some of the hardcorest web developers and designers have started to test the possibilities of the newest markup for building websites, HTML5. I realize that some might not even be aware that there was HTML1, 2, 3, or 4 or what it even means for coding language to be upgraded. In a nutshell: HTML, overseen by the World Wide Web Consortium (W3C for short), is the gobbledygook text that gives structure to a website; in its first iteration, the amount of things you could do with it was limited and in each version it has added bits of language that allow for more versatility. This latest version reflects the advancement of the web in general, by natively allowing the use of multimedia or web fonts, for example, as well as having a more robust set of "tags" - i.e., the ‹em› tag makes things ‹em›italic‹/em›, but that's just the most basic example - that power each website.
HTML5 has gotten a lot of support and generated plenty of excitement and the W3C wants to encourage its use so they are introducing an official HTML5 logo that will serve as a badge for those that are adopting the latest and geekiest markup language. In charge of designing the logo, identity, and a set of icons was Honolulu, HI-based
We intend for it to be an all-purpose banner for HTML5, CSS, SVG, WOFF,On our agency website we have a more visual description of the evolution of the mark, but I can give you the narrative form here. We start any logo development project with really a pretty standard design process - we research, build a brief, amass keywords, create concept boards, and then we get to sketching. In the concept board phase of the project, a few focal points really stood out to us - stars, sea stars, and archways.[…]
So, hundreds of star, archway and adorable sea star sketches later, we really focused in on the shape of the keystone and
Some sketches and a couple of other ideas considered.
(in what seems an obvious evolution) it's incarnation as a crest, badge or shield. Not only is a keystone is a great metaphor for how HTML5 stands at the center of this current technology movement, but the final design started to take shape simultaneously as a coat of arms and badge of honor we felt captured the spirit and substance of the open web platform and the community surrounding it.
- Ocupop Creative Director Michael NielingThis is a great strategy by the W3C, giving the organization a visual tool that the developer and design community can rally around and be proud to show off - a much needed boost, since most of the W3C visual palette is drab. The actual logo, or badge, is bold and simple with a solid structure, if a little superhero-ish, but it's definitely cool enough that people will not mind displaying it on their own websites. They push the color version a little too hard on the logo website and it would probably benefit them to show off the single color version too as I think more people might opt for it over the bright, road sign-like color version.
In addition to the badge, there is a set of icons that represent the different technologies that HTML5 offers. People can use the "Badge Builder 5000" to customize the badge and append the icons of the different technologies they used. Again, a great move by the W3C to offer a standard for users that can easily be accessed. Although the icons aren't perfectly clear without their explanations they do form a cohesive whole and work very well with the badge.
Branding a markup language sounds like a strange proposition...
but this works very well
now it will be up to developers and designers to decide if it's something they want to embrace.
- via
- underconsideration.com
The Next Open Web Platform
- HTML 5
- CSS 2.1
- CSS 3 Selectors
- CSS 3 Media Queries
- CSS 3 Text
- CSS 3 Backgrounds and Borders
- CSS 3 Colors
- CSS 3 2D Transformations
- CSS 3 3D Transformations
- CSS 3 Transitions
- CSS 3 Animations
- CSS 3 Multi-Columns
- CSS Namespaces
- SVG 1.1
- WAI-ARIA 1.0
- MathML 2.0
- ECMAScript 5
- 2D Context
- WebGL
- Web Storage
- Indexed Database
- Web Workers
- Web Sockets Protocol/API
- Geolocation
- Server-Sent Events
- Element Traversal
- DOM Level 3 Events
- Media Fragments
- XMLHttpRequest
- Selectors API
- CSSOM View Module
- Cross-Origin Resource Sharing
- File API
- RDFa
- Microdata
- WOFF
- HTTP 1.1 part 1 to part 7
- TLS 1.2 (updated)
- IRI (updated)
To see the original presentation which this repost intended ( as tribute to CSS Sensei, Eric Meyer ), but forbidden by a wimpy *Posterous inability to instantiate even the simplest CSS--inline OR external, try HERE
Accessible Rich Internet Applications||100 Specifications for the Open Web Platform and Counting »*but you can autopost it (little inside joke)