|
|
content. In many ways, COPE content is ideal. (product description, specs, definitions, images), the system can pull (rather than paste) that chunk into multiple deliverables. When you update the source, the update propagates throughout the repository. COPE content is elegant. It's efficient. It's logical. This saves companies millions of dollars in translation costs. It helps them avoid embarrassing, crazy, and litigious contradictions. COPE works well with text, audio, and video (if you use YouTube). Still, there are cases where COPE is the wrong method.
Modern browsers reflow text, but images are scaled down to fit the device. An image that looks great on a desktop may become unrecognizable on a smartphone. (Hello, pinch and zoom.) That's where the M from Special Database COPE-M comes in. “Preparing content for multichannel reuse is a good goal, but not all content scales effectively with the COPE model,” says Buddy. According to BuddyScalera, Create Once, Publish Anywhere (COPE) is often the wrong way to handle images. intelcontentClick to Tweet This article summarizes advice from Buddy's ICC talk. All images in this post are from his slides, and unless otherwise noted, all quotes are from his talk and subsequent conversations with him. Hand-picked related content: 11 ways to dominate the social scene with killer content Why some images are difficult to deal with Buddy drops what he calls a "truth bomb" about images: They are not the same as text.
Text is suitable for single sourcing because it can be separated from its appearance. Cascading style sheets allow text to look different in each instance without changing the underlying text source. "Text is a wonderful, flexible, flowable, reusable, channel-agnostic asset that works well in the digital world," he says. This is not the case in the image. They cannot be separated from their appearance. When it comes to images, one size doesn't necessarily fit all. As Justyn Hornor stated a few years ago, the "elephant in the room" in responsive web design is "how images are handled." A small image can look sharp on a mobile phone and look ridiculously small on a high-resolution monitor. Large images may take a long time to render on small devices where small images are sufficient. According to jphornor,
|
|
發表於 13:57:59