Raw Notes

Presented by Eric Goldhagen

• Actions and Triggers - ways of creating automated functions (actions) when a certain condition is met (trigger)
• Without writing code to refine what the trigger was, couldn't get specific enough
• Rules module gives more fine-grained control through the web interface (e.g.
  

Presented by Joshua Jabbour

Centralized Version Control

• Requires a central server where the repository lives
• In order to interact with the repository, you must have network access and contact the central server
• Actions must be communicated to the central repository in order to be recorded and versioned; can't commit remotely
• Once a change is committed, it cannot be safely edited; a second commit must be made to undo it
• Once you commit, everyone else can download your changes...
  

Presented by Frank Carey (frankcarey)

• In the beginning, Drupal was very code centric
• if you wanted to make something you coded a module, relied in hooks API, etc
• Content ruled the land (the database), but modules still stored many settings in the database
• Content in Drupal - nodes, friends, comments, votes, users, messages
• Then came the GUI-la Monsters - Flexinode, Views, CCK, Contemplate, Rules, Context - things you'd normally do with code, but now could do through the UI
• Config settings include variables, CCK, permissions, vi
  

Random/Framing Notes

• Introduction to HTML 5 book is a primary reference during this conversation
• Is it a good ideal to add a bunch more options, fields, and decisions for what to HTML5ize or not throughout Drupal?
  

Presented by Robert Holmes (robbiethegeek)

(Got here a bit late, but caught the very beginning of drush command overview)

Handy drush commands

• drush - listing of all the drush commands available to you
• drush status - basic info on your site
• drush sqlc (drush sql-cli) - takes you into MySQL console using the credentials of the site you're accessing with drush right now
• drush dl <projectname> - downloads code for module (project) into sites/all/<project
  

Presented by Alex Urevick-Ackelsberg, Zivtech (12-person Drupal shop based in Philly)

Starting Out

• look to other existing shops to get insights into the business of selling Drupal
• Define the type of Drupal/web shop you are. Are you just a Drupal firm? Do you provide other services/products?
  

Presented by Roger López (zroger)

Admin Themes

• clients/users appreciate a clear visual division between the public front-end view of the site and the admin view
• Garland: out-of-the-box theme that can be used to easily create that visual separation; it's the easy choice, but there are others that are specifically tailored to be admin themes
• Root Candy: specifically focused on being used on the administrative side; creates tabs at the tops for "root-level" admin items, emphasis on readibility, good table structures
• comes with built
  

Presented by Theresa Summa (theresaanna) and Seth Cohn (sethcohn)

Civi Updates & Announcements:

Kyle Jaster from Rayogram

• http://civicrm.org/blog/3711
• Rayogram planned and developed features with the intent to contribute them back to the larger Civi community
• When approaching projects like that, you need to think about how you can abstract your requirements so that they fit more use cases than just yours
• Tackled all of the core-related work first, so that bug fixes got into CiviCRM svn and can be easily pulled to facilitate the more customized aspects of dev for the project