{"id":4067,"date":"2013-10-28T14:44:20","date_gmt":"2013-10-28T19:44:20","guid":{"rendered":"http:\/\/www.encoretechresources.com\/insights\/?p=4067"},"modified":"2013-10-28T15:08:39","modified_gmt":"2013-10-28T20:08:39","slug":"analogies-for-good-content-its-smooth-for-one","status":"publish","type":"post","link":"http:\/\/www.encoretechresources.com\/insights\/2013\/10\/28\/analogies-for-good-content-its-smooth-for-one\/","title":{"rendered":"Analogies for Good Content \u2013 It’s Smooth, for One"},"content":{"rendered":"

Okay, need an excuse for being an orderly writer? You shouldn’t, but if you do, look at it from the viewpoint of the content you’re working with. Oh really?<\/p>\n

\"etw.vinishgarg.content.emotionalneeds.patchwork\"<\/a>Well, that’s what a writer named Vinish Garg suggests you do in a post<\/a> on the Enjoy Technical Writing (ETW) blog. Content, he feels, doesn’t like to be jostled around, or crammed into any place it seems it might fit. It seems to have bearings, real emotional needs, of its own. Garg uses analogies with a parking lot, a poorly patched road and a merge lane on a highway. The one we like best, that seems to fit best, is the poorly patched road.<\/p>\n

Content that doesn’t fit well, that doesn’t really belong in the place a careless writer put it, is like adding another sloppy patch to a poorly patched road. It’s not smooth, but bumpy. It causes the reader to wonder, “Does this make sense? Is it really correct? Does this really belong here?” And you don’t want to slow too much a driver whose main interest is breezing his way to understanding, or at least steering smoothly through a difficult patch. Readers, obviously, don’t like detours, roadblocks, or too many bumpy spots. <\/p>\n

That’s not to agree that content has a mind, or intent, of its own, as Vinish Garg evidently feels, only that the reader<\/em> does. He or she wants content that makes sense without too much steering. Good writing isn’t a game of bumper cars. \u2013 Doug Bedell<\/em> <\/p>\n","protected":false},"excerpt":{"rendered":"

Okay, need an excuse for being an orderly writer? You shouldn’t, but if you do, look at it from the viewpoint of the content you’re working with. Oh really? Well, that’s what a writer named Vinish Garg suggests you do in a post on the Enjoy Technical Writing (ETW) blog. Content, he feels, doesn’t like […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,3,5],"tags":[],"class_list":["post-4067","post","type-post","status-publish","format-standard","hentry","category-communication","category-technology","category-the-writing-life"],"aioseo_notices":[],"_links":{"self":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/4067"}],"collection":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/comments?post=4067"}],"version-history":[{"count":7,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/4067\/revisions"}],"predecessor-version":[{"id":4075,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/4067\/revisions\/4075"}],"wp:attachment":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/media?parent=4067"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/categories?post=4067"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/tags?post=4067"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}