Views is an indispensable and powerful module at the heart of Drupal that you can use to quickly generate structured tables or lists of consistently formatted content, and filter and group that content by simple or complex logic. But in pushing Views to do ever more complex and useful things, we can sort of paint ourselves into a corner sometimes. For instance, I have many times created multiple Views displays on a single page that contain overlapping content.
Posts in Code
When I first started working on the web, my entire process for figuring out how something worked was the "view source" menu option in my browser. Sometimes I miss that simpler web. But nostalgia notwithstanding, the web is more complicated now, browsers have more complicated tools for figuring out how things are working, and developers need to know those tools. So let's learn.
Drupal webforms are useful in a variety of contexts, but the most typical context is something like a contact form: user-facing functionality that needs to exist when a site launches, and be easily edited by a site owner post-launch. In that context, webforms should be created automatically for a smooth, predictable launch.
Not long ago, I went to a Denver area Drupal meetup. When it was my turn to introduce myself to the group I announced my name, took a look around the room and blurted out “... and I’m the only woman here.” I immediately felt weird about saying that out loud. But I’m glad I did. Why? It’s complicated.
Let’s say a friend (or a new client) asks you to make a small change to their Drupal website. You’ve never seen this site before and the original developer(s) are long gone. Of course the text is in some obscure block. Sometimes finding where to make the requested change is easy. Sometimes it’s not.
HTML5 has brought us several new technologies that make our lives as front-end developers easier. One technology that stands out among the rest is the localStorage spec. It is an easy-to-use, lightweight alternative to cookies and is perfect for storing and accessing local data quickly.
Every once in a while you have a 12GB MySQL export and you need to edit one line. Or at least I do. Let's imagine I forgot to skip a table on export and don't want to repeat the 12GB export. That would never happen, but let's imagine.
If you've ever tried to open a 12GB file in your favorite text editor, you've probably found it's no longer your favorite text editor. Suddenly your new favorite text editor is whatever can open that file without crashing, and ideally taking less than 20 minutes. Your new favorite text editor is Sed.
Last month at the Central Denver Drupal meeting, Nick Switzer from Elevated Third showed how they are using a structured spreadsheet format for describing their Drupal configuration in a way that makes it easy to build. They based their spreadsheet format on a template Palantir published a while ago, and someone mentioned Lullabot has been using something similar.