While content types and fields give you lots of flexibility, what do you do when they still don't match your data?

Is there a simple way to express your clients complex workflow and link that with their data structure?

What if you are simply more comfortable expressing your application's logic through code instead of pointing and clicking?

Drupal 7 and the Entity API provide some amazing functionality for these problems and more. Examples like the above used to mean that Drupal may not be the best fit for the project, but that's no longer the case. This session will you show you how you can have the freedom to express your own data through table schema and objects without compromising on integration with Drupal's many other features.

You'll see examples of:

- Defining your own entities in an object oriented style
- Creating relationships between those entities
- How to maintain tight integration with other Drupal features and contributed modules
- Patterns for creating fluid APIs that are easy to understand
- Advanced example of overriding entity behavior via custom controllers
- And much more