Ever need to build a content model with related child records? Want to build a Drupal based billing application? Need to model an educational site with master course records and child schedule records all in the same displays? Want to have lightning fast related content displays across 3 or 4 content types on the same page? Need to have your content entry UI's be intuitive and slick?

With a small IA footprint, entities, simple views and a little thinking "out of the Drupal box", this concept becomes a breeze.

p.s. not a single taxonomy vocabulary or term in sight with this approach :)

There are many Drupal web sites in the wild that contain geographic information as part of the day-to-day content added to the site. User profile information, events, and content locations are just the tip of the iceberg when it comes to content that can have geographic information assocated with it. With just a little bit of planning, this treasure trove of data can be turned into big, beautiful, and useful maps using contributed modules (and not one bit of code!)

This session with start with a quick slideshow providing an overview of some of the most useful mapping-related modules, including Address field, Geofield, Geocoder, and Leaflet. Following this, we'll walk though a full demonstration of how these modules can be easily put to use from start to finish. 

Attendees should expect to leave this session with actionable information on exaclty how to add beautiful mapping capabilities to their Drupal 7 site.

Full blog post and screencast of this material can be found at http://drupaleasy.com/x

Do you want to murder Drupal’s default markup with an ice-pick? Are you wondering which grid system is the new hotness (hint: no gives a ….). Is SMACSS more maintainable than BEM?

In this presentation, I’m going to walk the intermediate themer through common Drupal theming questions, pain-points, and best practices including

• Making Drupal’s crufty markup more semantic
• Comparison of various base themes and creating your own theme from scratch
• Object oriented css - the mecca of maintainability?
• Best practices on developing for Internet Explorer
• Keeping your theme fast - 80% of lag is at the front end
• Structuring your sass partials
• In addition, we’ll do a quick overview of the massive theming changes in D8 (time permitting)

To get the most out of this session, attendees should be familiar with the basics of Drupal theming, css, and sass.

Note: This session will be kicked off with a poem, "Ode to Drupal Theming"

Shouldn’t the web be awesome for everyone?

The goal of this session is to introduce developers and designers to web accessibility – what it is, why it’s important, and how to build a web accessibility initiative in their own companies. This includes a brief sampler platter of some fundamental no-no’s and hoorays when building and designing, some neat tools, and a walkthrough of basic standards for accessibility. This session will touch on Section 508, WCAG standards, and WAI-ARIA.

• Intro - What is Web Accessibility?
• Why does web accessibility matter?
• Why does web accessibility matter for my company?
• How can I initiate web accessibility in my company's culture and work plans?
• Basic fundamentals (web accessibility in practice / beginners’ how-to)
• Web accessibility tools to assess and improve your projects

Being a genius developer is one thing, being a great designer is another but without the proper process of managing a client, you may never get any work. What happens once the contract is signed? What expectations does your client have during the process? Too many times, development houses are too quick to get a contract (maybe) and get the start fee, but keep the client in the dark until you are finish, or so you think.

This session will show you what documentation is needed to make the developer/client relationship strong from the moment they tell you they have an idea until they are ready to redevelop their whole website three years later. We will focus on the proper documentation, client communication, and case studies to help with future projects.

CRM can mean contact relationship management or constituent relationship management. The first is used to describe software that primarily tracks sales leads. CiviCRM belongs to the second definition and is used primarily by non profit organizations.

Discover when and why you should consider using CiviCRM.

The main features of contacts, relationships, memberships, events and bulk email will be reviewed. Special emphasis on the tight integration with Drupal including rules, views, organic groups, group roles sync, member roles sync and webform.

Several use cases will be examined.

A membership system with online signup and renewal, and publicly searchable member's directory.

A one-to-many relationship among organizations and their programs.

Newsletter creation and emailing.

There always seems to be a divide between the styles applied to the site regions, and the styles applied to the content itself. Where the "theme" ends and the WYSIWYG editor begins. And what about layouts within the content area? What do content editors do now that responsive design is a major factor in all of this?

Fear not! The Classy Panel Styles module has arrived on the scene. It builds on the drag and drop content layout freedom that Panels provides and allows editors to apply ready-made styles the themer has whipped up for them —without having to remember class names!

