11 Reasons Why Responsive Design Isn’t That Cool!

Juan Pablo Sarmiento – 11 Reasons Why Responsive Design Isn’t That Cool!:

“Viewing a responsive website on a mobile device forces the CPU and memory of it while resizing images because you are downloading a large image, uncompressing it in your phone’s memory and then resizing it to fit a small screen.

[…] CSS media queries work incredibly well hiding things, but not that well removing them. CSS media queries won’t remove any unnecessary script or html you won’t use on mobile or desktop versions. It just leaves it there: hidden.

[…] Recognizing the mobile context is not just to be aware of the difference between screen sizes. Responsive Web Design does not recognize the mobile context because it just adequates a website to fit a screen, but it omits key mobile features.”

(Via Christiaan W. Lustig)

Sat, 01 Sep 2012 21:01:58 +0000

Managing Metadata - Any Volunteers?

Erik Hartman at CMSWire – Managing Metadata - Any Volunteers?:

“Librarians and archivists for that matter, are academically trained in using metadata for retrieval and reuse. Though well equipped for the task, most librarians are quite invisible to the web team and on the verge of being fired due to budget cuts. These people can be very valuable for your web team, so keep these specialists on board whenever possible.

I think there should be an overseer for metadata, be it a metator, content librarian, content analyst, metadata specialist, meta champion or any other dedicated role. Metadata has too much impact on an organization's online success to be handed over to a group of editors and/or subject matter experts (SMEs) with no insight in each other's work.”

Thu, 30 Aug 2012 18:15:34 +0000

What I wanted, part II

Dave Winer – What I wanted, part II:

“This was a secret of mine, because most of my competitors not only didn't listen to their users, but they didn't even use their own products. […] Be both a user and a developer. That way you understand users, and you can make their dreams come true, because they are your dreams too. The reward for that is success.”

Tue, 28 Aug 2012 14:44:56 +0000


Dave Winer – Respect:

I respect people who ship software that's open to competition, and then write specs to show people how to compete with them.

It's just like the web. People come back to places that send them away.”

Mon, 27 Aug 2012 20:20:46 +0000

The Service Economy and the New Role of the Enterprise CMS

Craig Malloy on CMS Wire – The Service Economy and the New Role of the Enterprise CMS:

“Employees are choosing their own productivity applications and the adoption rates are putting even some of the most successful enterprise applications to shame.

The traditional enterprise content management market can do little to stop this. And few consumer-workers will choose a heavy IT-centric content management system over newer, cooler options that have consumer technology DNA at their core.”

Mon, 27 Aug 2012 20:38:48 +0000

Rewarding Work

Scott Adams – Rewarding Work:

“Whenever you see the x-factor in someone's output - that little extra something that turns the good into the awesome - it's a marker for intrinsic motivation. […] To get to awesome you need to think you might be changing the world, saving lives, redeeming your reputation, attracting the mate of your dreams, or something else that is emotionally large.”

Mon, 27 Aug 2012 20:27:00 +0000

Big Experience Management? Coping With The Hype Cycle

Matt Mullen at Real Story Group – Big Experience Management? Coping With The Hype Cycle:

“There is something really important to consider here; namely that the there is an increasing gap between the what vendors are pushing as important and what real customer use cases actually demand.

[…] It surely makes sense to revisit possible solutions, just remember to focus on what your organization truly requires, rather than aligning with vendor buzzwords.”

Mon, 20 Aug 2012 08:11:00 +0000

Why Agile Fails

Matthias Marschall – Why Agile Fails:

“Agile will begin casting bright spotlights on these weak spots in your development process. The rug that everyone has been sweeping under for the past decade is suddenly lifted and the dark, scurrying truths see the light of day. People don’t care much for harsh truths, and when they see you holding the spotlight they’ll probably tell you to turn the damn thing off!

[…] Turn off the light, lay down the rug – let peace and prosperity reign over the Kindgom of Ignorance once again.”

Fri, 17 Aug 2012 10:20:47 +0000


Redactor is the most fantastic yet beautiful and easy-to-use WYSIWYG editor on jQuery. It is lightning fast, small, scalable, and powerful.”

Fri, 17 Aug 2012 10:30:19 +0000

Beware user experience overreach in your website overhaul

Tony Byrne at the Real Story Group – Beware user experience overreach in your website overhaul:

“In lieu of shelfware, you can end up with shelfscreens: planned user experiences that you never roll out. […]

1. Here's the operational maturity and ongoing staff education you'll require […]

3. Here's the metadata savvy (and consistency!) you'll have to sustain across your enterprise […]

8. Here's the performance hit at runtime […]

Just take the same critical eye to the practicality of proposed UX plans as you would to the suitability of any new software you introduce into the enterprise. Ask for that checklist.”

Wed, 15 Aug 2012 12:39:34 +0000

Finally — an XML Markup Solution for Design-Based Publishers: Introducing the PRISM Source Vocabulary

Dianne Kennedy – Finally — an XML Markup Solution for Design-Based Publishers: Introducing the PRISM Source Vocabulary:

“Until the tablet-publishing tsunami hit, design-based publications were able to justify their labor-intensive design-based publication process.

[…] We have come to believe the Source is the Solution. We must capture and store platform-agnostic content as early as possible.

[…] Source content must be semantically rich enough to enable the publisher to select content and automate layout and delivery to a wide variety of publishing platform in platform-native formats.

[…] In order to refine what we mean by the generic term article, the PRISM Content Type Controlled Vocabulary has been developed. […] Some content types that describe the unit-of-storage include an advertisement, article, blog entry, book chapter, cover, masthead, introduction and navigational aid.

[…] The Where Used metadata block allows for usage tracking. […] PSV allows for tracking the platform and even the device where the content was published. PSV also allows for tracking the section or page of the publication where the content appeared. Altogether, PSV offers nearly 40 optional fields to describe where content was used.

[…] The Usage Rights metadata block provides optional metadata fields that can be used by publishers to track usage rights of content in a repository. The 15 optional metadata fields in this block are based on the PRISM Usage Rights Metadata Specification.

[…] Unlike EPUB3, PSV makes no extensions to HTML5 and has no restrictions. PSV recommends that the new HTML5 <article tag be used as the root element for any content unit.

[…] PSV recommends a number of PRISM semantic classes that you can use to qualify any HTML5 element. Examples include box, caption, dateline, credit, and pull quote.”

(Via Simon St. Laurent at O’Reilly Radar – Applying markup to complexity).

Thu, 09 Aug 2012 19:41:40 +0000

Using HTML as the Media Type for your API

Jon Moore – Using HTML as the Media Type for your API:

“There are actually a variety of reasons I prefer using HTML:

rich semantics
hypermedia support
already standardized
tooling support”

Update: See my post on HTML Hypermedia API resources.

Thu, 09 Aug 2012 07:32:50 +0000