Drupal Dojo Session: DITA Integration module installation tutorial
Leader: Denes Lados (mimrock)
The book module is often seen as the documentation in/for Drupal. But it falls short in a couple of areas:
* There is only 1 hierarchy that never really fits all needs
* There are no standards in structuring the information inside a post, so 1 post might actually explain more than 1 topic
* You can only export individual pages or top level chapters with their children, you can't easily export cherry-picked topics (across chapters) into 1 document
* Version management is handled through the forking of the whole documentation
Drupal Dojo Session: Documenting (in) Drupal: the next generation
The book module is often seen as the documentation in/for Drupal. But it falls short in a couple of areas:
- There is only 1 hierarchy that never really fits all needs
- There are no standards in structuring the information inside a post, so 1 post might actually explain more than 1 topic
- You can only export individual pages or top level chapters with their children, you can't easily export cherry-picked topics (across chapters) into 1 document
- Version management is handled through the forking of the whole documentation
A DITA documentation distribution for Drupal
Introduction
A couple of weeks ago we launched Modulecraft an awareness & fund-raising project that aims to rally Drupal professionals around a shared effort to create the ultimate toolset for Drupal business. The first fundraising round has as goal the development of a documentation distribution for Drupal that uses a similar approach as the localization server and that enables a distributed/federated documentation architecture for the Drupal project. As a Drupal user you'll be able to get a set of documentation from the drupal.org docs server imported into your own site. You will than be able to edit it and build subsets of the documentation for your own projects. You'll also be able to submit topics that were edited or created by you on your own infrastructure and add them as suggestions to the Drupal documentation server.
The following is a first proposal for the specification of the Documentation system we want to build as part of the modulecraft project. It is by no means complete, and it strongly needs your feedback. This is our first encounter with DITA and our ideas should really be proof checked by technical writers that have extensive experience using DITA. It also contains some proposes a somewhat exotic usage of RDFa, feedback is also very much needed here. In the coming days I'll be adding new sections to the specification here. This is a wiki so be bold! You can add comments either here or at the original posts on the Pronovix blog. I'll be incorporating feedback into this wiki.
Read moreWorkflow for Drupalversity - how to contribute!
Now that this project has started to move, I've started to think about it less in terms of something that I can build myself and more in terms of a bigger project that lots of different people can contribute to, usually in a relatively small way.
Read moreViews – the basics and a bit more (screencast)
(My previous post mysteriously disappeared. Pardon if this becomes a double post.)
I've just ported my Swedish introduction to Views to English! It can be viewed at blip.tv or downloaded from tr.im/drupal.
The screencast is a step-by-step guide into Views (for Drupal 6, of course), covering the following:
* Download and installation
* Creating a simple list page + the basic settings
* Creating a table
* The point of grouping fields
* Creating and enabling a Views block
og_panels screencast
Hello,
Thanks for the og_panels screencast.
While watching and then implementing og_panels on localhost I noticed that after I create the default home page with the page name "Home", the tab appears as "View". Similarly if I change the discussion page to the default page, the tab turns to "View". I saw this on the screencast too.
Just wondering how to overcome this.
Thanx,
Gerry
Dojo video production requirements
Note that all videos on drupaldojo.com must comply with these guidelines (prospective from February 23, 2008.) We will accept all submitted videos, but submissions that do not comply may be modified by the Dojo to match these requirements if needed. Currently all videos must be uploaded to blip.tv and then will be added to the DrupalDojo.com site. (On the new dd.com site you will be able to upload a video directly through the site.)
There is also a wiki page that has some tips and tricks for making videos.
Read moreClean up some code - Video on Coder module
Code Cleanup with Coder module: This is a 9 minute video that shows me doing a little code cleanup on pathauto module using the cool Coder module. This is a great tool for pointing out secure text and coding standards issues in your code. This is also an easy way to get involved with rolling patches for modules that you use.
Read morePractical lesson: An autocomplete nodereference field that is dependent upon a choice made in another
(Introducing the shiny new "Dojo Practical Lesson" format)
Problem statement
If you need to do this, feel free to use this code. If you can think of ways of improving it, please join in.
So I have three content types with additional fields added through CCK.
Content type one: Company
Content type two: Contact
Content type three: Ticket
The Company content type has a nodereference field where Contacts can be filled in (multiple autocomplete field).
Read moreNew Video - Applying Patches to Drupal Core
Hey folks, I've got another video out, Applying Patches to Drupal Core - there is .mp4 and .mov and a torrent for the .mp4. This one is just as quick and dirty as the last one - it is 12 minutes. It shows you how to use the command line to apply, test and reverse patches for Drupal core. This is a great way to be part of core development even if you know nothing about code. The developers are writing the patches but they need many eyes to test them and see if they really work in a wide variety of use cases.
Read more