JVIS USA LLC is an international supplier for automotive components and tooling with facilities in 6 countries and customers all over the world. Their website helps them introduce their products to auto makers.

Going multilingual

When JVIS commissioned their website, they requested just a few static pages. It was built as a simple static HTML site (no CMS) and in English. Very soon after launching their new site JVIS decided to localize to Japanese, Chinese, Korean, Russian and Spanish. These are the languages spoken by their larger clients.

At that point Jason Marshall contacted us about translating JVIS' website. It was already built (as a collection of 23 HTML files), ready to be translated. Our translation service would have produced another 92 static HTML files which JVIS would have uploaded to their server. It was clear that JVIS was going to be adding new content on a regular basis and maintaining it all in several languages without using a content management system would have been a very unwelcome task.

The likely possibility of turning a client from being happy to frustrated, due to this manual content management, concerned us very much.

We suggested to Jason Marshall, the web designer who built JVIS website, to first migrate it all to a CMS and only then begin the translation process. The first choice was Drupal, given its powerful multilingual capabilities. Maintaining a multilingual Drupal site would be much simpler, not just for us, but mostly for the client. From the client's point of view, only English texts would need to be managed. Drupal would automatically handle everything else.

Mediacurrent collaborated with InterMedia Outdoors, Inc. to redesign their family of interactive websites using the Drupal content management system as a foundation. This required the migration and restructuring of content from several websites hosted by a legacy content management system (CMS.) The result was a fresh, modern web design and a social network that allowed Intermedia’s users to access a vast repository of content quickly and easily. This case study focuses on www.in-fisherman.com, the first website Mediacurrent developed for InterMedia Outdoors, Inc.

I'm looking at a fresh new copy of Drupal 5 Views Recipes. I wrote it, and I'm thrilled to see it in print.

I have a mix of Drupal 5 and Drupal 6 sites out there. If you've got any Drupal 5 sites, consider this book.

Appendices

I'll start by mentioning the appendices, since I think that's one of the most information-rich sections of the book. (The rest of the book consists of 94 step-by-step recipes.)

Appendix A – List of all default views available for Drupal 5
Appendix B – Comprehensive list of Drupal 5 field formatters, by module
Appendix C – Comprehensive list of Drupal 5 style plugins, by module
Appendix D – Views 1 hooks
Appendix E – Modules included in recipe ingredients
Appendix F – Additional resources and modules
Appendix G – Selected noteworthy patches to Views, sorted by topic

Appendix E can serve as an index to the recipes, and also includes a column indicating which modules are available for Drupal 6. Appendix G unlocks a whole host of functionality not available in Views 1 by default.

Recipes

Interesting content includes:
- How to overcome the case of the missing term in taxonomy views
- Views arguments
- Proximity search (Find every trailhead within 6 miles of a Senior Center, for instance)

For the last few months myself and quite a few community members have been working on a larger vision for our beloved Drupal documentation. It has taken quite a bit longer than I had hoped, but I want to put out a draft of an initial "roadmap" for documentation that outlines our bigger issues and an approach to tackling them. I've attached a document which has everything we've hammered out so far in a 10 page document along with three appendices. This post is just a short summary of what is in that document and to let people know that we are gearing up to kick things off and really make Drupal documentation rock.

For starters, we've spent a lot of time identifying problem areas, prioritizing them and setting out some target dates. When looking at the tasks we need to accomplish we recognized that there are two main areas to focus on: the documentation itself and the community of people that create and maintain it.

At DrupalCon DC 2009, an unexpected event happened. While sessions centered on development, writing code, performance, businesses and the community were happening up front, the community of Drupal designers and themers were connecting behind the scenes like never before. It started over Twitter and in small Birds of a Feather (BoF) sessions and ended with the designers and themers taking over a room for the last two days of DrupalCon.