<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Drupal.org redesign &#8211; a strategy for the documentation section</title>
	<atom:link href="http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/</link>
	<description>pretty design pending</description>
	<lastBuildDate>Mon, 15 Feb 2010 23:30:46 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dru29</title>
		<link>http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/comment-page-1/#comment-247820</link>
		<dc:creator>dru29</dc:creator>
		<pubDate>Fri, 01 May 2009 04:10:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/?p=657#comment-247820</guid>
		<description>Can anyone direct me to a Drupal theme for people with disabilities?
And, is there a Drupal group with members of
the Alliance for Technology Access?
http://www.ataccess.org/

Thanks,

dru29 (a newbie)
dru29@drupal.org</description>
		<content:encoded><![CDATA[<p>Can anyone direct me to a Drupal theme for people with disabilities?<br />
And, is there a Drupal group with members of<br />
the Alliance for Technology Access?<br />
<a href="http://www.ataccess.org/" rel="nofollow">http://www.ataccess.org/</a></p>
<p>Thanks,</p>
<p>dru29 (a newbie)<br />
<a href="mailto:dru29@drupal.org">dru29@drupal.org</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Howard</title>
		<link>http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/comment-page-1/#comment-177657</link>
		<dc:creator>Andy Howard</dc:creator>
		<pubDate>Fri, 19 Dec 2008 14:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/?p=657#comment-177657</guid>
		<description>Really enjoyed this post Leisa. I like your approach to documentation, and I also like your approach to collaborating with Mark. It&#039;s got me thinking - for this project, were you typically communicating to Mark with verbal/chat along with lo-fi wireframes and sketches? You guys have been pretty fast with iterations, and your process have got me thinking. Would love to see a post on the project process in some more detail!</description>
		<content:encoded><![CDATA[<p>Really enjoyed this post Leisa. I like your approach to documentation, and I also like your approach to collaborating with Mark. It&#8217;s got me thinking &#8211; for this project, were you typically communicating to Mark with verbal/chat along with lo-fi wireframes and sketches? You guys have been pretty fast with iterations, and your process have got me thinking. Would love to see a post on the project process in some more detail!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vm</title>
		<link>http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/comment-page-1/#comment-175387</link>
		<dc:creator>vm</dc:creator>
		<pubDate>Fri, 12 Dec 2008 10:17:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/?p=657#comment-175387</guid>
		<description>(Perhaps this is not the right thread)

Modules should have a user&#039;s manual section. Now modules have the documentation link, which is useless. The maintainer of the manual could be the module developer or someone else. Others could help in writing the manual by simply commenting the manual node. A demo site or at least a captured image(s) of what the module does, would be nice to get the main idea quickly. These could be added by others also.

Themes should have a data sheet (in table form?). Comparison option of selected themes would be nice, but not necessary. At least a large captured image of a theme should be &quot;mandatory&quot;.

These changes would be easy to make.</description>
		<content:encoded><![CDATA[<p>(Perhaps this is not the right thread)</p>
<p>Modules should have a user&#8217;s manual section. Now modules have the documentation link, which is useless. The maintainer of the manual could be the module developer or someone else. Others could help in writing the manual by simply commenting the manual node. A demo site or at least a captured image(s) of what the module does, would be nice to get the main idea quickly. These could be added by others also.</p>
<p>Themes should have a data sheet (in table form?). Comparison option of selected themes would be nice, but not necessary. At least a large captured image of a theme should be &#8220;mandatory&#8221;.</p>
<p>These changes would be easy to make.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leisa.reichelt</title>
		<link>http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/comment-page-1/#comment-171365</link>
		<dc:creator>leisa.reichelt</dc:creator>
		<pubDate>Mon, 24 Nov 2008 12:43:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/?p=657#comment-171365</guid>
		<description>if you haven&#039;t had the chance to check out the prototype version of this it is now online here: http://drupal.markboultondesign.com/iteration9/documentation.html

note: we&#039;ve already sketched up some amends to this, but do let me know if you have any more feedback!

thanks again for your thoughtful feedback.
Leisa</description>
		<content:encoded><![CDATA[<p>if you haven&#8217;t had the chance to check out the prototype version of this it is now online here: <a href="http://drupal.markboultondesign.com/iteration9/documentation.html" rel="nofollow">http://drupal.markboultondesign.com/iteration9/documentation.html</a></p>
<p>note: we&#8217;ve already sketched up some amends to this, but do let me know if you have any more feedback!</p>
<p>thanks again for your thoughtful feedback.<br />
Leisa</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: random-points</title>
		<link>http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/comment-page-1/#comment-170627</link>
		<dc:creator>random-points</dc:creator>
		<pubDate>Fri, 21 Nov 2008 14:02:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/?p=657#comment-170627</guid>
		<description>Some random points ....
.. Has the search function improved in the backend of drupal ?

.. Drupal documentation, as it  appeared to me, unlike the hype, was / is actually quite useful and structurally  nicely laid , only thing people were/are jumping at the forum without really going through the docu.s even minimally   --&gt; perhaps a knowledge-base type thing that prompted a relevant link to a relevant pieces from the docu.s before a forum post or issue is submitted could help

.. apart from &#039;cardsorting&#039; and classification or non-classification of things &#039;documentaion&#039; per se can be champion when the actual documentation follows or imbibes the details, including text and static images, describing things to such details that makes drupal books really redundant ... till then there will be some or other &#039;complaints&#039; of insufficiency of docu.s</description>
		<content:encoded><![CDATA[<p>Some random points &#8230;.<br />
.. Has the search function improved in the backend of drupal ?</p>
<p>.. Drupal documentation, as it  appeared to me, unlike the hype, was / is actually quite useful and structurally  nicely laid , only thing people were/are jumping at the forum without really going through the docu.s even minimally   &#8211;&gt; perhaps a knowledge-base type thing that prompted a relevant link to a relevant pieces from the docu.s before a forum post or issue is submitted could help</p>
<p>.. apart from &#8216;cardsorting&#8217; and classification or non-classification of things &#8216;documentaion&#8217; per se can be champion when the actual documentation follows or imbibes the details, including text and static images, describing things to such details that makes drupal books really redundant &#8230; till then there will be some or other &#8216;complaints&#8217; of insufficiency of docu.s</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Megan</title>
		<link>http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/comment-page-1/#comment-170522</link>
		<dc:creator>Megan</dc:creator>
		<pubDate>Thu, 20 Nov 2008 18:39:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/?p=657#comment-170522</guid>
		<description>I like the IA plan overall, and I&#039;m looking forward to having a place to start when I start learning drupal, since that is my plan.  I&#039;m curious, when you say that you don&#039;t to show where the documentation is incomplete, where the holes are, I wonder whether that leaves people searching for something in vain, thinking they are searching incorrectly.  Is there some way to highlight where the incomplete sections are that need community contributions, so people know if they have reached a dead end?</description>
		<content:encoded><![CDATA[<p>I like the IA plan overall, and I&#8217;m looking forward to having a place to start when I start learning drupal, since that is my plan.  I&#8217;m curious, when you say that you don&#8217;t to show where the documentation is incomplete, where the holes are, I wonder whether that leaves people searching for something in vain, thinking they are searching incorrectly.  Is there some way to highlight where the incomplete sections are that need community contributions, so people know if they have reached a dead end?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leisa.reichelt</title>
		<link>http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/comment-page-1/#comment-170503</link>
		<dc:creator>leisa.reichelt</dc:creator>
		<pubDate>Thu, 20 Nov 2008 16:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/?p=657#comment-170503</guid>
		<description>@worldfallz - I couldn&#039;t agree with you more. In fact, the need that newbies have for structured, handholding documentation is a big part of the rationale behind the strategy as I had hoped to outline in the conversation I&#039;d posted.

By allowing people who know what they&#039;re looking for to search, we can then give over important pages like the Documentation landing page entirely to supporting newbies.

I&#039;ve also made an allowance for a special type of content, which I&#039;ve called &#039;designed content&#039; which is all about a more linear and structured pathway through content to support people who need this more scaffolded learning style.

so, i can&#039;t help but think, we&#039;re actually on the same page with this.

at any rate - the next iteration is going to be available in a few short hours I believe, so we can have a play with it there and see what we think.

thanks again to everyone for such thoughtful feedback</description>
		<content:encoded><![CDATA[<p>@worldfallz &#8211; I couldn&#8217;t agree with you more. In fact, the need that newbies have for structured, handholding documentation is a big part of the rationale behind the strategy as I had hoped to outline in the conversation I&#8217;d posted.</p>
<p>By allowing people who know what they&#8217;re looking for to search, we can then give over important pages like the Documentation landing page entirely to supporting newbies.</p>
<p>I&#8217;ve also made an allowance for a special type of content, which I&#8217;ve called &#8216;designed content&#8217; which is all about a more linear and structured pathway through content to support people who need this more scaffolded learning style.</p>
<p>so, i can&#8217;t help but think, we&#8217;re actually on the same page with this.</p>
<p>at any rate &#8211; the next iteration is going to be available in a few short hours I believe, so we can have a play with it there and see what we think.</p>
<p>thanks again to everyone for such thoughtful feedback</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: worldfallz</title>
		<link>http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/comment-page-1/#comment-170470</link>
		<dc:creator>worldfallz</dc:creator>
		<pubDate>Thu, 20 Nov 2008 15:35:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/?p=657#comment-170470</guid>
		<description>It&#039;s definitely NOT an either / or discussion-- we  absolutely do need both. I perceived the original suggestions as recommending using only a wiki style documentation and completely abandoning hierarchy-- which I still think is a mistake.

And while searching is very much a sore spot and desperately needs to be improved, the chief complaint I see when providing support in the forums to real newbies (as opposed to developers who are just new to drupal) is that they simply can&#039;t figure out how to get started. That reflects a complete failure of guided learning that randomly wandering around a wiki will not solve.

Getting started is not done with search-- it&#039;s done with guided browsing/reading. How can you search for something when you have no clue what you&#039;re looking for? This is particularly true of drupal where some of the jargon is completely unfamiliar to true newbies.

We, as the knowledgeable community, need to guide real newbies through the topics they need to understand in the order in which they need to understand them. Once they have that basic foundation, THEN they can jump to a wiki style interaction where they will have specific needs they wish to find information on.</description>
		<content:encoded><![CDATA[<p>It&#8217;s definitely NOT an either / or discussion&#8211; we  absolutely do need both. I perceived the original suggestions as recommending using only a wiki style documentation and completely abandoning hierarchy&#8211; which I still think is a mistake.</p>
<p>And while searching is very much a sore spot and desperately needs to be improved, the chief complaint I see when providing support in the forums to real newbies (as opposed to developers who are just new to drupal) is that they simply can&#8217;t figure out how to get started. That reflects a complete failure of guided learning that randomly wandering around a wiki will not solve.</p>
<p>Getting started is not done with search&#8211; it&#8217;s done with guided browsing/reading. How can you search for something when you have no clue what you&#8217;re looking for? This is particularly true of drupal where some of the jargon is completely unfamiliar to true newbies.</p>
<p>We, as the knowledgeable community, need to guide real newbies through the topics they need to understand in the order in which they need to understand them. Once they have that basic foundation, THEN they can jump to a wiki style interaction where they will have specific needs they wish to find information on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon</title>
		<link>http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/comment-page-1/#comment-170460</link>
		<dc:creator>Gordon</dc:creator>
		<pubDate>Thu, 20 Nov 2008 15:18:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/?p=657#comment-170460</guid>
		<description>I&#039;m a &quot;technical communicator&quot; by trade (technical writer, documentation monkey, whatever...) and this looks great.

Multiple entry points to cater for both the types of user and the types of information. Once &#039;in&#039; the information the navigation is as hierarchical as can be presumed from the current context.

You obviously learned a few things at the Online Help Conference in Edinburgh!! ;-)

And, as someone else pointed out, since when were these things EVER either/or discussions? They are always &#039;BOTH&#039;.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a &#8220;technical communicator&#8221; by trade (technical writer, documentation monkey, whatever&#8230;) and this looks great.</p>
<p>Multiple entry points to cater for both the types of user and the types of information. Once &#8216;in&#8217; the information the navigation is as hierarchical as can be presumed from the current context.</p>
<p>You obviously learned a few things at the Online Help Conference in Edinburgh!! <img src='http://www.disambiguity.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>And, as someone else pointed out, since when were these things EVER either/or discussions? They are always &#8216;BOTH&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: catch</title>
		<link>http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/comment-page-1/#comment-170413</link>
		<dc:creator>catch</dc:creator>
		<pubDate>Thu, 20 Nov 2008 10:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/?p=657#comment-170413</guid>
		<description>If you find content via google, it might still be organised into multiple pages, chapters, or some other kind of hierarchy. I think we all know that one single book doesn&#039;t work for organising the handbook as such - but smaller sub-sections are likely to keep their structure, at least initially.

One good thing, is that Drupal 6&#039;s book module allows you to have multiple books - so once we upgrade Drupal.org, it wouldn&#039;t be much work to split all the &#039;top level&#039; books out in to separate ones to get us started.</description>
		<content:encoded><![CDATA[<p>If you find content via google, it might still be organised into multiple pages, chapters, or some other kind of hierarchy. I think we all know that one single book doesn&#8217;t work for organising the handbook as such &#8211; but smaller sub-sections are likely to keep their structure, at least initially.</p>
<p>One good thing, is that Drupal 6&#8217;s book module allows you to have multiple books &#8211; so once we upgrade Drupal.org, it wouldn&#8217;t be much work to split all the &#8216;top level&#8217; books out in to separate ones to get us started.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
