Site Building

Duration : 1 hour

After the intro session, just a few things that we have used Drush to solve, and maybe cover a few more of the commands we didn't talk about before, plus would be great to leave 15-20 mins at the end of the session for people other then us to talk about practical things they have done with the power of Drush.

Agenda really is going to be determined by what we get covered in the intro session, and then having a more indepth convesation about how we use Drush, and a little more hands on showing off of the built in Drush commands.

Duration: 1 hour

Just getting people over the hurdle of getting Drush setup and the basics of why you should
1.) What is Drush?
2.) Why is Drush?
3.) Where is Drush?
4.) How to Drush?

This session is going to be tag teamed by Robert (robbiethegeek) Holmes and Thomas (tom_o_t) Turnbull.

About Tom, charming gentleman with the funny accent that is awesome and knows lots of stuff :)
@thomasturnbull

About Robbie, boisterous and passionate gent with a funny accent that is ok (if I do say so myself) and knows a little.

This is a one hour session talking about the state of e-commerce in Drupal and what people can expect.

We'll be looking at:

• Brief summary of online commerce on D6
• Ubercart, past and present.
• Future of ecommerce on D7:
• What's going on with Ubercart development
• The new Commerce module: what's the status, how does it differ from Ubercart, which should you use and when.

As Drupal becomes more popular for media and other content rich sites, the need for fast-loading, highly maintainable and flexible themes becomes paramount. Let's discuss what modules and methods we use to obtain this in our themes. Focus on CSS and other front-end code techniques as well as template.php goodness to keep themes lean. I'll come with my toolbox and hope that you'll do the same!

Session time: one hour.

About the Presenters:

# Brief description (1 paragraph)
Want to control access to some nodes in some way? Then ya need some access on ya nodes.

# Agenda (bulleted list preferred)

• Introduction
• Out of the box (user permissions)
• Contrib modules
• Module Development, aka how contrib does it
• Node type modules and hook_access
• Using grants
• Rewrite SQL
• Drupal 7 Changes

# About the Presenter (optional, but helpful to attendees and camp organizers)

This session will be a quick hands-on how-to overview of the Rules module http://drupal.org/project/rules

More and more modules are including rules support and in my opinion will soon be as common and relied upon as views is now.

In order to show the power of this relatively new module, as well as going over general interface and functionality we will create a simple workflow interface using rules

Overview
Many publishers and media companies have shifted their Websites to Drupal. This DrupalCampNYC8 session explores why this is the case by examining current and future trends. We will present several case studies and host an open discussion about workflow tools, popular contributed modules, mobile publishing, and techniques for monetizing content, all of which are helping publishers rethink their businesses. From workflow management, multiplatform publishing, and subscription payments, to video integration, social media integration, and user generated content, this session will focus on how publishers and media companies are using Drupal to invite wider audience participation and ultimately improving their bottom line.

Duration: 1 hour

One hour, ten mini-sessions, any topic...as long as it's five minutes long. Pitch your crazy new module, complain about the state of documentation, show how you built your lizard selling site using Drupal, talk about the 5 best modules for organizing profile pictures, dazzle us with strategies for getting work done while taking care of five small dogs and a baby, demonstrate your awesome Jquery menus, show newbies how to review a patch, brag about how you got your users to navigate 70 different content types. As long as it's 5 minutes long, it's fair game.

Description

Exportables have become all the rage in drupal over the last year or so. They go a long way to solve the long standing issue in drupal that not only is content stored in the database, but much of the configuration of the site as well. That configuration is what makes your site different from the basic install that drupal ships with, and often is the real "work" in creating a drupal site. Because it lives in the database, it makes it hard to:

• Track changes to configurations overtime
• Store backups of just the configuration