Over our years of working with organizations, we've developed some strong opinions about how to make the Drupal content editing forms as helpful as possible. Our colleague Eileen Webb talks about this as "AX" (like "UX", but for content administrators). We think AX is particularly relevant in the nonprofit sector, where there is often uneven funding for technology and extra staff turnover that can result in a loss of org knowledge. Since I find that I'm continually referencing these three A List Apart articles on this topic, I'm going to stash them here on our blog for efficiency's sake.
We keep hearing this question: "Should I build in Drupal 7, or Drupal 8?" The answer to this question will differ depending on your organization's needs and your project goals. But here's one thing we can tell you: right now, if you build in Drupal 7 *or* Drupal 8, you should do so with a sound content strategy and a three-year plan.
Johanna and I just came back from Design4Drupal 2014 at the MIT Stata Center. I've been going to this Drupal Camp for several years, but this year certainly had the most informative and well-rounded set of sessions. I particularly enjoyed Steve Fisher's (@hellofisher) keynote with takeaways like: "Good user experience is connecting the head and the heart" and "Silos are for farming, not web design".
Erin and I will be at the 2014 NTEN NTC next week in Washington, D.C. We're going to helping with Drupal Day on Wednesday. I will also be doing a breakout session about diversity, accountability, and empowerment in nonprofits and the nonprofit tech community with amazing co-presenters Ivan Boothe, Shireen Mitchell, Sloane Davidson, and Aliya Rahman. If you're going to be there, let us know. We'd love to say hello in person!
If you've ever been here before, you may notice that the site looks totally different. We started DevCollaborative in January 2013. The three of us were already working together, and had been in various forms for some years, but we decided to team up under a common name to make it easier to think and talk about ourselves as a team as we worked to develop more unified processes, better collaboration techniques, etc.
Ah yes... WYSIWYG editors (or as I prefer to more accurately call them, "rich text editors"). As you can see, I'm not their biggest fan. There are lots of reasons why they're troublesome, but I'll save that for another post. I wanted to quickly share a problem we came up against yesterday with a site we're about to launch, and its solution.
Building a membership site in Drupal isn't so hard, really. The challenge is to have memberships that include recurring fees. That is, a membership that automatically renews, and the member pays automatically. There are several reasons why this is hard. Some reasons include the payment processor - not all payment processors support recurring fees. But mostly, it's the tools we have available that are limiting in their options. But it is possible, though difficult, and fraught with peril.
When I first heard the news that there was a Drupal fork, I was pretty surprised and doubtful. Then I heard who started the fork (Nate Haug and Jen Lampton, really respected Drupalers), and I got a lot more interested, really fast. I've been playing with Backdrop now for a couple of weeks, and have even contributed some pull requests. It's helped me understand better the rationale behind the fork, and helped me think about what might happen moving forward.
We haven't posted in way too long because we've been busy building some cool new sites, including this responsive beauty: http://jewishsocialjustice.org (design by the talented Carey Otto). And then Michelle and I went to DrupalCon Portland.
If you haven't heard, Twitter RSS is officially dead on March 5, 2013 (here it is in Twitter-corporate-speak; Mashable translation). If you're using Aggregator to pull a Twitter RSS feed into your Drupal site for pretty stylin', then you have to act now. The process for replacing the RSS feed is annoying, but not impossible. I've done it a few times now.