<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">

<channel>
<title>InfoDesign: Understanding by Design</title>
<link>http://www.informationdesign.org/</link>
<description>Dedicated to the growth and improvement of the information experience industries.</description>
<dc:language>en-us</dc:language>
<dc:creator>plato@xs4all.nl</dc:creator>
<dc:date>2013-06-10T09:56:34+01:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=4.21-en" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>


<item>
<title>Interesting facts make web pages compelling</title>
<description>Facts, not &apos;factoids&apos;. Find &apos;Facts&apos;, replace &apos;Content&apos;.
&quot;Users hunt for facts online, so factually rich content will attract readers and keep their attention.&quot;
(Jakob Nielsen ~ Alertbox)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/06/#006853</link>
<guid isPermaLink="false">6853@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content strategy</dc:subject>

<dc:date>2013-06-10T09:56:34+01:00</dc:date>
</item>

<item>
<title>Interview with content strategy author Ann Rockley</title>
<description>Getting your hands dirty with markup for real.
&quot;Content strategists should realize that XML isn&apos;t scary and it is really powerful for doing cool things with your content. In the &apos;olden days&apos; when we first began creating Web-based content we used to have to use HTML codes to tag the content, now you create content in web forms or Word and rarely, if ever, have to think about the HTML codes. The same is true of XML, you don&apos;t have to use codes to create content, there are lots of tools that &apos;hide&apos; the XML tags. However, XML is much smarter than HTML. HTML tags describe the formatting structure of the content, XML defines the semantic structure of the content. For example, we can define that some content is a  teaser and then have the system handle it differently when published to the Web, mobile, or even print.&quot;
(Words+Pictures=Web)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/05/#006835</link>
<guid isPermaLink="false">6835@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content strategy</dc:subject>

<dc:date>2013-05-23T10:51:05+01:00</dc:date>
</item>

<item>
<title>The Governance component of content strategy success</title>
<description>The larger the organization, the more important this component becomes.
&quot;While all three components (creation, publication, governance) of the content strategy lifecycle are intended to be ongoing, it&apos;s the Governance component that often requires the most dedication due to its never ending need for attention. Once content is created and published then it will forever need to be managed, maintained, optimised and compliant which leads to the age old question of &apos;where to begin?&apos;&quot;
(Jessica O&apos;Sullivan ~ Siteimprove)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/05/#006829</link>
<guid isPermaLink="false">6829@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content strategy</dc:subject>

<dc:date>2013-05-14T17:47:47+01:00</dc:date>
</item>

<item>
<title>WYSIWTF</title>
<description>Including the notion that form (a.k.a. presentation) has meaning too.
&quot;Arguing for &apos;separation of content from presentation&apos; implies a neat division between the two. The reality, of course, is that content and form, structure and style, can never be fully separated. Anyone who&apos;s ever written a document and played around to see the impact of different fonts, heading weights, and whitespace on the way the writing flows knows this is true. Anyone who&apos;s ever squinted at HTML code, trying to parse text from tags, knows it too.&quot;
(Karen McGrane a.k.a. @karenmcgrane  ~ A List Apart)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/05/#006816</link>
<guid isPermaLink="false">6816@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content management</dc:subject>

<dc:date>2013-05-02T15:54:44+01:00</dc:date>
</item>

<item>
<title>The content strategy order of operations or &apos;Dear Aunt Sally Can Perform Magic&apos;</title>
<description>Mnemonic device for the UX disciplines: LATCH re-visited.
&quot;The reason I ask has to do with something you may remember from early math classes when coursework introduced multiple types of operations. There needed to be a set of rules in place so that little Jimmy would know whether or not multiplication happens before or after subtraction. Enter the Order of Operations, a.k.a &apos;Please Excuse My Dear Aunt Sally&apos;.&quot;
(Tom Harari a.k.a. @tomharari ~ iAcquire)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/04/#006798</link>
<guid isPermaLink="false">6798@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content strategy</dc:subject>

<dc:date>2013-04-12T16:41:32+01:00</dc:date>
</item>

<item>
<title>The three components of content strategy success</title>
<description>Reducing the essence of content strategy to a holy trinity: create, publish, and govern.
&quot;Creating effective website content can be an arduous task, especially when so many factors must be considered: varying role capacities, internal politics, customer expectations etc. However, following a structured strategy can make creating focused content a piece of cake!&quot;
(Jessica O&apos;Sullivan ~ SiteImprove)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/03/#006779</link>
<guid isPermaLink="false">6779@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content management</dc:subject>

<dc:date>2013-03-27T12:47:33+01:00</dc:date>
</item>

<item>
<title>The five elements of modular and adaptive content</title>
<description>Object orientation moving up the ladder. Now, it&apos;s entering the info layer.
&quot;When the word modular comes up in a conversation about web design, it&apos;s usually in regards to the code. Object oriented programming on the backend, separating structure, presentation, and behavior on the front end, or perhaps the reuse of certain visual patterns like buttons across the site. However, if we&apos;re going to spend some time talking about modularity in web design our first stop, like everything else web design, should be the content.&quot;
(Steven Bradley a.k.a. @vangogh ~ Vanseo Design)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/02/#006737</link>
<guid isPermaLink="false">6737@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content strategy</dc:subject>

<dc:date>2013-02-18T11:57:20+01:00</dc:date>
</item>

