Last week, I wrote a post about the differences between content types, taxonomies, and entities in Drupal, and how you should use each. Now, even with having a strong understanding of how to use these mechanisms, there is still plenty of room to mess up when developing a content model. Here are ten lessons we have learned over the past seven years of building Drupal-powered websites and apps:
Recently a client for an "inherited" (that is, one where we weren’t the original developer) Drupal 7 site asked us to change how a series of videos were presented. They needed to collect some demographic information from site visitors before making the videos available. This is a fairly standard use case (think whitepapers on an agency site), and the Webform Protected Downloads module works pretty well if you’re dealing with PDFs. But the client wanted to make the videos appear in a lightbox.
In response to our clients’ needs and our own particular strengths at leveraging interactive video to engage audiences, we have been building a custom video player that integrates web video with online services commonly used to for running campaigns. This product, currently called "Dub", uses the open source jPlayer framework and Popcorn JS to integrate social media, web forms for petitions/surveys/user registration, and custom overlays such as maps and presentations onto the video itself.
I recently had a conversation with a client who was confused by Drupal terminology and didn’t know the difference between content types, taxonomies, and custom entities. This is a fairly common question we get asked by clients that are new to the content management system.
In my last blog post, I talked about ways you can integrate the Salsa CRM system with your Drupal site using the Salsa API and Salsa Entity modules. In part 2, I'll dive into using Salsa API with your own custom code.
The traditional method of designing a website has its roots in print. When you design for anything from a logo to a soda can label, you start out with the basic (sketches), work toward the finessed final design, and show your client developing designs at each stage. Web design has worked in a similar manner for a very long time; the designer starts with colors and typography, then moves into mocking up the full design as a flat image.
The most important part of a content strategy, in my opinion, is your content model. It not only ensures your copywriters and editors are able to publish the appropriate content, it provides the framework for your user experience and ensures proper delivery of content across marketing channels.