Using Drupal as a platform for fundraising and advocacy usually means having to integrate with several third-party systems. Beyond the expense, this creates situations that make it hard to get a complete picture of your constituency. To solve this problem we are thrilled to announce we have released AbleOrganizer, a community engagement platform and are excited to show you how it works.
Right now, there are nine, highly motivated people on the East Coast of Florida who are burning the midnight oil... focusing evenings on classes and labs, and days on projects and resources to master the Drupal skills that build new careers and make them valuable members of the Drupal Community. They are the select few of the 2014 Drupal Career Starter Program, and in less than two months, most will be ready for work experience as interns.-->
Last week we deployed a major improvement for issue page workflow: https://drupal.org/node/2159813. The issue edit form is back on the issue page, instead of the standard comment form. Huge thanks to webchick, Mark Carver, sanchiz, Bojhan, joachim and everyone else who worked on the issue.
As we mentioned in a previous blog post, we are happy to be offering lead retrieval capability to our DrupalCon exhibitors, who have been asking for it for some time. We know that lead retrieval has been used before at DrupalCon and it raised some concerns among attendees.Personal blog tags: DrupalCon Austin
With DrupalCon Austin fast approaching, the call for submissions is already open! With the impending release of Drupal 8, Austin will be an important event to help us push the DevOps mindset into the forefront with Drupal 8.
Have you been automating the deployment or maintaining Drupal across a large number of systems, testing your code for performance and functional regressions, or architecting Drupal as a service layer? Consider submitting a session!
The DevOps track is interested and seeking topics relating to:
- Automated development / deployment of environments
- Emerging best practices for Drupal 8 continuous integration
- Changes in deployment and testing best practices from Drupal 7 to Drupal 8
- Emerging best practices for Drupal 8 hosting and performance
- Frontend automated regression/performance testing
- Distributed Drupal development (Docker, Vagrant, etc)
- Architectures with Drupal as a service
- Performance best practices
- Configuration management
- Testing best practices throughout the development workflow
See you in June!
Photo credit: alex de carvalho on Flickr
The Charlotte Drupal Drive-in is coming up on February 22nd. I just wanted to take a moment and highlight ours sponsors and the value they are bringing to making this event happen.
Classic Graphics is providing us with a fantastic facility with a large training room and four smaller conferences rooms. Each with projectors. Classic is also providing print marketing materials and access to their talented creative department for the event.
Drupal Association is providing a community cultivation grant which is funding all catering needs for this event so our attendees never have to leave the facility for food.
Command Partners is providing a $100 Apple iTunes card to giveaway and marketing skills to help promote the event.
Thanks to these sponsors for their generosity. Without them, the event just wouldn't happen. There is still time to register for the event. Head over to http://charlottedrupaldrive.in and register today!Blog Category:
It has been awhile since I have published a top modules list for Drupal so I thought with Drupal 8 coming out soon it was time for one last top Drupal 7 modules list. As I have stated in past blogs on this subject, it can be very challenging to sort through the literally thousands of modules available for Drupal. Therefore, what I like to do as an 8 year veteran of Drupal is routinely publish a list of modules that I use most often on projects. In doing so I hope to give newbie developers a good list to start with. Some intermediate developers might also find a handful of less obvious modules that can help them out on their next project as well.
Modules Unraveled: 095 What's New and Updated in Panopoly 1.1 with Tom Kirkpatrick - Modules Unraveled Podcast
- First off, what is Panopoly?
- What was the reason for creating it?
- What are some of the features built in?
- What’s new in 1.1?
- Other distributions are built on top of Panopoly. What are some of the big ones you can think of?
- Do you know of any sites that are already built on top of Panopoly?
- Damien McKenna
Will 1.2 change over to CKEditor? #mup095
- Chris Ball
You mentioned open academy one of your other distributions. what is the state of open academy?
This week's podcast is parts of a fun conversation I had with Ruben Teijeiro at Drupal Camp Vienna in December 2013. I "borrowed" him from mentoring Manuela Hutter at the code sprint to talk with me, but in the end, they both still managed to get a lot done that weekend. Thanks for your contributions, folks!
Drupal 6 was released in February of 2008. At the time, George W. Bush was still president, XP was the latest Windows OS, songs like “Pocketful Of Sunshine” and “Just Dance” were on top of the charts, Fidel Castro was President of Cuba, some people thought that turning on the Large Hadron Collider would create a black hole and destroy Earth, and Heath Ledger - the most terrifyingly hilarious Joker to appear in a Batman movie - had not yet passed away.
Welcome to 2014. Processing speeds are faster, MacBooks and iPads are now MacBook Airs and iPad Airs, "Demons" by Imagine Dragons is now dominating the airwaves, the "God Particle" has been discovered, Batman - who is not being played by Christian Bale (which I am not okay with) - is teaming up with Superman, and Drupal 8 is just over the horizon. And much like that laptop that you bought a couple of years ago (yes...the one that you spent so much money on and was so future-proof that you swore you wouldn't need to buy one until the next decade), a lot of us are thinking it's okay, my Drupal 6 site is working just fine.
But are we right? I checked in with some of our experienced Drupal developers and asked how much better can Drupal 7 possibly be compared to its D6 little brother?
“About a million times better…”
“An awful lot”
Oh. So maybe there is something to this after all. But I hear Drupal 8 is coming out pretty soon, so shouldn’t I just wait to change my D6 site to D8 after it is released?
“All the [D8] third party integrations and futureproofing, plus a really improved front-facing UI have me pretty stoked. In-line editing, responsive out-of-the-box, Twig...”
“We aren’t seriously working with D6 nowadays, are we?!”
I’m realizing that developers are definitely excited for D8, but that’s part of the problem. Many quality developers are already ditching the D6 ship and gearing up for D8. When D8 is released, almost all valuable support for D6 will be gone and bug fixes for even the core will cease. At that point, security for D6 websites will not be up to date, and if things go wrong with a site, they are going to go very wrong. Unfortunately, it won’t be possible to just jump to D8 as soon as it’s released.
“I’d say we won’t be able to use Drupal 8 for 1 year from now at very-very minimum. The API completion phase is supposed to begin on July 1st; that’s when Drupal 8 betas will start appearing. So, ideally, we’ll have a release by the end of the year- somewhere in the 4th quarter plus some time- and maybe 4-6 months to get contrib modules in stable shape so they can be used on business-critical websites.”
You’re not laughing anymore. From a business standpoint, it can often be hard to justify upgrading to something that is going to be “second best” in the foreseeable future. Nobody wants to buy an Apple product a couple months before the newer better cheaper line of futuristic tech is about to be unveiled. Nobody wants to start liking a popular song right before everyone is about to forget about it. I didn’t want to like Heath Ledger as the best portrayer of The Joker ever right before his tragic demise made it impossible for the character to ever be played so well again. So it’s understandable when there is resistance to switching away from a D6 website. After all, my website is working just fine right? Look, my information is on the web, people are viewing my page, everything is fine.
But it’s time that we stepped swiftly into 2014 and realized that an effective web strategy involves maintaining a website just like we would maintain any other business product. Our websites are products, and when we make them change and grow with us, our audience notices. In fact, our audiences often increase as a result of SEO boosts that growing and changing websites enjoy. Expecting a website from the last decade to keep pace with the latest is like showing up to a business meeting in a 1986 Mustang and not understanding why a billion dollar company didn’t take you seriously. Don’t misunderstand me, I love the eighties, I love Mustangs, and I’m sure you take good care of it and that it runs quite reliably. But dynamic content, added features, and upgrading versions are what we have come to expect as users, so we should start expecting it when we deliver a site as well.
Let go of Drupal 6, forget about the recession of 2008, buy yourself a ticket to an Imagine Dragons concert, and start working on a shiny new Drupal 7 site with refreshed strategy, bold content, and exciting new features. Do it with the help of a leader in Drupal, like Propeople, and you’ll never regret it. While you’re at it, stay ahead of the curve and make sure that your long term web goals include a jump to Drupal 8 in two to three years when everything is really running smoothly. Build a habit of revitalizing your web presence instead of staying stagnant, and you’ll notice a lot of positive results.
If you have any questions, or simply want to know more, don’t hesitate to leave a comment below or send me an e-mail.Tags: DrupalUpgradeDrupal 6Drupal 7Drupal 8Check this option to include this post in Planet Drupal aggregator: planetTopics: Business & Strategy
The next alpha for Drupal 8 will be alpha 9! Here is the schedule for the alpha release.Feb. 16-18, 2014 Only critical and major patches committed Feb. 19, 2014 Drupal 8.0-alpha9 released. Emergency commits only. Feb. 20-24, 2014 Disruptive patch window
Getting involved in any community on a professional or personal level can be intimidating at first. How do you add value and contribute to something that already has so much community involvement, innovation, and growth? It’s easy to feel like you're trying to catch a runaway train. I feel like this is especially true for designers who want to get involved or even just learn about what is already happening.
I am new to Drupal. In fact, I barely ever heard of Drupal before I was fortunate enough to join the Drupalize.Me team as an interactive designer. And I may never have appreciated this amazing community if it weren't for my incredible colleagues—each of whom promotes contribution and collaboration. The absence of a similar experience could hold back many talented designers who might bring great new insights to the Drupal community. Not every designer has the advantage of working for Drupalize.Me, but I believe every designer relishes the idea of making a positive impact with his/her knowledge and skills. So how do designers get involved and not feel like they're trying to catch that runaway train?
After creating the field type and field widget it is now time to complete the set by creating the field formatter.
Whilst working with Mancunian Matters, a Manchester based news web site, our brief was to re-design the frontend and upgrade the site from Drupal 6 to 7.
After reviewing the stats for the site it became evident that the site had a large mobile following - so we suggested a responsive design that worked with mobile advertising as well to gain a better revenue platform for the publisher.Blogs: Drupal PlanetTags: Drupal Design
Whenever I post a tutorial about sending emails using Drupal, the first question I get asked is how to send emails as HTML. By default, emails are sent as plain text in Drupal 7. There are a few modules out there that allow you to send emails as HTML like Mime Mail, HTML Mail and Swift Mailer.
There are a few benefits in sending emails as HTML. For one thing, they can be styled and images can be displayed. Also, it's easier to track open rates and clicks if the email is HTML. However, there are some downsides to using HTML. One thing I've read about is that HTML emails are more likely to be flagged as spam. Especially if your whole email is just a single image.
I’ve been working with Drupal for nearly 8 years now and I’ve worked on a lot of sites over the years. One of the earliest, memorable sites I worked on was a large community content driven site, which introduced me to the issues of “Deployment” and “Configuration Management”, although I didn’t know them by those names at that time, all I knew was this; making configuration changes to a production site without losing data can be a pain in the butt.
And the reason that was was that I, like many others, was up to that point using a simple yet dangerous deployment strategy, I was developing my new functionality/configuration on a local development site and then replacing the production database with the local version. And while that approach may work in a lot of cases, if there is any content being created or important data being collected in the production database, then you’re going to have a bad time.
However, I was thrown into this issue headfirst, and I came up with a better approach that worked for me… running the production and local database throw a diff/merge application.
I never wish that process upon anyone, it was slow and painful. Don’t get me wrong, it worked, and I learnt a lot about the Drupal 6 database structure from that experience… but it’s not an advisable approach.
Later in my Drupal career, during a community driven collaborative site build, while dealing with the similar problem of having multiple developers wanting to make configuration changes without stepping on each others toes, I was introduced to Features. At this time, I was using a hook_update_N() based approach for deployment, and Features didn’t appear to me at first as being all that necessary… how wrong I was.
To this day, I could not consider building a site without Features, and over the years at Drupal meet ups and events I have repeatedly said that someone really needs to do an introductory type talk on Features, it’s always somewhat assumed that people should be used or mentioned as an aside, and yet so often I find that so many out there don’t see the need for it. This year at, Drupal South 2014, I decided to take my own advice.
I will be presenting (or have already presented) “Features 101: A beginners guide to Configuration Management” at DrupalSouth 2014 on Saturday the 15th at 12:30pm (room TBA). The talk will be posted (if possible) here (or has already been), but come see me in person if you’re attending.
The following distribution was made specifically for the talk, so if you’d like to follow along and learn how to use Features yourself you can build your own copy using Drush with the following command:drush make https://raw.github.com/Realityloop/Features101/7.x-1.x/stub.make features101
Once built, install as per a standard Drupal site.
Time permitting, a tutorial-esque version of the talk will be posted here, but no spoilers up front :)drupal planetdrupalpresentationfeatures
Last week I did a webinar with the team at Acquia. The webinar was called, "45 Modules in 45 Minutes".
During this session we'll walked … jogged … okay, actually we ran through 45 of the best and most popular modules in 45 minutes.
Drupal is a great CMS, but not all features come right out of the box. There are thousands and thousand of modules available for Drupal 7. Figuring out which modules to use can be a real challenge!
In this webinar, you'll get an overview of 45 of the most important modules.
This Wednesday, 12 February 2013 at Noon Pacific (-8 UTC), we'll hold our next monthly Drupal Association board meeting. As usual, we'll give an update from the staff report, which now includes our updated dashboard numbers. We'll also tackle the an adjustement to the Association's mission statement, and here about our (fingers crossed) imminent CTO hire.