<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Design Your Content ~ Part 2</title>
	<link>http://fadtastic.net/2007/04/11/design-your-content-part-2/</link>
	<description>thoughts on &#124; comments about &#124; examples of  } web design trends.</description>
	<pubDate>Fri, 16 May 2008 19:15:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Ted Goas</title>
		<link>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-38978</link>
		<author>Ted Goas</author>
		<pubDate>Wed, 11 Apr 2007 18:44:17 +0000</pubDate>
		<guid>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-38978</guid>
					<description>Great article Andrew. I agree that longer articles should use H-tags to break out the content into smaller sections.

What about lists (unordered and definition)? I'd like to hear some reader thoughts on when to use (and how to style) lists in content. I think lists are easier to read through quickly, as content can often be consolidated and abbreviated while still getting the entire message across.</description>
		<content:encoded><![CDATA[<p>Great article Andrew. I agree that longer articles should use H-tags to break out the content into smaller sections.</p>
<p>What about lists (unordered and definition)? I&#8217;d like to hear some reader thoughts on when to use (and how to style) lists in content. I think lists are easier to read through quickly, as content can often be consolidated and abbreviated while still getting the entire message across.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Aaron</title>
		<link>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-38981</link>
		<author>Aaron</author>
		<pubDate>Wed, 11 Apr 2007 18:52:05 +0000</pubDate>
		<guid>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-38981</guid>
					<description>Superb article! Lots of great tips and information.

However, your comparison with newspaper articles is a contentious one and I'm sure many newspaper editors would disagree with your point about headers. 

Layout on the web and layout in the printed press (especially newspapers) are two entirely different sciences. Even the writing style is different.

I agree sub-headings on the web are a good thing. In print, there's just not enough precious column inches to waste the space!

The three articles you link to are not written for the web, they're written for print.</description>
		<content:encoded><![CDATA[<p>Superb article! Lots of great tips and information.</p>
<p>However, your comparison with newspaper articles is a contentious one and I&#8217;m sure many newspaper editors would disagree with your point about headers. </p>
<p>Layout on the web and layout in the printed press (especially newspapers) are two entirely different sciences. Even the writing style is different.</p>
<p>I agree sub-headings on the web are a good thing. In print, there&#8217;s just not enough precious column inches to waste the space!</p>
<p>The three articles you link to are not written for the web, they&#8217;re written for print.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Andrew Faulkner</title>
		<link>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-38989</link>
		<author>Andrew Faulkner</author>
		<pubDate>Wed, 11 Apr 2007 19:46:02 +0000</pubDate>
		<guid>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-38989</guid>
					<description>Thanks for the praise.

Ted, thanks for the list suggestion. I agree - a list can be used to present information in bite-size chunks to the reader.

Aaron, I don't want to dwell too much on the header issue but here's my view:

I agree that (sub)headers may not be fit for newspaper print, but the sites in the examples were all web versions of national newspapers. I didn't aim to compare web and print.

&lt;blockquote&gt;The three articles you link to are not written for the web, they’re written for print.&lt;/blockquote&gt;

Whether they are written for print or not (I think these are web only stories), surely it would take minimal effort to put headers into the online version? When putting print material onto the web, the material should use the web to its strengths not simply copy the story online. But that's a different article. ;)</description>
		<content:encoded><![CDATA[<p>Thanks for the praise.</p>
<p>Ted, thanks for the list suggestion. I agree - a list can be used to present information in bite-size chunks to the reader.</p>
<p>Aaron, I don&#8217;t want to dwell too much on the header issue but here&#8217;s my view:</p>
<p>I agree that (sub)headers may not be fit for newspaper print, but the sites in the examples were all web versions of national newspapers. I didn&#8217;t aim to compare web and print.</p>
<blockquote><p>The three articles you link to are not written for the web, they’re written for print.</p>
</blockquote>
<p>Whether they are written for print or not (I think these are web only stories), surely it would take minimal effort to put headers into the online version? When putting print material onto the web, the material should use the web to its strengths not simply copy the story online. But that&#8217;s a different article. ;)</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Christian Watson</title>
		<link>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-38992</link>
		<author>Christian Watson</author>
		<pubDate>Wed, 11 Apr 2007 20:38:34 +0000</pubDate>
		<guid>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-38992</guid>
					<description>Great points! Doing more with content and typography in order to optimize presentation and readability is something that is very important to me and is all-too-often overlooked.

Regarding your points about quotes, you might want to check out my &lt;a href="http://www.smileycat.com/miaow/archives/000632.php" rel="nofollow"&gt;pull-quote design showcase&lt;/a&gt;, which provides some examples of creative pull-quote styling.</description>
		<content:encoded><![CDATA[<p>Great points! Doing more with content and typography in order to optimize presentation and readability is something that is very important to me and is all-too-often overlooked.</p>
<p>Regarding your points about quotes, you might want to check out my <a href="http://www.smileycat.com/miaow/archives/000632.php" rel="nofollow">pull-quote design showcase</a>, which provides some examples of creative pull-quote styling.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: wotaewer</title>
		<link>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-39007</link>
		<author>wotaewer</author>
		<pubDate>Wed, 11 Apr 2007 21:47:38 +0000</pubDate>
		<guid>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-39007</guid>
					<description>Nice wrap-up, even though I think the title "design your content" goes a bit in different direction. I was expecting somthing rather user-oriented not developer-oriented. 

In times of css its pretty easy to make anythink look like a header. What you talk about, especially on headers, is more a question of web standards. 

I would find it interesting how to "design" your h1-h6 and your p tags and so forth, so that your content becomes more readible.

I for example have trouble scanning through your article because I have the feeling its visually not well structured. You have main-headers which have sub-headers which differ only in font-size, which makes them a bit hard to differentiate. It all looks kind of the same...</description>
		<content:encoded><![CDATA[<p>Nice wrap-up, even though I think the title &#8220;design your content&#8221; goes a bit in different direction. I was expecting somthing rather user-oriented not developer-oriented. </p>
<p>In times of css its pretty easy to make anythink look like a header. What you talk about, especially on headers, is more a question of web standards. </p>
<p>I would find it interesting how to &#8220;design&#8221; your h1-h6 and your p tags and so forth, so that your content becomes more readible.</p>
<p>I for example have trouble scanning through your article because I have the feeling its visually not well structured. You have main-headers which have sub-headers which differ only in font-size, which makes them a bit hard to differentiate. It all looks kind of the same&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ted Goas</title>
		<link>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-39069</link>
		<author>Ted Goas</author>
		<pubDate>Thu, 12 Apr 2007 04:32:41 +0000</pubDate>
		<guid>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-39069</guid>
					<description>&lt;em&gt;wotaewer&lt;/em&gt;, I understand what you mean. I thought the same thing when reading the first installment of this series. Perhaps this idea of 'designing' content could be the topic of another article. Using icons, thumbnails, backgrounds, border, etc. in the content elements instead of just the header/footer/sidebar layout. Designing content can be a great way to keep the reader's attention, so long as it's done properly and not over-designed.

Anyone up for it?</description>
		<content:encoded><![CDATA[<p><em>wotaewer</em>, I understand what you mean. I thought the same thing when reading the first installment of this series. Perhaps this idea of &#8216;designing&#8217; content could be the topic of another article. Using icons, thumbnails, backgrounds, border, etc. in the content elements instead of just the header/footer/sidebar layout. Designing content can be a great way to keep the reader&#8217;s attention, so long as it&#8217;s done properly and not over-designed.</p>
<p>Anyone up for it?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Andrew Faulkner</title>
		<link>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-39091</link>
		<author>Andrew Faulkner</author>
		<pubDate>Thu, 12 Apr 2007 08:06:46 +0000</pubDate>
		<guid>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-39091</guid>
					<description>Wotaewer, thanks for the feedback. It's appreciated. I think with Ted's and your comments taken onboard, I'll write a Part 3 showing how to visually design the content.

Cheers guys.</description>
		<content:encoded><![CDATA[<p>Wotaewer, thanks for the feedback. It&#8217;s appreciated. I think with Ted&#8217;s and your comments taken onboard, I&#8217;ll write a Part 3 showing how to visually design the content.</p>
<p>Cheers guys.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: wotaewer</title>
		<link>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-39381</link>
		<author>wotaewer</author>
		<pubDate>Fri, 13 Apr 2007 21:42:09 +0000</pubDate>
		<guid>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-39381</guid>
					<description>great, Andrew; looking forward to it.

@ Ted: constantly working on it and trying hard ;)</description>
		<content:encoded><![CDATA[<p>great, Andrew; looking forward to it.</p>
<p>@ Ted: constantly working on it and trying hard ;)</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Lisa</title>
		<link>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-42853</link>
		<author>Lisa</author>
		<pubDate>Mon, 30 Apr 2007 21:25:39 +0000</pubDate>
		<guid>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-42853</guid>
					<description>At our paper, the process that exports print content as XML drops style tags indicating subheads, which consequently present on our site as plain text. It is our practice to manually style these &lt;em&gt;whenever possible&lt;/em&gt;, as seeing them as regular text is even more confusing than not having them at all. 

We are starting over with a new CMS, but now although our legacy systems are being upgraded to allow subheads to be noted in the XML, the programmers on the web development side are loathe to style tag anything other than headline, byline, caption and text. 

This leaves web producers the only option of manually scanning a large quantity of stories daily in order to catch these things. Visually helpful? Absolutely. Workflow efficient? Not really. 

Your suggestions are fantastic and I agree with all you have said, but unfortunately are backburnered when handling large loads of content.</description>
		<content:encoded><![CDATA[<p>At our paper, the process that exports print content as XML drops style tags indicating subheads, which consequently present on our site as plain text. It is our practice to manually style these <em>whenever possible</em>, as seeing them as regular text is even more confusing than not having them at all. </p>
<p>We are starting over with a new CMS, but now although our legacy systems are being upgraded to allow subheads to be noted in the XML, the programmers on the web development side are loathe to style tag anything other than headline, byline, caption and text. </p>
<p>This leaves web producers the only option of manually scanning a large quantity of stories daily in order to catch these things. Visually helpful? Absolutely. Workflow efficient? Not really. </p>
<p>Your suggestions are fantastic and I agree with all you have said, but unfortunately are backburnered when handling large loads of content.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Andrew Faulkner</title>
		<link>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-42954</link>
		<author>Andrew Faulkner</author>
		<pubDate>Tue, 01 May 2007 11:20:49 +0000</pubDate>
		<guid>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-42954</guid>
					<description>Lisa,

Thanks for the honest insights into some of the issues for news editors. This article wasn't meant to be a complete criticism of online newspapers in general, more of a suggestion of ideas for those lacking in visual sparkle.

&lt;blockquote&gt;We are starting over with a new CMS, but now although our legacy systems are being upgraded to allow subheads to be noted in the XML, the programmers on the web development side are loathe to style tag anything other than headline, byline, caption and text.

This leaves web producers the only option of manually scanning a large quantity of stories daily in order to catch these things. Visually helpful? Absolutely. Workflow efficient? Not really. &lt;/blockquote&gt;

This boils down to technology, I know. I agree that if it takes, let's say, an hour just to style the headers, it isn't efficient enough to warrant the effort. And the story will probably not get out onto the web faster than competitors' stories.

With XML delivering the different aspects of your articles, it surely isn't a large step to control the style of what it outputs. Unless I'm misunderstanding you, you could develop a set of CSS rules that style every single article automatically as required with minimal effort?</description>
		<content:encoded><![CDATA[<p>Lisa,</p>
<p>Thanks for the honest insights into some of the issues for news editors. This article wasn&#8217;t meant to be a complete criticism of online newspapers in general, more of a suggestion of ideas for those lacking in visual sparkle.</p>
<blockquote><p>We are starting over with a new CMS, but now although our legacy systems are being upgraded to allow subheads to be noted in the XML, the programmers on the web development side are loathe to style tag anything other than headline, byline, caption and text.</p>
<p>This leaves web producers the only option of manually scanning a large quantity of stories daily in order to catch these things. Visually helpful? Absolutely. Workflow efficient? Not really. </p>
</blockquote>
<p>This boils down to technology, I know. I agree that if it takes, let&#8217;s say, an hour just to style the headers, it isn&#8217;t efficient enough to warrant the effort. And the story will probably not get out onto the web faster than competitors&#8217; stories.</p>
<p>With XML delivering the different aspects of your articles, it surely isn&#8217;t a large step to control the style of what it outputs. Unless I&#8217;m misunderstanding you, you could develop a set of CSS rules that style every single article automatically as required with minimal effort?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: am Design &#187; Arkisto &#187; Artikkelikatsaus: Maaliskuu 2007</title>
		<link>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-54136</link>
		<author>am Design &#187; Arkisto &#187; Artikkelikatsaus: Maaliskuu 2007</author>
		<pubDate>Sun, 10 Jun 2007 11:09:35 +0000</pubDate>
		<guid>http://fadtastic.net/2007/04/11/design-your-content-part-2/#comment-54136</guid>
					<description>[...] rusetti. Vaikka Andrew Faulknerin / fadtasticin artikkelisarjan Design Your Content (Part 1 &#124; Part 2) jälkimmäinen osa ilmestyi vasta huhtikuussa, on sarja kokonaisuutena maaliskuun [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] rusetti. Vaikka Andrew Faulknerin / fadtasticin artikkelisarjan Design Your Content (Part 1 | Part 2) jälkimmäinen osa ilmestyi vasta huhtikuussa, on sarja kokonaisuutena maaliskuun [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