Beyond that, we'll show you how you can use these easy applicable styles to allow further flexibility with panel panes without requiring 101 different panels layouts.

We'll also talk about how this was all put together and how you can use it to create your own set of Classy Panel Styles.

This session is great for developers, themers, content editors and more.

Slides: http://bit.ly/classy-panel-slides
Sandbox: http://bit.ly/classy-panel-styles
Recording: http://youtu.be/5BcD6fVJbYI

With the ever expanding amount of content on the web, we all understand the importance of connecting with our site's visitors as quickly as possible. Technology has evolved such that we can now personalize the content of our sites based on a wide range of known user attributes such as location, where they entered the site from, time of day, behavior, and much more.

It has historically been very difficult to tailor content to visitors in this way with Drupal unless they created an account and signed in. That all changes with a combination of the new Personalize module, Visitor Actions module, and the unending flexibility of Drupal itself. These modules were developed for Acquia Lift, a new SaaS product from Acquia which takes personalization even further, but the code for these modules is open source and can be extended in many ways to be used both with and without a subscription.

In this session I'll introduce these new modules and walk through implementation details, extension possibilities, and more.

Developing a User's Guide for the customer can be a daunting task. The biggest question is.... "What do you put in the User's Guide?" or should it be called a "As Build" Document. The size of the document will depend on the amount of special features and complexity developed for the site and the what the customer need to know to manage the content. Come and share your thoughts on this topic.

Presented at the 2013 FLDC, this session was so popular we were asked to do it again!

Wouldn't it be great if you could use variables, nesting, operators/functions and more in your CSS? With SASS you can!

SASS (Syntactically Awesome Stylesheets) is an amazing way to save time, energy and frustration in your CSS theming. With this session, we will outline the features of SASS with demonstrations and explain how to put it to use with your Drupal theming, from the simple to the complex!

We will explain the basics of SASS, Compass and other awesome features to help make your Drupal theming workflow easier.

New for 2014: We will also touch on other great resources and libraries to use with SASS, as its usage continues to grow and grow!

This session will showcase how new developers, and savvy veterans can kickstart their Drupal projects with a well styled and responsive mobile-first theme in under 5 minutes with some Pantheon, Panopoly and Kalatheme magic.

Kalatheme is designed for people who want to get to work quickly so they can make things happen.

Rapidly build responsive, mobile first Bootstrap 3 driven subthemes with our easy to use and one of a kind subtheme generator. Kalatheme does the heavy lifting for you so don't worry about HTML5, CSS3, media queries or what your theme looks like on Internet Explorer 8. Plus, leverage the entire spectrum of Bootstrap themes, from Default Bootstrap, to Bootswatch to Custom-built Bootstrap themes. We even have support for Third Party bootstrap libraries so you can choose a start state from a myriad of styling options.

With Kalatheme you can also easily add custom CSS to any pane using the amazing Panels In Place Editor or toggle what panes show up on what devices. All views content pane grid displays are also automatically responsive.You never have to turn block.module on ever again.

Kalatheme is also for advanced developers too with solid SASS Tools and respect for grids of any size.

In this session we will show how we built a healthcare portal for one of Florida's largest insurers for healthcare using Drupal. This presentation will entail what contrib modules were used, and custom modules written; as well as the theming done. One of the biggest components of this site is the integration with multiple enterprise services, ranging from rating engines to health care exchange (as required by ObamaCare). We will discuss the challenges encountered as well as the solutions implemented. Lastly, we will discuss how JavaScript MVC framework (AngularJS) can be used with Drupal to enhance usability and performance of the application.

Topics

• Site features (plan listing, checkout, dual DB schema, shopping cart)
• Packaging and Deployment
• Internal and external integration with enterprise services (rating engine, physician directory, Healthcare.gov, cart checkout, google analytics, salesforce)
• Challenges in implementing a healthcare site
• Future developments with REST and AngularJS

The first session looked at the background and goals for Migrate, how it works, and the status of the project.

