It seems we're using an ever-increasing number of modules on our Drupal 7 sites, which are getting progressively more complex as clients (understandably) want more features, more eye candy and more value for their money. Some modules are downloaded from drupal.org, some are modified, some are written completely from scratch, and even features are modules. We've come up with a simple organisational method which we think ought to keep everything organised, and we thought we'd share this and let you have your say.
We just got back from DrupalCamp Oxford at the weekend, and there were a lot of good sessions. When you consider the ticket price was only £50 and included two 3-course lunches (both of which were way above and beyond the usual "Drupal event" food quality), it was a real bargain, but with so much information to take in, we thought we'd provide a quick summary of the key bits we took away from it.
Wonderbag is a unique product that needed a unique site. Drupal 7 put us in a great position to come up with something special, featuring huge amounts of evocative imagery, especially where food is concerned, along with a whole bunch of social content and interactivity.
The site integrates with Twitter and Facebook, and allows users to participate in discussions on the site itself. It contains a recipe index where users can submit their own recipes for moderation, and an online shop selling the Wonderbags themselves.
The National Skills Academy for Food and Drink needed an improved online presence, with more interactivity, stronger visuals, and more control over their own content. As they had a lot of content and a very long potential features list, we went on a few trips to York to sit with their team and get a feel for what they needed.
Sportsbeat needed a strong online presence and they wanted to accomplish this with a strong brand and bold visual style on their new site. We put together a site that feels modern to use, keeps the content straightforward, but engages the user and makes the user want to explore.
The inner pages include a team page where each team member's information can be viewed, a work page where each case study can be enlarged and flicked through, magazine style, and a grid of company logos to show off Sportsbeat's list of high-profile clients.
The Dyslexia-SpLD Trust came to us because their existing self-assessment framework was inflexible and costly to maintain. We had a track record of building custom web applications using Drupal 7, so we sat down with them to discuss what they needed.
Initially we looked at the quiz module for self-assessment, but due to their need to have a confidence level, as well as a particular response, for each statement, we decided to build something from scratch using Drupal's Entity system and its excellent views integration.
Stroud College aimed to separate its identity as a business training provider from its main identity as a college aimed at youngsters in order to attract more business-oriented organisations without the concern over the audience of its courses being misplaced. We provided a completely separate site on a new domain, complete with course listings, course calendar, online booking and reservation system, and e-commerce integration for buying course registrations online.
It has been a bugbear for a while, sitting in a client meeting, running them through how the block system works and being confronted with a list of system blocks that have no bearing on the site.
Having to explain 'just ignore those' is annoying for us, and confusing for them. The fix is pretty simple really, just drop this bit of code into your theme:
Drupal has no native CRM system. But it should have one. Drupal CRM (known by various other names including DropCRM and DCRM) is the attempt to rectify this situation, and at DrupalCon London this year, I propose that the very first code is to be created and used as a springboard to kickstart development work.