Yesterday I ran across a module called Display Suite that blew my mind. This module fills a gap in Drupal that I was only vaguely aware existed, but now that I know it is there I can’t see myself building many sites without this module installed.
I'm a fan of the OpenLayers module in Drupal 7 (and 6 too, for that matter) and here's why you should be too.
You can allow for both latitude/longitude mapping, KML property boundary mapping, geocoding entered addresses (with a helper module) and more. With this module, you can input the geo data and then display all your information on a map.
A few months ago, I came up with an idea to design and build a Digett landing page that would break down the state of the San Antonio web design community and explain to the average consumer why the Digett way is the only way to go. Today, I'm proud to announce the launch of that page — San Antonio Web Design.
This comic about restaurant websites started me thinking about the way most websites are built. My experience over the past 5-6 years of building sites is that the motivation for a new site ranges from “our current site’s design is out date” to “it is difficult to use” or even “we need a website because we don’t have one.”
For the last two weeks, I've talked about A Developer's Perspective on Mobile Websites (part 1 | part 2). This week, I'd like to close out by going through a couple of the decisions I make for each mobile site I make:
Last week, I talked about A Developer's Perspective on Mobile Websites. This week, I'd like to take that a bit further and discuss special considerations for mobile development.
Editor's note: This article is out-of-date. Please check out our post on Drupal Mega Menus Revisited.
Mega Menus have become all the rage in navigation user inteface. When you have a large list of items for a dropdown menu a mega menu makes an efficient way to display the list. An excellent example of a mega menu is on the White House's website.
While every web browser (Firefox, Safari, Chrome, etc.) has it’s programming peculiarities that have to be accommodated when building a website, the bane of every web developer’s existence is Internet Explorer 6. Many web design companies have stopped developing for the ten year old IE6 now that IE 9 has been released. Even Microsoft is trying to kill off IE6.
Drupal is robust and heavily tested, so the sites we built a few years back—on Drupal 5 or even Drupal 4.7—are still running like champs. That makes it hard sometimes to explain why a client would want to spend the money to upgrade their site to Drupal 6 or 7.
Recently I’ve been working on a couple of websites in Drupal 7. One of them has some pretty complicated data structure and relationships. I’ve really been racking my brain as to how to build these data structures in Drupal, to the point of even completely starting over twice.
