Media

Check out some pics and video from Dries Buytaert's keynote on the first day of Drupalcon Paris.

Checkout our live coverage of the keynote! http://drupaleasy.com/live/drupalcon-paris-driesnote

I recently presented a talk at DrupalCon Paris titled, "45 Modules in 45 Minutes: The Best Modules You're Not Using". I hand-picked 45 modules that were not among the top 100 most downloaded modules from Drupal.org for the period of June 21 - August 16, 2009.

The Drupal community in Florida has been steadily gaining momentum this year, and if the next week or so are any indication, there are no signs of slowing down. Starting with our hugely successful DrupalCamp back in February (attended by over 100 people) to meetups in various cities since then, Florida Drupalers are starting to really get a sense of how vibrant our local Drupal community actually is. The next week has no less than three Drupal-related events in the Sunshine State:

This is your moment, you've decided to step up and make a job board for your local Drupal User Group. You spend some time thinking about everything you'll need, including the job listings themselves. You'll want to gather the standard info, like job title and job description, salary, experience, the works. When it comes to gathering company info, your instincts make you take a few extra moments to plan. If you think about this from the perspective of the person posting 6 or 7 jobs, she would end up having to type (or at least copy and paste) the business' contact information each time. If you think about collecting 3 or 4 fields for each business, then that's about 20 extra form fields for the user to fill out. If she then decides to change the info, let's say she made a typo, she now must click through each edit screen 6 or 7 times. That amounts to hundreds of clicks and several hundred repeated keystrokes. There must be a better way. A nodereference can help your users. Once finished, you will have two nodes, one for a job and another for a company, and yet you will still display the information about the company inside the job listing. By the end of this tutorial, you should understand what a nodereference is for, how to create and use one, and finally, how to use template files to theme the output of the nodereference and get the most out of the relationship.

This article is also available in French from KolossalDrupal . There's an incredible amount of functionality that can be provided by the Views module , especially when it is combined with intelligent use of Node Reference fields. When you relate your site's nodes with Node Reference fields, these relationships can be easily leveraged to create some very useful views. I'm going to build a view for a sample music site. In the site, I have 3 related content types for "Band" nodes ("Black Eyed Peas", "Linkin Park", etc...), "Album" nodes ("Back in Black", "Bat Out of Hell", etc...), and "Events" (concerts, television appearances, etc...)

The deadline for winning one of four Drupal-related books that we're giving away will be here before you know it. UPDATE: the entries are now closed. Thank you for your participation.

We've seen in the previous four articles that RDF has the potential to be a game-changer when it comes to linked data on the web. The fact that is it an open standard, easy to understand, and implementable on sites from those powered by the most complex web applications to simple hand-built web pages makes it easy to understand why so many people are starting to look at RDF as one of the future cornerstones of the web. Luckily for the Drupal community, our fearless leader Dries Buytaert recognized this in 2008 and suggested that Drupal take the lead in implementing RDF among open source content management systems. Since then, a number of individuals have stepped up and committed to working to get RDF functionality in Drupal 7. The Semantic Web group on Drupal.org is the focal point of the work that is going on in this effort. Earlier this year, they posted a video about what will be possible when RDF functionality is available. They showcased advanced search results and the ability to navigate the relationships that RDF triples provide with HTML documents.

In the first three parts of this series, we've looked at what RDF will do for you as both a consumer and a provider of RDF data and we've had a quick primer on what exactly implementing RDF entails. Turning our attention back to Drupal, this article will take a look at the state of RDF in Drupal 6 and some of the available contribued modules. Tomorrow's article will take a look at what the next version of Drupal will offer in terms of RDF. Drupal 6 does not have any RDF functionality in core. If you want to implement anything having to do with RDF in Drupal 6, you'll need to utilize contributed modules. Only a few of the RDF-related contribued modules for Drupal have even had official releases - the majority of them are still somewhere in the development process. While reviewing the existing RDF modules for Drupal 6, I found that I could categorize them into two categories - "Provider Modules" and "Consumer Modules". Those in the former category are designed primarily to help you RDF-ize your site's content. Modules in the "Consumer" category are generally designed to help you consume, use, and display RDF data from various sources. In some cases, there is some overlap, so this categorization is more for convenience than anything else.