<item>
<title>Content strategy: Separating content from information</title>
<description>A kind of new style DIKW and DTDT thinking with &quot;(...) describes what content really is.&quot;
&quot;Content is a piece of information we want to share with our audience. We create content by turning a piece of information into a type that our audience is familiar with. Then we distribute that content on the channels where we think our target audiences spend their time.&quot;
(Ahava Leibtag a.k.a. @ahaval)
</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/02/#006729</link>
<guid isPermaLink="false">6729@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content strategy</dc:subject>

<dc:date>2013-02-13T10:28:39+01:00</dc:date>
</item>

<item>
<title>A history of content management in two humps</title>
<description>Desperately hoping CM and CMSs get consumerized as well.
&quot;One last thing that end-users need to keep in mind as they think about solutions that are migrating from the consumer world to the enterprise world. A consumer application is not necessarily battle hardened for enterprise use.&quot;
(Digital landfill)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/02/#006724</link>
<guid isPermaLink="false">6724@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content management</dc:subject>

<dc:date>2013-02-07T14:56:20+01:00</dc:date>
</item>

<item>
<title>What to expect from a content strategy process</title>
<description>Testimonial for content strategy, the Canadian way.
&quot;Content strategy is the most important part of your project. It is where you plan what to put into the website, trade publication, brochure, catalog, fifty foot outdoor advertisement, or whatever. Some companies do content strategy intuitively, but most need a lot of help. Enter the content strategist.&quot;
(Darcy Hastings a.k.a. @bioagency ~ BIO digital)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/02/#006723</link>
<guid isPermaLink="false">6723@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content strategy</dc:subject>

<dc:date>2013-02-07T14:40:09+01:00</dc:date>
</item>

<item>
<title>&quot;All of the work we do is change management&quot;</title>
<description>Karens star is rising and rising.
Interview with Karen McGrane. ~ &quot;For us this is a generational issue, and it&apos;s our life&apos;s work to help contribute to organizations’ learning how digital design (and information architecture) should fit into their organization. If we are going to be successful, we may not fix it for ourselves, but for the next generation of digital designers, I want to leave those organizations better off. There will also be some social darwinism, where the organizations that successfully navigate this transition are the ones that are going to survive.&quot;
(IA Summit 2013)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/02/#006721</link>
<guid isPermaLink="false">6721@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content strategy</dc:subject>

<dc:date>2013-02-05T11:58:17+01:00</dc:date>
</item>

<item>
<title>Three digital governance challenges</title>
<description>Embedding in the existing organization. A big challenge for UX and CX management and staff.
&quot;It&apos;s time to leave the web sandbox and lead the organization into a deeper understanding of the power and use of digital channels. It&apos;s time to inform and engage executives so that organizational expectations are reasonable and that they&apos;re supported culturally and fiscally. So maybe you can clean up the mess in six months - but it&apos;s going to take a lot of resources and a cultural shift that can probably only be directed from an executive level. Most likely though, tough &apos;redesigns&apos; are going to be ongoing evolutions.&quot;
(Lisa Welchman a.k.a. @lwelchman ~ WelchmanPierpoint)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/01/#006714</link>
<guid isPermaLink="false">6714@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content management</dc:subject>

<dc:date>2013-01-30T14:47:06+01:00</dc:date>
</item>

<item>
<title>We must remove publishing and content management concerns from authoring systems</title>
<description>We tend to forget how important the content infrastructure and technology is.
&quot;They create a language to express publishing, content management, or reuse concerns, and then expect writers to write directly into what is really an internal content management format. Putting a graphical face over the markup does nothing to change this. The graphical interface only hides the syntax of the XML. It does nothing to change the fact that authors are being asked to create what should be the internal semantics of the publishing system — semantics they generally neither care about nor understand.&quot;
(Mark Baker ~ EveryPageIsOne)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/01/#006712</link>
<guid isPermaLink="false">6712@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content management</dc:subject>

<dc:date>2013-01-30T10:03:53+01:00</dc:date>
</item>

<item>
<title>The evolution of technical communication</title>
<description>Information management and technical communication appear to be the parents of content strategy.
&quot;Over the years technical communication has transitioned from a conventional author-reader engagement to a realm of social collaboration. Let&apos;s take a look at how technical communication has progressed over time and the significant milestones along the way.&quot;
(Monalisa Sen and Debarshi Gupta Biswas ~ tcworld)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2013/01/#006693</link>
<guid isPermaLink="false">6693@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content strategy</dc:subject>

<dc:date>2013-01-09T13:50:21+01:00</dc:date>
</item>

<item>
<title>Content Planning Demystified</title>
<description>Without a plan, no project. Without a plan, no modification of the planning.
&quot;It turns out that the only real way to avoid a trainwreck with editorial work is to get ahead of the trouble, line everything up carefully, and leave oodles of room for all the pieces to connect on time. The same is true of content strategy, content planning, and just about everything to do with content on the web, except for the writing itself – and that, too, usually takes far longer than anyone expects. If you’re not a professional editor and you suddenly find yourself dealing with content creation, you’re almost certainly going to underestimate the time and effort involved, or to skip something important in the planning process that pops up to bite you later.&quot;
(Erin Kissane a.k.a. @kissane ~ 24ways)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2012/12/#006682</link>
<guid isPermaLink="false">6682@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Content strategy</dc:subject>

<dc:date>2012-12-21T09:46:43+01:00</dc:date>
</item>


</channel>
</rss>