In this second session, you can try out a Drupal 6 > Drupal 8 migration for yourself, or relax and follow along with the demonstration.

This won't be a tutorial on using a finished product. Rather, you can expect to see, first-hand, the culmination of 5 months of development on the brink of its first major user-facing milestone: A D6 > D8 core migration.

To prepare ahead, have the following installed on your laptop:

• A clean installation of the IMP sandbox, where the work on Migrate is taking place - the sandbox is a full copy of core, so you'll clone it and run the installation.
• A working D6 site (with data)
• Drush 7

Alternately, you can set up at the beginning of the session. There will be USB drives with:

• Drupal 6
• A D6 MySQL database
• A clone of the Drupal 8 IMP sandbox for you to install

You should be plenty familiar with setting up local Drupal sites if you want to install during the session. If not, plan to follow along.

Slides (from both sessions)

Drupal 8 is coming, and with it a whole new era of Drupal development. Drupal 8 modules will be very different than in the past: Object-oriented design, Plugins, Services, unit testing... all these new big words.

While the entirety of Drupal 8 obviously cannot fit into an hour or two, the important parts can. This session will offer a tour of Drupal's new basic architecture, followed by a walkthrough of a for-reals Drupal 8 module. Along the way we'll discuss new best practices, guidelines, functionality, and the benefits they bring.

Slides are available online, as is the sample code from this session.

Part 1: Big picture

Drupal 8 will have a fancy new template engine (Twig) and a simplified theme layer (we hope). We'll show you the new template syntax (don't worry, it's easy) and walk through some of the major problems in Drupal 7 that have either already been solved in Drupal 8, or that we are still working hard on improving.

Things we're currently improving include:

• Syntax
• Consistency
• Complexity
• Redundancy
• Security

Learn about all the changes in the Drupal 8 theme layer, and find out how you can get involved. We want Drupal 8 to be easy for theme developers and people new to Drupal, and also make more sense to the pros.

We still need your help, come learn what we're working on and how to get involved!

Part 2: Nitty gritty

Let's make a Drupal 8 theme together!

We'll make a D8 version of my personal site's theme, including Twig template overrides for page, node, comment, block, field, and more!

The concepts are similar to what you already know about Drupal 7 theme development, but the syntax is a little different, and other minor improvements abound.

Come get your feet wet with Twig, and the new theme layer in Drupal 8.

