A couple of weeks ago Acquia, the Red Hat of Drupal, reached out to fellow CMS founder, Matt Mullenweg of WordPress, to see if he would consider switching to Drupal. As luck would have it, this was enticing to Matt. He has long understood the value of the Drupal community and has been looking for ways to leverage our community to make WordPress even better. When Acquia suggested switching to Drupal, it dawned on Matt that this was certainly the easiest way to integrate with Drupal without irritating his webmaster.
"I have always wanted to be part of the Drupal community, where technical expertise is sought after to create some of the most advanced websites. This move demonstrates the synergy between WordPress and Drupal without the possibility of function name conflicts." - Matt Mullenweg
Several months ago I started working with some of our top developers to try to come up with a practical integration strategy between Drupal and WordPress. We had been struggling with this for some time when webchick said jokingly: "It would be a lot easier if they would just use Drupal instead".
To be honest, I felt a bit silly even talking to Matt about using Drupal, but I didn't know at the time that he had been struggling with exactly the same goal and the same problems. webchick's inadvertent idea has ushered in new possibilities for innovation and frankly this is such a fundamental change for us I can't even imagine the world as it was before.
I am very excited about this collaboration. WordPress and Drupal form a killer combination that can't be beat in today's CMS market. I can hardly wait for the WordPress developers to get their drupal.org accounts set up, so we can work together in ways that were never possible before. I also suggested xjm to setup extra "WordPress tables" at the DrupalCon Portland code sprint.
A new Drupal module has been created to ease the transition. The "WordPress_iframe" module will be available on drupal.org soon. It facilitates a rapid integration of existing WordPress sites into their Drupal counterparts. We are excited about the debut of this new module because it embodies the Drupal community's open acceptance of this partnership while it allows us to roll out literally millions of these new Drupal/WordPress sites over the coming weeks.
As part of the agreement, Matt didn't want to completely move away from the WordPress branding, so we have incorporated it into Acquia's logo. Phonetically Acquia is pronounced ah-kwee-uh, so we've swapped out our Q for the well-known WordPress "W". The name is still pronounced "ah-kwee-uh" but will now be spelled "Acwuia". This visually puts WordPress right in the center of our logo - exactly where it belongs. This is WordPress, powered by Drupal.
We are very proud of this partnership and look forward to serving many more customers as a result. You can expect many more great things from Acwuia coming soon.
Matt, your Red Press of Drupal t-shirt is on the way. Let's stand together as brothers, united in Drupal!
Last week it was Red Nose Day, a UK-wide fundraising event organized by Comic Relief every two years. A combination of television programs, local community events, social media and Drupal websites were used to raise £75 million ($113 million) in one day. On Red Nose Day everyone is encouraged to cast inhibitions aside, put on a Red Nose and do something funny for money. The money is used to make a difference to the lives of countless people across Africa and the UK who are facing terrible injustice or living in desperate poverty.
Rednoseday.com and Comicrelief.com are built in Drupal and the Acquia team have been supporting their talented web team with Drupal expertise and use of the Acquia Cloud to ensure a stable and massively scalable platform.
During the live show there were massive peaks in website traffic and every hour there were special heartfelt appeals within the program which results in a frenzy of donations. To deal with the sudden, massive spikes (they call them 'slams'), we had to employ 24 load balancers, 28 web heads and 2 database servers. We had an additional 12 load balancers and 2 web nodes ready for failover. This happens so quickly that it would not give you enough time to spin up additional servers once the traffic starts to ramp up. Along with the hardware, Acquia had 11 people helping with the infrastructure the night of the event.
As you can imagine, there is nothing like a live, six-hour televised national charity event where millions of dollars are at risk, to put fear into the hearts of any web team. To be able to do help inspiring charities such as Comic Relief gives the entire Acquia team an exceptional sense of accomplishment. I am very proud of their dedication and commitment to this project.
In fact, we've been doing our bit with some Harlem Shake videos from both our Reading (UK) and Burlington (US) offices to raise donations. It's not too late to help this tremendously worthwhile and life changing cause: https://www.rednoseday.com/donate.
Today I'm excited to announce that we've released the next generation of Mollom - our Content Moderation Platform. For the past five years, we have worked hard to help companies stay ahead of the curve when it comes to content moderation. With today's release, I feel like we've secured our place as the leading enterprise-ready content moderation system.
With over 2 years in development, and 600 beta users, the new content moderation platform is built to help companies handle extensive amounts of user generated content with ease. The main features of the Content Moderation platform are:
- Easy team management. Site admins can add moderators, assign privileges, and monitor how moderators are performing - keeping an eye on productivity while trusting that no malicious content is making it to their site.
- Fast moderation. If we know it's spam, your team never sees it. If we're sure it's good content - we'll publish it to your site. For the content we're unsure about - moderators now have a very easy user interface where they can view the contributor, their comment, and their reputation, spam, and profanity score all within seconds. They can approve or decline, and even take bulk actions to speed things up.
- Custom filters. The system allows each user to create custom filters so they can focus on a specific subset of commenters. If they only want to see users with low spam and profanity scores - creating a filter takes just a couple seconds and they now have a customized view.
- Multi-site management. All customers can have from one to hundreds of sites in their system - which makes moderation for big brands with multiple site properties very easy. Adding a site takes just a couple minutes, and customers can view analytics separately across all site properties.
I'm really excited to finally show this off to the world, and continue to help more companies embrace social without fear!
We just celebrated our two year anniversary of Acquia's expansion into the European market. It has been a phenomenal two years and as a result, we have grown to over 50 employees in Europe. Our UK office is bursting at the seams so we're about to move into our new digs in Reading. We also have a growing presence in the Benelux, France and Germany.
We are looking for more great talent, no matter what level you're at. If you are passionate about working on some of the most challenging Drupal projects alongside other talented Drupalists, we want to talk to you! Please stop by Acquia's booth at DrupalCamp London, or contact us at email@example.com. We currently have vacancies for Client Advisors, Customer Support Coordinators, Customer Advocates, as well as Sales and Marketing roles.
When we first announced the Spark authoring experience initiative for Drupal in May of last year, we chose Drupal 7 as our target in order to develop the features and get them in front of testers as quickly as possible. After DrupalCon Munich in August, the team shifted efforts towards Drupal 8 core instead, in order to more directly improve the experience of Drupal itself. Since then, we have successfully worked with the community to drive home a redesigned and mobile-friendly toolbar, support for draft revisions, in-place editing, numerous mobile improvements, and have WYSIWYG and unified in-place editing on the way.
This has kept the team pretty busy, however, and so the Drupal 7 version of Spark has not been receiving many updates in the meantime. Olivier Friesse (noisetteprod) of Radio France graciously offered to sponsor work to help things along. Thanks to this sponsorship, we were able to have Théodore Biadala (nod_) of Acquia's Professional Services team spend 3 weeks on getting the in-place editing feature production-ready for Drupal 7, including:
- Full backport of Drupal 8 code, including Create.js/VIE.js integration
- Integration with CKEditor module to provide WYSIWYG support for rich text areas, which resulted in numerous upstream improvements
- Removed requirement on jQuery 1.7 so that Edit module can work on stock Drupal 7 installations without jquery_update module
- Removed requirement on PHP 5.3 so Edit module can also work in PHP 5.2 environments
- Basic support for Views/Panels in-place editing
- Numerous bug fixes to help further stabilize the code base
Working towards a stable release for Drupal 7 naturally identified bugs with the Drupal 8 implementation of inline editing, which are being tracked in this issue: https://drupal.org/node/1894454.
In short, the needs of Radio France have brought tremendous value for the entire community, in both Drupal 7 and Drupal 8. If you'd like to try out the work that we've done, download the 7.x-1.0-alpha7 release of Spark or Edit 7.x-1.0-alpha6!
Thanks once again, Olivier and Radio France, for your support! If other companies would like to sponsor further work on Spark, please let me know.