Redesign- recent iterations and implications for handbook re-write - 29 views

• 
  #1 heather james on 20 Nov 08

   

  I was reading this post from the redesigners & the comments as well.
  
  http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/
  
  I thought this was interesting - what i took away, leisa describes the thoughts of three users, their needs and their solution
  
  1. i have a specific problem I need an answer to in which case, i search
  
  2. i'm new at drupal, or some aspect of drupal and I need to get up to speed in which case, i need access to some 'designed' content (eg. tutorials) and I'm likely to hit the docs landing page
  
  3. i need more information about which I am looking at now eg. I want to see the documentation associated with this module that I might choose
  
  I think we should organise the theme handbooks to this end.
  
  Answer to 1: Having all pages including relevant keywords, and keeping an index of all topics will improve search?
  
  Answer to 2: Create guided tutorials for specific needs. By modeling with a few examples we could encourage more contribution in this area
  
  Answer to 3: Maybe that's not relevant to theme section?
  
  - It should be really clear what is guided tutorial content, and what is authoritative reference information.

   

  <div class="cArrow"> </div><div class="cContentInner">I was reading this post from the redesigners & the comments as well. <br /> <br /> <a href="http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/" rel="nofollow" target="_blank">http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/</a> <br /> <br /> I thought this was interesting - what i took away, leisa describes the thoughts of three users, their needs and their solution <br /> <br /> 1. i have a specific problem I need an answer to in which case, i search <br /> <br /> 2. i'm new at drupal, or some aspect of drupal and I need to get up to speed in which case, i need access to some 'designed' content (eg. tutorials) and I'm likely to hit the docs landing page <br /> <br /> 3. i need more information about <x> which I am looking at now eg. I want to see the documentation associated with this module that I might choose <br /> <br /> I think we should organise the theme handbooks to this end. <br /> <br /> Answer to 1: Having all pages including relevant keywords, and keeping an index of all topics will improve search? <br /> <br /> Answer to 2: Create guided tutorials for specific needs. By modeling with a few examples we could encourage more contribution in this area <br /> <br /> Answer to 3: Maybe that's not relevant to theme section? <br /> <br /> - It should be really clear what is guided tutorial content, and what is authoritative reference information.</x></div>

  ...

  Cancel
• 
  #2 Hans Henderson on 20 Nov 08

   

  Heather,
  
  don't want to be a wet dishrag but IMO this should be posted to d.o.
  
  1 I don't want people to be able to point to Diigo splintering/diluting discussion
  2 you'll get better feedback there
  3 the record of the discussion will be useful to people later on, all this will go away
  4 this is higher-level topic than theming anyway
  
  Basically I'd like to keep discussion on Diigo to specific categorization/placement of existing d.o. pages, and even those should be summarized and posted back as issues periodically if we can.
  
  Substantive discussion about handbook pages (i.e. about the content itself) should also take place on d.o.
  
  I like the topic and will respond over on the issues queue if you repost it there.
  
  
  OK?

   

  <div class="cArrow"> </div><div class="cContentInner">Heather, <br /> <br /> don't want to be a wet dishrag but IMO this should be posted to d.o. <br /> <br /> 1 I don't want people to be able to point to Diigo splintering/diluting discussion <br /> 2 you'll get better feedback there <br /> 3 the record of the discussion will be useful to people later on, all this will go away <br /> 4 this is higher-level topic than theming anyway <br /> <br /> Basically I'd like to keep discussion on Diigo to specific categorization/placement of existing d.o. pages, and even those should be summarized and posted back as issues periodically if we can. <br /> <br /> Substantive discussion about handbook pages (i.e. about the content itself) should also take place on d.o. <br /> <br /> I like the topic and will respond over on the issues queue if you repost it there. <br /> <br /> <br /> OK?</div>

  ...

  Cancel
• 
  #3 heather james on 20 Nov 08

   

  That's cool.
  
  I thought it was a relevant discussion to sub-team members, to consider a 'big-picture' view before digging in.
  
  In terms of, when submitting the final recommendations for how-to re-do the theme handbooks, it would be good to explain the thinking behind it.
  
  Helps also keep people on same page.
  
  But, no worries, I defer to your leadership here, in order to drive this change someone needs to be in charge.
  
  Having the sub-team is a great step forward, and you've already done alot on this topic.
  
  -h

   

  <div class="cArrow"> </div><div class="cContentInner">That's cool. <br /> <br /> I thought it was a relevant discussion to sub-team members, to consider a 'big-picture' view before digging in. <br /> <br /> In terms of, when submitting the final recommendations for how-to re-do the theme handbooks, it would be good to explain the thinking behind it. <br /> <br /> Helps also keep people on same page. <br /> <br /> But, no worries, I defer to your leadership here, in order to drive this change someone needs to be in charge. <br /> <br /> Having the sub-team is a great step forward, and you've already done alot on this topic. <br /> <br /> -h</div>

  ...

  Cancel

To Top