(completed D8 theme can be reviewed, stolen, or forked from https://github.com/jenlampton/jen)

Learn to manipulate views through inception. If views doesn’t operate the way you’d expect: Take Control. A single view (query) isn’t always the answer. Sometimes we need to go deeper and use views within views within views…

This presentation will focus on some of the technical constraints views has natively. I will show basic configuration of views with a few extra modules to harness more power.

I will propose a solution when the use of functionality like ‘distinct’ and ‘aggregation’ can’t solve your problem. For example, how to overcome duplicate results in your queries.

Goals:
Help you think outside of the box
Give you more freedom with your content design and structure
Award you with your ‘viewception’ merit badge

If you know anything about Drupal 8, you'll know that there's a Symfony going on in the basement. What you might not know, is that a Composer is orchestrating all of the parts in one harmonious piece of beautiful music.

In this season, we'll learn:

• What Composer is and where it came from
• How to install Composer
• How you can use Composer in any PHP project
• The best practices when using Composer with Git
• How Symfony uses Composer
• How Drupal will use it in Drupal 8
• How Drupal will (hopefully) use it in the future.

The only thing you'll need for this concert of sorts is enough wit to run commands on the command line, and a basic understanding of PHP.

We were approached by one of our clients a good while back to differentiate some minor content on the site based on their different geographical markets and the location of the users visiting the site. Originally, this included just a few graphics, but as you are probably well-aware, true believer, this didn't satisfy them for long and additional features were desired. The appropriate combination of contributed modules didn't present themselves so custom modules and methods were developed to handle this feature set. What we found on our journey was a plethora of interesting trivia about the Drupal system and how to correctly workaround the "gotchas". Practical examples will be shown from our Drupal 6 build with concepts that are easily transportable and applicable to Drupal 7 platforms.

Youtube and slideshare.net are available!

This session will talk about Developing a custom project as a Team. We'll cover a common workflow for developing projects. We'll go over how to use git and github for the management of branches and pull requests. We'll go over code reviews, and some of things to watch out for. We'll look at the test framework Behat. And we'll discuss how this all fits into an "agile" development process.

I am the creator of the Coder module. I was the Release Manager for Examiner.com, one of the highest profile, highest traffic sites built with Drupal using D7 in the early days. I work for Tag1 Consulting and specialize in performance, scalability, and development workflow where these practices have been put to the test for many clients. I also write a semi-regular column in Drupal Watchdog.

I live in Florida and was at the very first Florida Drupal meetup.

With the release of Drupal 8, for the very first time in its history, Drupal core will support upgrading directly from the end-of-life version (Drupal 6) to the very latest release (Drupal 8).

This is made possible by writing a new subsystem based on the key parts of the battle-tested contributed modules Migrate and Migrate D2D. During this session, we'll discuss:

Part I: Background

• Timeline
• Rationale
• Shortcomings of Update.php
• Benefits of the new approach

Part II: Demonstrations

• A brief discussion of Drupal 8 changes from the site-builder perspective
• A demonstration of core-supplied migrations in action: where your data begins and where it ends up
• An overview of Migrate API internals: how your data gets from the source to the destination

Part III: A "State of the Module" address

Although Migrate API is not a beta-blocker, the API is expected to be stable by March 31. In the final segment of this session, get an overview of the project

• what's working
• what straightforward work remains to be done
• what sticky decisions are still outstanding
• where you follow along
• how you can help

In the second session, you'll have the chance to try your hand at running a migration yourself - See Migrate in Drupal 8: Let's Do This Thing for details. The sessions compliment each other, and you can attend either one individually, as well.

Slides (from both sessions)

In this session Kevin Basarab will go over the new features of Drupal 8 and what you can expect to see in the forthcoming version. From CMI, views in core, web services, mobile and HTML5 we'll talk about the new features and show a live demo of some of the new features. In addition the session will cover how to help finalize Drupal 8 and get involved yourself.

- View Video From This Session
- View Slides From This Session

Like an AMC Gremlin, a good site-builder can get you where you want to go, but you’ll look like a dope pulling up to the Oscars in one. Sometimes you need a convertible Aston Martin with a supercharger. Drupal gives you all the tools you need to build a beast like that, but you’re sure as heck not going to drive one off the third-party module lot.

Sometimes you need to write your own modules.

Don’t worry: You don’t need to be Dries to do this! There’s a tremendous amount of utility to be had at even a fairly basic level, and I can show you how to unlock it.

I’ll walk you step by step through the development of a bike mileage log, into which you can create, edit, and delete daily entries, and view the results in a themed table. This is the sort of thing you could pull off with a content-type and a view, but our version will be much leaner and much more user-friendly. Moreover, I’ll show you how to include some slick Ajax functionality without writing a lick of Javascript.

You’ll learn:

- The basic structure of a custom module
- How the hook system works
- How to debug Drupal modules, custom or otherwise
- How to use Drupal APIs, including the Form API, the Schema API, and the Database abstraction layer.

Even if you wind up never writing a full-blown custom module, knowing this material will make you a better Drupal developer, better equipped to solve problems with the modules you do use. Which, in turn, will drive a better reputation for our chosen platform. We all win!

Look at the slides on Slideshare

Many Drupal users are not logging in to public facing websites. Applications "inside the firewall" can be easily built and maintained by Intermediate Drupal administrators. These internal applications often have more complicated functionality and workflows than public-facing websites, with all the bells and whistles like responsive mobile design, Organic Groups, Workbench Moderation and more.

We will begin with a brief overview of why one would choose Drupal and an overview of distributions commonly used, like OpenAtrium and Drupal Commons, and then give a case study of three custom-built internal websites:

* Orange County Public Library "Orange Peel"
* Proctors Theatre "Calendar and Help Tickets"
* Chautauqua Institution "Intranet"

We will give tips on estimating internal websites, maintaining them, adding new features, and share some wisdom from managers about the value of "rolling your own" internal web applications with Drupal. Finally, we will give some notes on integrating your Intranet with non-Drupal back-end applications.

Ryan Price is an independent web developer, who upgraded two Drupal 5 Intranet sites to Drupal 7 for Proctors and Chautauqua. He is an 8-year Drupal veteran and co-hosts the DrupalEasy Podcast.

Kristin Retaleato is a web developer for the Orange County Public Library System, and the maintainer of the Orange Peel.

In the first part of this presentation, we will give a brief overview of Open Atrium 2's robust capabilities for managing communications, knowledge, and teams. The second part will be a discussion on the essential planning required to build a successful Open Atrium site.

The goal is to provide an understanding of the building blocks and how people, content, permissions, and structure work together in Open Atrium.

This presentation is for people & teams who are considering using Open Atrium to build an intranet, collaboration site, or communication platform for their business or organization. We will stay out of deep code conversations and focus on achieving your business goals with Open Atrium.

Every modern framework nowadays provides a scaffolding tool code generator for speeding up the process of starting a new project and avoid the repetitive tasks.

The purpose of this session is to build a module through a live demo and show how to take advantage of the Symfony Console Component to provide a CLI tool to automate the creation of Drupal 8 modules by generating the directory structure for a module, controllers, forms, services, plugins and required configuration files.

Topics included on the session:

- Composer
- YAML
- Namespaces
- Dependency Injection
- Annotations
- Routing
- Controller

By the end of this session you will learn how:
- Setting up a local environment for Drupal 8 using a Virtual Machine.
-- https://github.com/hechoendrupal/drupal8.dev

- Building modules for Drupal 8.
-- https://github.com/hechoendrupal/DrupalAppConsole

Session slides
http://jmolivas.com/slides/fldc14/introducing-drupal-8-console-scaffoldi...

Drupal 7 is a powerful, robust tool, that allows your site to grow in almost any way imaginable. But with this flexibility comes a learning curve. Drupal 7 has a reputation for being hard to use, harder to learn, slow, and only easy to develop if you know exactly what you're doing.

Don't get me wrong, those of us who do know Drupal, usually love Drupal, and we can become very efficient at using it to do a great number of wonderful things. We often love Drupal so much that we pour hours of our time, our hearts and often our souls into maintaining contributed modules, creating and posting patches, and helping others in the community.

But let's look into the future for a minute. Drupal 8 will probably be easier to use, but harder to learn. It will be slower to run (unless you have a beefy hosting environment), and completely different to develop code for. Developers for Drupal 8 are going to be more expensive, harder to find, and development time is going to be longer (at least initially) as everyone learns the new systems.

Small to medium-sized businesses are already feeling the increasing development (and hosting) costs that are associated with running Drupal websites. How much of the Drupal ecosystem is made up of these sites, people, and developers? How will they fare in a Drupal 8 world? How does that affect the entire Drupal ecosystem?

I'd like to offer an alternative to Drupal 8: BackDrop CMS.

Backdrop CMS is a fork of Drupal. It splits from Drupal 8 very early in the development cycle, before the introduction of the Symfony framework. It's code is similar to that of Drupal 7 (meaning any Drupal 7 developer should be able to get Backdrop) but also includes features comparable to those in Drupal 8 including CMI and views in core.

The primary goal of the Backdrop project is to decrease the barrier to entry. This includes lowering the system requirements (meaning more affordable hosting) as well as making the interface easier to use, and the code easier to learn. With each significant change that's made, the benefits are carefully weighed against the cost of change.

Come hear more about Backdrop CMS.

The concepts of Entities, Bundles and Fields underlay much of Drupal 7 and Drupal 8 functionality. Though Drupal sitebuilders and developers understand the concept of Fields, Entity Types and Bundles are often misunderstood or even unknown to those new(or not so new) to Drupal. Understanding these concepts will make you a better Site Builder and give you a better understanding of how many popular contributed modules work.

In the first section of this session we will delve into what Entity types, Bundles, and Fields actually are in Drupal. We will look at what is going on under the hood and how Drupal core is using these features.

We will then look at what contrib modules are doing to take advantage of this architecture. Some of the modules that we will look at are:

*Entity API
*Profile2
*Field Collection
*Entityforms
*Drupal Commerce
*Organic Groups
We will look at what new Entity Types and Bundles these modules define or how they add functionality to existing Entity Types.

Understanding these concepts and how they are being used in different modules will give you a better perspective on evaluating different contrib modules.

Come to find out many tools that can add flexibility to your site building experience

AngularJS is a client-side Javascript framework for rapidly developing robust, responsive, data-driven applications backed by a server-side API, but it also serves well as a rapid prototyping tool that produces real, working code that can easily be rolled into a final product.

In this presentation, we'll explore three common use cases for AngularJS: rapid prototyping a new application UI using canned widgets and mock APIs; building a functional application from an existing data API; and integrating AngularJS into an existing application piece-meal.

Server-side application development is quickly transforming into an ecosystem of data APIs that can be consumed by any number of client applications: native mobile apps, HTML5 hybrid apps, and other back-end-oriented clients. Making the mental shift towards API development serving thick-clients can be difficult but ultimately worthwhile. Let me help you get over that hump or maybe take the next step into the world of Javascript MVC development.

The goal of this session is to introduce developers and designers to what Owners, Executives, Hiring Managers and HR Personnel look for when adding members to their team. It doesn't matter if you're brand new to the industry or a 'grizzled vet'...this session is designed to give you some insights into what, where, when, why and how decision-makers in our industry actually want to hire YOU!

Intro - Why do I care what THIS guy thinks?
What do I really need to do to impress someone enough to get an interview?
What skills do I really need (other than being a code junkie?!?)
What makes someone 'ferocious'?
Designers vs. Developers vs. Everyone Else
The power of diversity!
Culture. It's all about the Culture :-)
Why Drupal matters (but why it isn't EVERYTHING)

Awesomeness indeed! In this session we will learn how we as developers how to make fantastic user experiences using the power of the AJAX framework in Drupal 7. We will go over the "use-ajax" class, "#ajax" in forms api, "#states" in forms api and the conditional fields module. With these basic concepts we will learn how to add that special something to your projects.

This session will be fast paced and full of examples!

This session is geared toward developers but will include some sitebuilding tips at the end.

Building a community site can be a daunting task. Should you use a distribution or go with a more customized approach?

This session will discuss the approach of starting with basic Drupal 7, building a basic data model, and using entities to build a decoupled foundation so that you can scale your community and add functionality without refactoring your site.

The following topics will be discussed:
- Data modeling
- Entities
- SEO
- Content strategy
- User roles/profiles
- Social media

If you want to build more efficient sites using a decoupled flexible approach, this session will help introduce some of the latest techniques to accomplish your goals.

From privacy laws like COPPA and FERPA to PCI compliance to copyright and trademark to contractual provisions, Drupal developers can encounter a number of legal challenges and compliance requirements. This session will help arm attendees with knowledge about these challenges, as well as best practices for working to navigate them while avoiding potential pitfalls.

Site-builders love Panels because it unleashes content, and clients love Panels for the In Place Editor (IPE). There is just one problem: no content is the same (and generic layouts do not always make the grade). The Panels Layout Builder partially solves the issue. But, what if your site is responsive? Your 30% column width will be just that, from mobile to desktop.

This session will cover how to add custom Panels layouts to your theme, utilize Sass, and responsive methods.

To get the most out of this session, you should be familiar with basic Panels functionality, responsive web design, and Sass.

Resources & Links

Creating a custom Panels layout
https://drupal.org/node/495654

Singularity documentation
https://github.com/Team-Sass/Singularity/wiki

Responsive Panels layout referenced in slides
https://github.com/mglaman/responsive_panels_layouts

Radix, responsive Panels layouts module
https://drupal.org/project/radix_layouts

Slideshare of slides
http://www.slideshare.net/MattGlaman/rockin-responsive-content-with-panels

Imagine you are an artist who wants to build a site for your studio. You don’t know anything about building a site and you are intimidated by the prospect of building your own local development environment or installing drupal remotely on some shared hosting service. Instead you download and install Kalabox. Get some coffee while it spins up. When you return you’ll have an awesome local development environment with some of most well known and powerful Drupal tools at your fingertips, all accessible through a sexy and intuitive user interface. Easily spin up a new site and get started! When you’re done click deploy and push the site up to Pantheon. You’ve now got a website on the internet!

Imagine you are running a team of 15 developers and building an enterprise application. You need everyone to be on the same local environment, you need solr, you need tika, you need … a great starting point. Imagine being able to use Kalabox as a great starting point for your puppet manifests or chef recipes. Imagine being able to use your own custom provisioner. Imagine being able to test your site locally on Ubuntu LEMP one minute and Fedora LAMP the next. Imagine being able to deploy to your own OpenStack or OpenShift cloud.

This session will showcase how easy it is to get up and running with Kalabox. It will appeal to hardcore developers who need an awesome and customizable native linux local development stack to supercharge their development workflow but also to new users who just want to get started working with Drupal without all the annoying setup.

One of the barriers to beginning with Drupal is getting a local development server running.

Numerous tools exist to make this easy, but sometimes they make things even more complicated. New users often spend more time trying to install various $AMP tools than they do learning Drupal.

You can develop your site locally using the same environment that you would deploy your site to.

I've been using [Vagrant](http://vagrantup.com) for a few years and have found it invaluable for Drupal Development.

In this two-hour workshop session we'll set up vagrant, virtualbox, and get a webserver running with a Drupal 7 installation.

You'll learn about the server that actually powers your Drupal site and how the various pieces tie together to show users what they see in their browser's window.

When we're done, you'll have a base machine that you can easily tear down, and start new with everything already installed.

Here is the box we built during the presentation:
vmboxen.s3.amazonaws.com/drupal_saucy32.box

Is it your dream to work for a Drupal shop? Don't want to relocate? What if I told you that some Drupal shops hire remote employees? Have I got your attention yet?

I've got personal experience and lots of cool stuffs to share about this subject.

If you're in the market for a new job doing what you love and think working remotely is for you, come check out what it's like being a remote employee and how to find these opportunities.

I'll share the good, the bad and the ugly. Want to know what the average day is like? How about the challenges I face and how I deal with them?

If that doesn't scare you away, I'll conclude with tips and hints on where to find these elusive remote opportunities and what to do to prepare for the treacherous interview process.

Here's what you can look forward to:
What it's like to be a remote employee
What the challenges are
How to find remote employment opportunities

Drupal is a powerful content management and like most powerful things it needs good security! Come to this talk to learn best practices for securing your Drupal site and understand how to prevent common attacks.

* Learn practical security practices in the following areas:
* Setting up permissions, roles and users
* Accepting user content with input formats
* Keeping up to date with Update Status
* How Drupal Security Team works
* Securing your hosting environment

Learn about and how to avoid the following kinds of attacks

* Cross-site scripting attacks
* Cross-site request forgery
* SQL injection
* Menu access checks
* Node access checks

Everybody knows about Webforms so why would we want a another survey/form system in Drupal? Entityforms takes a very different approach by using an entity and standards fields approach to forms.

This has many advantages including being able to use virtually any field module in Drupal. Now you can easily gather geographic information, reference site content and include media references in your surveys and other forms. It also allows for simple integration with popular Entity-aware modules such as Views, to handle submission lists and Rules, to handle notifications and form access.

Come and learn more about Entityforms and when you might want to use it(and when you won't).

Every Drupal shop claims to be agile. Every project management job listing requires experience leading an agile team. And many of the Drupal camp speakers will mention “agile” in some way during their presentations. It seems like agile is everywhere these days. But has agile reached IT “buzzword” and cliche status? Or, is it a real thing? Unless you’ve sat through some training, you may be wondering - what is “agile” development?

As a Drupal practitioner, you need to know the realities and misconceptions of this software development philosophy. During this presentation, we will take a close look at:

* The roots of agile development
* What agile IS, and what agile IS NOT
* Various flavors of agile
* The many myths and misunderstandings about agile