documentation

Hallo,

ich wollte fragen, bevor ich das übersetzten anfange, ob es erwünscht ist,
die Dokus von drupal.org (zB. Themeing Guide usw.) ins deutsche zu übersetzten.

Um diese dann auf einem unserer Projekte zu veröffentlichen.
So wies in etwa das Drupalcenter.de schon mit dem Handbuch gemacht hat?

Muss evtl. noch etwas beachtet werden?

grüsse aus München
Flo

Vendredi 28 mars sur RFI Benoît Thieulin s’est engagé à reverser à la communauté l'ensemble de ce que son agence a développé pour Mediapart.
Écoutez l'extrait (16 min..)

Andy Oram recently posted a very interesting article on the O'Reilly Radar on how to improve online documentation. It's a very insightful analysis of the problems that face those writing documentation.

He suggests two tools should be implemented on any online documentation effort:

1. Quizzes
2. Cross-reference management

He recommends each documentation page include a simple quiz at the end. This is to help monitor quality. If readers aren't answering a question right, this probably means that section of the documentation needs improved.

I've started writing up a handbook on lessons learnt when setting up a more centrally-administered site.

<

blockquote>
Drupal is set up to maintain community-based sites out of the box, with comments, blogs, forums, and multiple users and roles integrated as part of core.
However it's also a very strong platform for centralized, traditional Content Management and a full web development platform, from a brochureware 'about us' site presence to full ecommerce site or knowlegebase.

Hello, all,

There have been some conversations recently about adding features into DrupalEd -- the main discussion has been around improving documentation and supporting different types of install profiles, but, IMO, there are also other areas where things can be made better.

First off, for those who are offering suggestions, thank you. Using the install and providing feedback gives us all a place of reference from which to start the discussion, and get more people contributing into DrupalEd.

Nancy Wichmann has single-handedly coded up the Site Documentation module! Here's a screen shot of it in action (click for a larger version):

Send your improvements to the issue queue. Thanks, Nancy!!

Jose Reyero just completed updating the handbook “Internationalization: Building multilingual sites” on Drupal.org to reflect some of the new developments with i18n and Drupal 5.x. This new documentation makes it easier to start using i18n and to understand all the new features and fixes that both Jose and Gabor have been helping move forward. It even includes screenshots to show off some of the latest features added to the module.

It is a great place to start if you are looking to see if i18n will fit your needs and should save you a lot of time during basic set up. I know a lot of people new to i18n are coming to this group to see the latest on the module and would like to know more about what is happening right now with drupal 5.x, so I will try to post more often here with user end perspectives.

Let's start with brainstorming a list of things that would be useful to have documented when you inherit a new site. Here are a few I can think of off the top of my head:

• List of enabled modules
• What roles exist
• Permission assignments (though making this look readable is going to be a fun task ;))
• What content types (and their fields) exist
• What vocabularies exist, and what content types are they assigned to
• What forums exist
• Workflow module permissions
• System variables (?)
• Other?

Feel free to respond here with your own ideas!

UPDATE: Raw Screencast Is Up! | Torrent file here

This Easter Sunday josh_k returns to the teachers spot in the Drupal Dojo to "resurrect" the lost jQuery lesson.

We'll be retracing our steps, and also forging ahead into new territory. Our mission? To show how easy it is to take your Drupal site to the cutting edge of User Interface with jQuery, talk about the tools and resources that make this easy, and outline some best-practices for security.

Oh, and get it all on video this time. Join us if you like at our usual time: 11am PDT / 2PM PDT / 8pm CET.

The Drupal Dojo is a community group dedicated to spreading best-practices and helping developers who are new to the system get up to speed and become masters in their own right. We hold virtual lessons and produce practical developer documentation in both written and screencast form. If you're a newcomer looking for help in grokking the system or an old hand who's tired of being told to clone yourself, consider joining us in the Dojo!

So I've been granted documentation editor status on the main drupal site. Erm, mwahahaha... I think :)

That means I'm in a position to update the handbook that's here: http://drupal.org/handbook/modules/station
Is that ok with the maintainers of the module?

A few things I'd like to add or change:
- the list of component modules is out of date
- use of the word 'block' in the schedule is potentially confusing, as a 'block' means something quite specific in drupal. Would 'slots' be ok? or 'timeslots'?