Languages make everything so complicated! I just discovered the autocomplete bit on my reference fields wasn't working - until I tried searching by another language, and then the results gave me a surprise:
Several of our recent projects have involved setting up languages that feel like 'child' languages of other languages, for a variety of reasons. Sometimes it's for marketing, so that content can be overridden for markets using a specific currency, other times it's to target a specific audience. Our classic examples are 'Euro English' and 'British English' - in either case, these are special cases of regular English. A more traditional example would be Canadian French - where most content would be the same as French, but some pages would want different spellings or customisations. We came across Amazee Labs' work on language fallback which inspired us to work on the Language Hierarchy project.
We had a lovely time at Drupalcamp Bristol - and especially enjoyed trying to tell the world about our build pipe and automated testing setup. Sadly Mike's trusty laptop died just as he was about to demonstrate some exciting live action testing - but at least it meant everyone got to get to coffee a couple of minutes early.
As promised the slide deck is available below - using google slides because it's slightly cooler than powerpoint!
Anyone familiar with developing with Drupal will be very familiar with how we use hooks to leverage functionality provided by other modules and the core itself. We use them as part of the course when it comes to wanting to tweak data or even extend some core functionality, but how do we expose our own hooks for others to be able to alter what our custom modules do without the need for a developer having to hack around with our code?
Openlayers has a Drupal module which enables you to add maps to your site. We added locations and categories to the events on CoventryMotoFest.com, and wanted to be able to show maps of certain event categories - or just all of them.
We've done a fair bit of reading around lately, thinking through different ideals on content construction. There's a fine balance to be struck between atomic units of content, vs. an enormous amorphous blob of formatted HTML, and articles like this by Wim Leers and sessions like this provide great food for thought.
In recent months there has been much hype over the newest addition to Apple’s product portfolio: the Apple Watch. It’s undoubtedly an impressive looking piece of kit and Apple have been quick to show off its many features in an attempt to get developers thinking up weird and wonderful applications to make the most out of this whole new approach to how users both consume and interact with their content. But what does the Apple Watch mean to us as web developers? How do we leverage Content Management Systems like Drupal to make use of this recent trend towards wearable tech?
On April 21st, Google updated their mobile search algorithms to boost the rankings of mobile-friendly web pages, whilst conversely decreasing rankings for pages that have been designed only for large screens. This change is likely to have a big impact on many Drupal sites, and ComputerMinds have seen a surge in requests for retrofitting responsive themes onto existing Drupal sites.
Queues are a wonderful way of separating different parts of a system. Once you have separated those parts you can do lots of interesting things, like be more fault tolerant or have a more responsive front end for your users.
For example, lets suppose that we have a website on which we can book a holiday. We can choose lots of different options and at the end of the process when we've booked the holiday we'd like to send the customer a nice PDF detailing all the options they've chosen.