Category: zui


zui_HTML5_Badge_512_v0.1

zui HTML5/CSS3 boilerplate: structure

Where the HTML5 BoilerPlate and Normalize.css projects leave off zui boilerplate defines a specific markup structure for optimal semantics in order to maximize consistency, speed up development, and ensure stable progressive techniques are implemented without risk and minimal hassle. | read on »
share-button

Seriously though, let’s make a “SHARE” button (or not?)

My previous post about too many things to like and share was sitting as a draft for so long (a few months ;) that by the time I got around to finishing it Google had released this +1 business and Buzz was no longer just some strange relative that scares the kids at family gatherings but part of a real Google social networking deal. But for all my kidding around, why isn't there a single "SHARE" button I can put on my website? | read on »
always_add_more_link_to_excerpt

WordPress Snippet: ALWAYS show a “read more” link using the_excerpt()

Anyone who has developed a custom theme for WordPress is probably familiar with the inconsistencies of dealing with excerpts, sometimes called “more teasers”. The problem stems from the ability for the blog/site owner to be able to create excerpts in three ways: Manually type a specific excerpt using the “excerpt” data field Use the nifty “more tag” to indicate a beginning portion of the article as the excerpt-more-teaser Or do nothing at all and have them auto generated from the first few hundred characters or so And then as the theme developer you have two main (default) ways of displaying[...] | read on »
Technically accurate and annoying, Chrome doesn't find the unicode character if it doesn't exist in the fonts you've chosen

Google Chrome won’t render unicode characters

While attempting to use a groovy "star glyph" I discovered that Google Chrome was not rendering some extended unicode characters while all the other browsers I test were. Turns out Chrome isn't being helpful with extended Unicode characters but there is an easy fix for your site and your browser. | read on »
backwardscompatibility

Backwards compatibility in web development is silly!

Fed up with ten year old draft specs and DO NOT TRY THIS AT HOME warnings from other web professionals I make a perhaps infallible argument for why you should be using all the latest browser technologies (and every browser version older than a month and the people who use them can go to hell). | read on »
css3-no-vendor-specific-prefixes

No more CSS3 browser vendor specific prefixes (please)

As of today all the major browsers (mostly) support the pure straight css3 declarations for the following css3 features. And because I have gone a little bit out of my way to make my current site completely html5 without any unnecessary (or annoying) javascript hacks or unpleasant backwards compatibility concerns I have elected to forego all browser vendor prefixes for these "experimental" features. | read on »