General discussion

Hello,

we are doing an application documentation sprint. The recent documentation survey indicated that 71% of respondents needed application documentation. A quick review of the documentation available in 60 of the core and contributed applications revealed the following.

1. 23 out of 60 applications did not have an administration interface. (12/31 core)
2. 27 out of 60 applications did not have administration help documentation. (14/31 core)
3. There were few direct links from administration help documentation to the relevant handbook pages.
4. There were no links from the administration help documentation to the application administration interfaces.

How you can help improve the usability and documentation.

We need volunteers to research and write one or two paragraphs on how to use each of the 60 modules. We have researched all the links to application administration interfaces and application help documentation so you do not have to. In many cases we have also linked directly to the package for applications which may include valuable information in install, readme, and upgrade documentation. We have also set up a test site where you can work with an application to help write documentation for it. We have created customization and configuration handbook pages for each of the 60 applications and provided you with those links.

Results of the survey:

Users of documentation:
-69% site admins
-46% site users

Situation when using documentation:
-Troubleshooting a problem- 54%
-Administering a Drupal application -52%
-Administering Drupal-49%
-Learn about Drupal-48%

Documentation needs
-Drupal application documentation-71%
-Drupal administration documentation -65%
-An answer to your problem-58%

Decision criteria for using the documentation again
-Read the documentation-68%
-Found answer to problem last time-59%

Usability experiment: card sorting

click here

1. The first red cluster is the About Drupal handbook
2. The first blue cluster is the Installation and upgrading handbook
3. The next red cluster is the Configuration and customization handbook
4. The last blue cluster is the Developing for Drupal handbook

The results indicate that we can meet the diverse documentation needs with the handbooks we have selected. We will use the results to help design the subsections in the book so that they are easy to find.

Actions by the docs team

1. Creating a documentation block which meets your situation, needs, and decision criteria when using the documentation.

Results of the survey:

Users of documentation:
-69% site admins
-46% site users

Situation when using documentation:
-Troubleshooting a problem- 54%
-Administering a Drupal application -52%
-Administering Drupal-49%
-Learn about Drupal-48%

Documentation needs
-Drupal application documentation-71%
-Drupal administration documentation -65%
-An answer to your problem-58%

Decision criteria for using the documentation again
-Read the documentation-68%
-Found answer to problem last time-59%

Usability experiment: card sorting

click here

1. The first red cluster is the About Drupal handbook
2. The first blue cluster is the Installation and upgrading handbook
3. The next red cluster is the Configuration and customization handbook
4. The last blue cluster is the Developing for Drupal handbook

The results indicate that we can meet the diverse documentation needs with the handbooks we have selected. We will use the results to help design the subsections in the book so that they are easy to find.

Actions by the docs team

1. Creating a documentation block which meets your situation, needs, and decision criteria when using the documentation.

Anybody know where in drupal 4.6.0 can I turn on "Popular content" block?

Sorry for my question but I really can't find it....

As pointed out in this Drupal thread, other site implementation are now using themes that are very similar to bluebeach. For example,

• Mambo's main site
• Ubuntu - Linux for Human Beings (runs on plone)
• Kubuntu (not sure what CMS this is)

Steven deserves a lot of kudos for coming up with what now seems to be a popular, contemporary design. However, it seems that part of the original reason for not releasing bluebeach is no longer valid:

In order to keep Bluebeach as a unique style for Drupal.org, the theme will not be made available for download.

I would suggest that it might be nice if a revised version of bluebeach was made available for download. One with a different color scheme and font would give some differentiation between drupal.org and Drupal sites (so that every other new site on the Drupal sites page doesn't look like drupal.org), yet allow Drupal site administrations to take advantage of this great design.

Besides, seems strange for drupal.org not to be using a GPL'd theme (or at least a variation of one) that is availble to everyone. Especially since Drupal could use more good themes :)

If i create a new node and publish the node to the front page (direct save, no preview)
the node counter shows 4 reads after i switch back to the front page.
In my opinion this is wrong. I think it is only 1 read. Better 0 read because i'm not interesting in counts of my own access to nodes, when i create them.

After the creation of a node thinks go strange:
if i click on a node to edit his content the node counter shows: 11 reads.

Can anyone tell me what's going wrong here?
I don't want to show my user fake counts.

meinolf