Vancouver, October 5-6, 2012

Information Architecture and Administration

The Site Building track contains 2 sub-topics: Drupal Admin and Systems Admim.
Drupal Admin covers anything and everything that you can do through the administration interface without writing code. Sessions should focus on providing solutions, key concepts and stimulating the development of skills and solutions.
Systems Admin targets all things outside Drupal, but that are essential to know when working with Drupal. For instance setting up Varnish, running on a cluster, or switching to Nginx.

Streamlining Content Definition and Entry

Tight timelines, development logistics, and clients underestimating time requirements can make getting the content into your new build a deadline blowing proposition. Third party sites try to help by allowing parallel content entry, but their content model is different from Drupal's, leading to other issues. What we really need is a content entry system that has the same feature-set as Drupal, so let's use Drupal!

Organic Groups: Who, what, where, when, why?

This will be a beginner-to-intermediate session for developers considering or interested in using Organic Groups on community sites, or to serve as a back-end access control / theme management system for sub-sites.

The pitch:
Do you need a site that serves different communities that have different access or theme needs, that want to share content and reuse backend structure (i.e.: content, entity types, user roles)? Do you want to set up an intranet or discussion site? Organic groups can solve these problems! (Or not!)

Future-proofing Your Content (or, Death to the WYSIWYG Editor)

It’s become all too common a practice to create web pages by entering text, images, video, and more into a single text area, creating what’s affectionately known as a “blob”, that will really only work on desktop computers. In this session, we’ll cover how you can structure your content so that it can be served up on any device, wrapped in any design. We’ll explore how content “chunks” can be used across your Drupal web properties and discuss how this approach fits with your broader content strategy.

What the heck is WEM? (Web experience management)

Web Experience Management (WEM) refers to the personalization of a website visitor’s experience based upon business intelligence. What does that mean?!?! Put simply, WEM is an approach to increasing meaningful engagement with your website visitors based upon what you know about them. WEM solutions provide integration between content management, fundraising, and CRM tools so that you can present more targeted outreach. In this session, we will examine a handful of WEM strategies and tools.

Avalanches, Ugly Baby Meetings & Project Calamities

Drupal's great. But why is it so hard to have velocity but not viscosity around clients, dev teams and projects? This thrashing leaves many clients leaving Drupal and many Drupalers hating clients. Clients and projects drive Drupal and so let's develop better methodology for implementing world-class Drupal sites, have profitable dev shops and happy Drupal customers.This is geared for site owners, small shop owners, project managers and clients to understand and dissect how to run a project with Velocity and without Viscosity!

Subscribe to RSS - Information Architecture and Administration