There are many great positions available for people who build Drupal sites. For anyone who knows PHP, Drupal is a great extension to your tool chain. Drupal’s unique site building model also allows for non-coding web development. Right now, the job market in Drupal is tipped in the favor of the job seeker. If you need help finding Drupal jobs, you’re in the right place.
At DrupalCon Paris, I attended a grid presentation by Mark Boulton, for designers. I didn’t get it. Recently I read the biography of Steve Jobs. Now I get it. Drupal designers like Mark focus on the art outside. For several issues, this column has focused on the art inside. At the risk of redundancy, let me state that when I talk about Drupl'Art I am talking mostly about the art within.Aesthetic Minimalist
Like all artists, I navigate my craft through stylistic seas. Most recently, I sailed into an Extreme Minimalist Period: fewer lines of code mattered to me. Eventually, Charlie (chx) politely suggested that, if I insisted on charting that course, to at least comment it better. He was right, I was wrong; and I offer up a heart-felt mea culpa to the developers who followed in my turbulent wake and are now stuck with the flotsam and jetsam.
I am still a Minimalist, but now an aesthetically practical Minimalist; readability and maintainability carry the day. Farewell to saving opcodes!Doug Green
Doug is a 25-year veteran of software development, inventor of the coder module, and core contributor. He specializes in creating interpretive language, development tools, and complex or high performance software. He believes software is functional art, and infuses that belief in everything he does.
It took a little while but I'm really happy to be able to say that there is a set of very good JS people around in the core issue queue. I know there are some out there in contrib but unfortunately very few show up in the core issue queue. We're nice and we have cookies, don't be afraid!
I also want to give a shout out to droplet who's been reminding us that europe an north america are not the only Drupal users while sending out really good patches. Thanks to SebCorbin for working on a major and very important architectural change. Of course thanks to: mfer, ksenzee, JohnAlbin, attiks, rupl, sdboyer, rteijeiro and everyone else working for a better JS in Drupal.
Today I'll explain, how we've build our own Inline Conditions in order to support Commerce Discount rules based on taxonomy terms of product display nodes.
I ran into an interesting problem with the drush @self alias today. I wanted to pull a fresh copy of the DB down from a client’s live site to my local development copy. Should be as easy as drush sql-sync @clientsite.live @self, right? I’ve done this a thousand times before.
And I’ve also ignored the warning message every time before, but today I thought I’d check it out:
WARNING: Using temporary files to store and transfer sql-dump. It is recommended that you specify —source-dump and —target-dump options on the command line, or set ‘%dump’ or ‘%dump-dir’ in the path-aliases section of your site alias records. This facilitates fast file transfer via rsync.
There are actually two possible solutions to this warning (that I can think of), and they illustrate some of the useful “power user” features of Drush that any frequent user should be aware of.
The warning is there because drush would prefer to rsync the DB dump from site1 to site2, rather than a one time copy. Rsync has lots of speed improvements, not the least being diff transfer. When transferring an updated copy of a file which already exists at the destination, rsync will only send over the changes rather than the whole file. This is pretty useful if you’re dealing with a large, text based file like an SQL dump – especially one that you’ll be transferring often. In order to use this efficient processing though, Drush needs to know a safe path where it can store the DB dump in each location.
First we’ll add the %dump-dir% attribute to our alias for clientsite:~/.drush/clientsite.aliases.drush.php1 2 3 4 5 6 7 8 9 10 11 12 13 <?php // Site clientsite, environment live $aliases['live'] = array( 'parent' => '@parent', 'site' => 'clientsite', 'env' => 'live', 'root' => '/var/www/example.com/public_html', 'remote-host' => 'example.com', 'remote-user' => 'cvertesi', 'path-aliases' => array( '%dump-dir' => '/home/cvertesi/.drush/db_dumps', ), );
Notice that %dump-dir actually goes in a special sub-array for path-aliases. This is very likely the only time you’ll need to use that section, since most everything else in there is auto-detected. This is the directory on the remote side where drush will store the dump.
Our options come in with the @self alias. In a local dev environment, the most common way to handle this is in your drushrc.php file:~/.drush/drushrc.php1 $options['dump-dir'] = '~/.drush/db_dumps';
But this won’t work for all cases. You can also take advantage of Drush’s alias handling by creating a site alias with the settings you want, and letting Drush merge those settings into @self. When Drush builds its’ cache of path aliases, it uses the site path as the cache key (for local sites only). That means that if you have a local alias with the same path as whatever @self happens to resolve to, your alias options will make it into the definition for @self. So here’s the alternate solution:~/.drush/clientsite.aliases.drush.php1 2 3 4 5 6 7 $aliases['localdev'] = array( 'root' => '/Users/cvertesi/Sites/clientsite', 'uri' => 'default', 'path-aliases' => array( '%dump-dir' => '/home/cvertesi/.drush/db_dumps', ), );
There’s just one, obscure caveat with the latter method: somewhere in the alias merging process, BASH aliases are lost. That means that ‘~’ stops resolving to your home directory, and you have to write it out (as I did above).
Friday February 14th is the DrupalSouth Code Sprint, and PreviousNext are decending en masse to Wellington, New Zealand, to participate.
As a team we've been discussing what we'd like to sprint on. We've collectively agreed that the sprint would be an opportune time to work on porting some of our favourite contrib modules to Drupal 8.
Read on to find out our plans and how you can get involved.
We know first-hand how committed those of you working in marketing and branding agencies are to delivering the best in branding solutions for your clients. This requires employing the most optimal tools for whatever medium you’re working in; whether it’s classic print advertising, or cutting-edge experiential branding. When it comes to website design and development, we here at Propeople have found that Drupal provides some of the best features for agencies and clients to create a great user experience, advance a brand, and, ultimately, reach their goals.
There are many great tools and platforms available for building websites, and, as a full-service digital agency that delivers solutions outside of Drupal, we fully understand that different issues can call for different tools. However, we believe that it’s no coincidence that Drupal has emerged as the CMS of choice for many developers and website administrators out there. Drupal’s powerful and user-friendly framework, its reputation as an enterprise level platform, and ability to fully integrate overall branding and digital marketing strategies, will likely lead many agencies’ clients to request Drupal for their web projects. Here are seven great things that Drupal has to offer to your agency, and your clients.
1. High Functionality and Ease of Use
In terms of ease of use, Drupal CMS is highly user-friendly and responsive. It can cater to both the technical and non-technical clients while at the same time providing the exact benefits and features that an advanced user would have access too. So, you might be thinking, “There has to be a catch here”. The only caveat is that Drupal can prove to have a steeper learning curve for developers than other CMS. However, it is very manageable for content administrators and end users.2. Drupal is a Great Tool for Social Media
To say that social media is important for a company in this day and age is a great understatement. With the amount of modules available for Twitter and Facebook integration, Drupal is the most versatile CMS when it comes to social media. As an example, the Metatag module allows for the publication of Twitter cards on the client’s website. With a Gigya Socialize module, visitors can log on to your website on their social logins and post from their own accounts be it from Facebook or Twitter, to name a few. Someone saw you a have new awesome product in your pipeline and they want to tell more people about it? Cool! They can invite a friend from Facebook or followers Twitter in mere seconds to see it. With Drupal the potential for increased viral exposure and interaction using social media is higher and less “pushy”.3. Drupal Has Great SEO/SEM Computability (Compliant with HTML)
Any client of yours will require their website to attract a healthy flow of traffic. And so they should, because a successful web presence is usually what sets the first good impression for potential customers (at least if you can’t meet in person, of course).
SEO is key if you want a site to be that number one hit on Google. Is your new marketing campaign getting the viral exposure it needs? Do you want your services to be noticed by potential clients? With Drupal, you have access to clean urls, meta-tags, and customizable titles and headings. With these tools, any prospective client would be able to fully take advantage of significant exposure for their product or services.4. Built-in Google Analytics Integration
Who visits a site, and what they do while they’re there, is one of the most important things to monitor in order to optimize that site to meet a client’s needs, and the needs of their audience. Want to see which product was most viewed or which blog on the website was the most popular? These are the kinds of questions that come up most frequently when figuring out what specific features of a site garner the most attention.
Drupal makes this easy, featuring built-in integration with Google Analytics, the most popular tracking tool on the web. While there are other modules that address the statistical aggregation of your web presence, having the most commonly used, and most efficient, service out there surely guarantees your client’s ROI.5. Great Collaborative Community With Countless Contributors
Being an open source CMS with a highly collaborative open source community attached to it, Drupal tends to avoid any hurdles associated with proprietary systems. So, the next foreseeable question would be: “That’s all great, but how does this benefit my client?”. For one, the knowledge of a huge number of developers can be leveraged to solve a problem or create something great in terms of contributed modules that further enhances the versatility of a website.
At the exact second this blog is being written, there are approximately one million users of Drupal around the world, with about thirty thousand being developers. Imagine a tenth of those developers working individually on a new module or a new feature. The opportunities for development and innovation become very interesting. Additionally, a client benefits from full transparency of the code that’s being used and features implemented. No tricks, no hidden fees or elements, and no problems.6. Countless Modules to Appeal to Every Client's Needs
Modules are community-contributed add-ons for Drupal that give you the tools to do exactly what you need to on a client’s website. We’re sure we harped enough on this in the previous items, however, this is a huge feature that adds value to Drupal. The Drupal library of thousands of modules is essential in an interactive world that is keen on available options and customized to their web presence. Whether it’s social media integration, e-commerce functionality, or different kinds of content editing, Drupal’s got you covered.
Interested in learning more about how your agency, and your clients, can benefit from using Drupal? Feel free to contact us by e-mail or send us your questions and thoughts through our social media platforms Facebook, Twitter, Google+ or LinkedIn.Tags: DrupalAgenciesStrategyCheck this option to include this post in Planet Drupal aggregator: planetTopics: Business & Strategy
In fact, it is so easy to use that I was simply able to drop it over the top of the drupal-phone.tpl.php template file in DruCall, tweak the drucall.js module to call JSCommManager.init() and DruCall is now the first solid implementation of JSCommunicator.Put it to the test
Before pushing this new version out to the community, it is undergoing some testing / baptism by fire. Lumicall recently announced free calling from desktop browser to mobile app powered by JsSIP's "tryit" demo code.
The DruCall module has now been deployed here on the Lumicall website as a parallel solution to access the same free calling service.Browser version sensitivity
JSCommunicator comes from server-side developers rather than web developers. It provides a solid communications tool but it doesn't look great.
The project aims to be a HTML fragment that can drop into just about any page on any web site, so it has been designed to be as raw as possible and allow the styling of the existing web site to influence it. Nonetheless, it could still look a little bit nicer and I would be delighted to see any CSS-based skins that people may develop to enhance it.This is a phone: and now this is too:
It's been three weeks since our last 'This week in core' post, but with holidays providing a welcome break for many, core development has continued at its usual rapid pace. Time flies! The session submission deadline for Drupal Dev Days Szeged is just around the corner on the 15th of January.Give Drupal a birthday present
Next week is Drupal's 13th birthday! Want to give Drupal a birthday present? Why not tackle an issue, or help mentor someone else to do so. There's also a Reddit AMA appearance by Dries (that's Ask me anything for those who don't use Reddit - I had to look it up) and we're also planning a special "This Year in Drupal Core".New Drupal core commit schedule
We're trying out a new commit schedule to increase core momentum. For one week starting January 15 up until the release of Drupal 8.0-alpha8 on January 22, core maintainers will commit only critical and major patches. (Normal and minor patches will be committed again starting January 23.) Read more about the new commit schedule.Where's Drupal 8 at in terms of release?
Each week, we check with core maintainers and contributors for the "extra critical" criticals that are blocking other work. These issues are often tough problems with a long history. If you're familiar with the problem space of one of these issues and have the time to dig in, help drive it forward by reviewing, improving, and testing its patch, and by making sure the issue's summary is up to date and any API changes are documented.
- Objectify the language negotiation system (no that doesn't involve wolf whistles) - this one blocks the final removals of variable_get/set and unblocks more work on cleaning up bootstrap.
- Move definition of menu links to hook_default_menu_links(), decouple key name from path, and make 'parent' explicit (removes hook_menu() and will iron out the new routing system; also fixes a performance regression.)
- Allow per-bundle overrides of field definitions (allows for node titles to have potentially different labels per node type from the managed fields screen and also fixes a performance regression)
- See our last edition for more extra criticals, many of which are still open.
If core's toughest criticals aren't on your to-do list this week, there are lots of other places to jump in and help with conversions and cleanups in core. The Drupal 8 "meta meta", compiled by vijaycs85, is a great place to start if you want to dig your teeth into a technical problem but aren't sure where to start. Or if coding isn't your thing, there are plenty of issues tagged as Needs change notification. Writing these is a great way to keep abreast of recent changes - see more on change records to get started.
- The CMI initiative are planning to hold biweekly meetings to gain momentum around the remaining critical issues
- As always, if you're new to contributing to core, check out Core contribution mentoring hours. Twice per week, you can log into IRC and helpful Drupal core mentors will get you set up with answers to any of your questions, plus provide some useful issues to work on.
The best of git log --after=2013-12-19 --pretty=oneline (XX commits in total):
- #2005716 by tim.plunkett, msonnabaum, dawehner, alexpott, effulgentsia: Promote EntityType to a domain object - this moves much of the entity type annotation/info to a first-class object. The existing entity type info/annotation was a large array with seemingly arbitrary keys. Much of the code had isset checks to see if a particular array key exists. This makes entity type an object with methods for retrieving the various information.
- #2098119 by beejeebus, alexpott, chx: Replace config context system with baked-in locale support and single-event based overrides. As the name suggests this bakes locale support into the config system and removes the config context system. Modules wishing to change config based on other non-locale based circumstances (eg domain module) can subscribe to an event and react accordingly.
- Issue #2130811 by by alexpott, Gábor Hojtsy, vijaycs85, sun, Wim Leers: Use config schema in saving and validating configuration form to ensure data is consistent and correct. This ensures that configuration is in the correct format, as defined in the schema, before the config files are written, eg integers are cast from text etc.
- Issue #2042807 by tim.plunkett, pwolanin, ianthomas_uk, jhodgdon: Convert search plugins to use a ConfigEntity and a PluginBag. One of the last plugin conversions and an important blocker of other criticals.
You can also always check the Change records for Drupal core for the full list of Drupal 8 API changes from Drupal 7.Drupal 8 Around the Interwebs
Blog posts about Drupal 8 and how much it's going to rock your face.
- Drupal 8 CMI walkthrough by Drupalize.me
- A piece about core mentoring also by Drupalize.me
- HHVM and Drupal - which spawned a HHVM Meta for Drupal 8 to track compatability.
- A podcast about migrate in core
- A piece by Last Call Media about setting up their blog on Drupal 8
- Another great Google summer of code project, this time on Creating a Drupal 8 hello world module.
- Jan. 25-26: Mark your calendars for the next Global Sprint Weekend. Join local user groups around the planet for a weekend of Drupal 8 contribution. The sprint weekend will be a great opportunity to engage your local community, and there are lots of resources on the sprint page to help get new people involved. Events are already planned everywhere from Illinois to Budapest to Montréal to Spain. Add yours today!
- Feb 14-17 DrupalSouth. Join Australian, New-Zealand and international guests for a weekend of Drupal. Signup for the sprint day is now open - come along and sprint on Drupal 8.
- March 24-30 2014: Drupal Developer Days Szeged: DevDays is still a ways off, but it will be the most important Drupal 8 developer event before DrupalCon Austin in June, so consider whether you can attend! See Join us for a week of Drupal 8 in March! and Five good reasons to register for Drupal Dev Days Szeged now by Gábor Hojtsy for more details.
Do you follow Drupal Planet with devotion, or keep a close eye on the Drupal event calendar, or git pull origin 8.x every morning without fail before your coffee? We're looking for more contributors to help compile these posts. You could either take a few hours once every six weeks or so to put together a whole post, or help with one section more regularly. Contact xjm if you'd like to help communicate all the interesting happenings in Drupal 8!
Drupal core announcements: Let's focus down on automated accessibility testing; working with the Dutch to make it happen
I mentioned in the < href="393798">recap of the Green by 2014 initiative that I've been working to organize a follow-on effort to continue building our automated accessibility testing tools. I just published the announcement at the following URL.
Here's the title and sub-title:
"Open-source accessibility testing for the modern web"
"Collaborating to improve Quail, an open-source web accessibility testing tool that will integrate with existing continuous integration processes and developer toolchains."
Please give it a read and share the announcement on your networks. We want to get as much outside involvement as possible from developers, accessibility experts, testers and library architects. With this project we have the resources to build the world's first modern accessibility testing tool for front end applications and web pages. What we need now is the momentum to get it built quickly.
I'm a lazy developer. Probably one of the laziest I know. I try not to commit anything to memory that can be looked up with 2 seconds of typing and a click. If I know someone else knows the answer and they're within earshot I'm definitely not going to sit around and try to figure it out myself. That's not to say I won't work hard or can't learn, but it's all about efficiency in the work place for me.
Great news! The official dates for 2014 Global Training Days have been selected:
Friday, February 28 (or Saturday, March 1)
Friday, May 30 (or Saturday, May 31)
Friday, August 29 (or Saturday, August 30)
Friday, November 14 (or Saturday, November 15)
Drupal 8 Wins: Avoiding the Dead Hook Blues, Part 1 - In August 2013, I spoke with Larry Garfield and Kris Vanderwater in a 90+ minute live Hangout on Air about the origins, details, and implications of the big architectural changes coming in Drupal 8. Today's video and audio podcasts are the first set of "curated" excerpts from that long conversation. We cover Larry and Kris's Drupal backgrounds, early Drupal memories, compare Drupal 4 to Drupal 7 and 8, some pragmatic reasons to choose Drupal, and how to get your head around the Symfony2 framework.
This is not a post about 5 cutting-edge technologies that may become relevant in 2014. This is a post about 5 technologies that are ready to be applied to your site today. However, not enough people are taking advantage of them and, most importantly, you simply cannot afford to ignore them any longer.Deep Analytics - its not about the what but the why and how
A lot is being said about Big Data and a lot may sound irrelevant to most organizations. However, Big Data is not just about the volume of data, it is also about the depth and breadth of user behaviour it can provide insight to. Big Data, at its heart, is the process of driving business decisions on the basis of real-world user data collected in the digital world
We cannot assume that users are rational automatons that carefully follow pre-ordained paths through a site. Analytics need to go beyond visitor numbers and page views (what most analytics software focus on unfortunately). Instead, we have to think in terms of goals met, paths followed and the context that surrounds them.
It is not the absolute numbers that count but the ability to connect all the dots from interactions off your site (e.g. social media, marketing campaigns) to specific actions on your site. Subsequently, that data needs to actually reach the people that can act on it. At times this means the people creating content and dealing with the site daily. They cannot waste time trying to sift through reports in order to glean some knowledge.
The decisions you make based on this deeper understanding of your business may be the single most important thing you do in 2014.
In 2013 Bluespark helped its clients gain more knowledge about their users and their sites through the integration of data in custom content editor dashboards integrated with their Drupal CMS. This made it easier to react to changing user demands. We also built sophisticated tracking techniques that allow our clients to know not only how many times a page was visited but how many times a piece of content appeared in search results, at what positions and whether it was clicked or not.Personalization, adaptive sites, experience management - oh my!
Armed with new knowledge about how people actually interact with your site, you can then begin the task of optimizing the site’s user experience to make it more relevant to the individual users.
The dirty secret of personalization is that it is actually simpler than you think. This is not about complex techniques and sophisticated technologies. In fact, the tools are already here. The key is to think of the different types of users and the context that led them to a certain page and act accordingly. As is the mantra with Semantic Web technologies, "a little semantics can go a long way," so it is with personalization: "A little bit of personalization can convert a lot of users".
Bluespark is developing tools that allow personalization algorithms to dynamically change the content of the page to the specific user context. And our clients (and us!) are already seeing positive user engagement results.Invest in UX not just for end users but for the content creators of your site - Editor Experience
If anything, 2013 is the year people finally stopped arguing about whether good user experience is important or just a nice to have. Good news - we won! The new business software being created proves it. Good user experience leads to profit.
In the CMS world, this means that it is worth your investment to make sure that the people working on your site's content and structure should have powerful tools that are also a pleasure to use. If you don’t, the result will be a site that is badly maintained with stale content. Which means that the initial investment to actually have a nice site is partially lost.
A positive editor experience will make the entire organization participate in improving the site content and in turn improving the experience of potential customers on the site. Investing in UX and design is no longer a luxury few can afford; it is necessary for the success of your business.
Bluespark has done extensive work in adapting the Drupal back-end to the specific needs of organizations to provide them with both a streamlined and pleasurable user experience.Content Strategy - do you know what your content is saying tonight?
The words and pictures that are next to your logo, on your site and across the web via your social media presence, are ultimately what is going to convince a person to buy your product or embrace your cause. A complete content strategy should span the range from defining your organization’s voice to defining who curates content, with what tools, how that content is stored and how can it be delivered to any number of different devices seamlessly.
The Internet of Things is coming - and soon those Things are going to be able to transmit a variety of rich messages. While “mobile first” is a great way to get started, really what we need to be thinking about is content everywhere. How is content on your site displayed on different devices, but also how is your voice and content represented on other websites (Facebook, Twitter, Google+, Pinterest or wherever the people you want to reach actually are).
If 2013 was the year UX finally got accepted as a key aspect of website development lets hope that 2014 is the year content strategy earns the same level of recognition.Service-based architecture - APIs will rule the world
Software runs the world; ergo the ability to connect different software together to complete more complex tasks gives you an advantage.
Think about the different bits of information you use to make decisions. Then think about the different tasks you perform to achieve your objectives. Can those processes be streamlined through the integration of disparate software services? If so, you’ve just given your company a huge advantage--to make better decisions faster, and to automate their implementation.
Most modern services provide APis. If we can get our lights in the house to switch on from our mobile phone, why is it that our CRM is not integrated with our membership administration tool on our website.
We’ve helped several clients to streamline their processes, reduce cost and reduce risk by building service-based architectures that were both more robust and less complex. Whether it is migrating 25000 sites and 3 million pages in a phased manner to new infrastructure; integration of legacy membership systems with a modern membership-management solution or translation automation for an organization dealing with 26 different languages, a service-based architecture that makes use of APIs allows us to provide robust solutions.So there you have it - 5 broad technologies that are ready to be exploited now. Taking advantage of them early on will provide you with an advantage. Drupal as a CMS is a great platform to build on and the wider Drupal community is already working on introducing easy solutions and tools for many of these issues. We at Bluespark are truly excited about 2014! Tags: Drupal PlanetContent StrategyAnalyticsAPIs
As is now a tradition, here is my annual Acquia retrospective. Time to look back at 2013. In your life, you only get an opportunity to do so many things, so you have to focus on doing things that matter. I'm fortunate that Drupal and Acquia are remarkable stories. I take time to write these retrospectives for you and for me. I write them for you, because you might benefit from my experiences or from analyzing the information provided. But I also write them for myself so I don't forget this incredible journey. If you want, you can read previous retrospectives: 2009, 2010, 2011 and 2012.
For Acquia, 2013 was another excellent year. It was our fifth full year in business (i.e. revenue-generating year), and we finished the year with 19 consecutive quarters of revenue growth. In short, 2013 was a year of continued momentum, record bookings and great customer success. With five-year sales growth of more than 84,100 percent, Acquia was identified as the second fastest-growing company on Deloitte's Technology Fast 500 in North America. Acquia was also listed among North America's fastest growing software companies in 2013's Inc. 500. We're all very proud of that.
We hired 208 people this year and ended the year with 412 employees, up from 280 employees at the end of last year. 337 employees are based in the US, with 197 in Burlington, 27 in Portland, and 113 remote employees. We employ 75 people outside of the US, 53 of which are based in our office in Reading, UK. In 2013, we almost doubled our headcount in the Reading and Portland offices. Additionally, we hired 31 interns in 2013.
Acquia grew its customer base to more than 4,000 organizations. Some of the brands we've added as customers include Intel Corporation, Polycom, News Corp Australia, Timex, the National Association of Realtors, the X PRIZE Foundation, Columbia University, McGraw Hill Financial, Bart.gov and the Red Cross.
In 2013, Acquia continued to be focused on providing Drupal support to our customers. In 2013, we reached the milestone of 100,000 support requests received and resolved during our company lifespan. In 2013 alone, we resolved almost 32,000 customer service requests, up 30 percent from 2012. We invested a lot in scaling our support team and on improving overall customer satisfaction and responsiveness. For example, we created a dedicated customer onboarding team. The result is that we spent more time with our customers to better understand their needs and help solve their Drupal questions. In 2014, we'll continue to keep customer success front and center. It's something we are very passionate about.
With regards to Acquia's software products, it was certainly our busiest year. Not only did we continue to invest heavily in Acquia Cloud and Acquia Network, we also launched some new products. Acquia Commerce Cloud was unveiled last quarter, providing a platform for creating content-rich, socially enabled shopping experiences. Acquia Cloud Site Factory was also released, providing a platform for launching and managing hundreds of websites. We unveiled Drupal Commons 3.0, our Drupal-based community platform, that was identified a Social Platform leader by Forrester Research. And we delivered the general availability release of the Mollom Content Moderation Platform, a content moderation platform built for the enterprise.
The cloud continues to prove to be a great way for organizations to save money, manage websites more efficiently and bring them to market faster. And Drupal is no exception to this trend -- in 2013, many organizations decided to standardize on Drupal in a big way, moving away from the variety of different systems -- exactly the vision we laid out in 2010.
And the proof is in the numbers: Acquia Cloud grew from 4,300 AWS instances at the end of 2012 to 7,300 AWS instances at the end of 2013. In aggregate, we're now serving more than 22 billion hits a month or 319 TB of bandwidth. I believe that makes Acquia the largest Drupal infrastructure provider in the world. Some of the Acquia Cloud achievements I'm most proud of include hosting the Grammy Awards (462 million visits) and hosting Red Nose Day during their largest fundraising event ever (£75 million/$113 million raised in one night).Drupal community and Acquia
In 2013, we continued our long track record of giving back to the larger Drupal community.
- We sponsored 77 Drupal events in 2013, helping thousands of Drupal developers connect and collaborate together.
- Our product teams sponsored work on numerous important community modules, such as Media, Organic Groups, and more …
- The authoring experience work for Drupal 8 that we started last year landed in core this year, including WYSIWYG and in-place editing. We also sponsored work on redesigned content creation page and an improved blocks UI for Drupal 8.
- Also on Drupal 8, we sponsored work on the Web Services and Migrate in Core initiatives, donating the Migrate module authors' time.
- We helped set up numerous process improvements to help streamline Drupal 8 core development, including various "hard problems" discussions at DrupalCons to work through complex issues, releasing monthly alpha releases for user and developer feedback, and laying out the criteria for beta 1. We've also helped establish communication channels to help promote what is happening in Drupal 8: the This Week In Core series, and the Drupal 8.0 landing page.
- We helped the Drupal Association to establish Drupal.org Working Groups to provide better leadership and transparency to the Drupal website. Some of our team also helped assist on Drupal.org upgrade and security issues.
I'm particularly proud of Acquia's contributions to Drupal. It's part of our philosophy to give back, and we work hard to do our part by contributing to the Drupal community -- the reason why we exist. I'm proud of this because it is not trivial to give back as much as we do.Conclusion
What I'm most proud of is that we have accomplished all of this "the open source way". Since Acquia's interests are so aligned with Drupal's, we try to raise the tide for the Drupal community at large.
At the end of the day, we're not selling Drupal or cloud hosting. We're selling what can be done with Drupal. The belief in the limitless. No matter what you dream, you can do it, and Drupal will get you there -- and Acquia is here to help you succeed. Thank you for 2013, and we're looking forward to working with more customers that are changing the world.
During the last weekend of January several Drupal contribution sprints will be taking place across the globe. The Swiss chapter will be happening at our office on both days.
Regardless of your knowledge level, if you have built a site in Drupal, you can contribute and are warmly welcomed.
We will split into pairs and work on Drupal core issues. Bring your laptop. If possible, install git before coming and git clone Drupal 8 core.
Pro tip for new folks: you can get a head start also by making an account on Drupal.org and taking a look at the Drupal Ladder.
- Date: 25.1 & 26.1
- Time: 9:00 a.m. - open end
- Location: Amazee Labs, Förrlibuckstrasse 30, 8005 Zürich
- Food & Drink: provided
- Registration: RSVP here
We are looking forward to welcome you for some serious sprinting.
To improve core momentum as we work toward a Drupal 8 beta, we are going to try some added structure in the commit schedule around Drupal 8 alpha releases:
For one week before each alpha release, we will commit only critical and major patches, to encourage focus on these important issues in preparation for each alpha release. (See the documentation on core issue priorities for more information.)
Immediately following the alpha release, there will be a "disruption week". Core maintainers will work with patch authors to schedule commits for patches that are difficult to reroll or are likely to break many other patches (for example, patches that touch dozens of files, or make significant changes to key APIs). The goal here is to help contributors know when to reroll these patches for the best chance of a timely commit, and to manage conflicts with critical, major, and beta-blocking issues. Patches that should be scheduled are identified at the core maintainers' discretion. See the Avoid commit conflicts and Will cause commit conflicts issue tags.
After we've tried this schedule for a couple months, we will re-evaluate it to make sure it is having the intended effect.
The release of the next alpha, drupal 8.0-alpha8, will be January 22, 2014. With that in mind, here is the commit schedule for the rest of this month.
Wed. Jan. 15 - Tues. Jan 21
Only critical and major patches committed.
Wed. Jan 22
Drupal 8.0-alpha 8 released.
Thurs. Jan. 23 - Tues. Jan 28
Disruptive patches committed at core maintainers' discretion. (Schedule in advance with a core maintainer.) Note that January 25 - 27 will be blocked off from scheduled changes, due to the Global Sprint Weekend.
Crawl errors are the bane of every digital marketer-- they seemingly pop up over night and their numbers grow exponentially. Luckily for Drupal marketers there a number of techniques that you can employ to minimize the number of crawl errors that occur and fix the newly created crawl errors on your website. However, before we get started, let's first review a few common crawl errors that you're likely to run into.
Page Not Found - Hard 404 Errors
The hard 404 error is usually the most common 404 error that you'll find when you're reviewing your crawl errors. These types of crawl errors generally occur when a previously published piece of content is deleted or the content is moved to another location without creating a search engine friendly redirect (301 redirect).
Page Not Found - Soft 404 Errors
Soft 404 errors are not quite as common as a hard 404. A soft 404 error occurs when a piece of content is published but has very little content on it or duplicate content. When the page returns a 300 code, it indicates that the page is accessible, but because there is so little content on the page it will not be indexed as it will be classified as a soft 404.
Access Denied - 403 Errors
This is one of the most frequent errors that I run into with Drupal websites. 403 errors typically occur when a previously published page is then unpublished.
Internal Server Errors - 500 Errors
Internal server errors, also known as 500 errors, occur when an unexpected error occurs and the source of the error cannot be identified.
How to Fix Crawl Errors using Drupal
The best way to stop those pesky crawl errors from occurring is by configuring your Drupal website to defend against them. To do so, we recommend installing and configuring the following modules.
- The first thing you'll want to setup is the Pathauto module, which "provides a mechanism for modules to automatically generate aliases for the content they manage." In other words, you can configure Pathauto so that when you publish content, the content's address won't look like "/node/231." Instead, it will use a logical, human and search engine friendly syntax based on the patterns that you set.
- Perhaps the most important module you'll install is the Redirect module. The Redirect module will automatically create a redirect when you change the path of the content. You can also use the Redirect module to manually fix the crawl errors that have occurred in the case that they were not automatically fixed.
- Next stop is the Global Redirect module. The Global Redirect module "searches for an alias of the current URL and 301 redirects if found. Stops duplicate content arising when path module is enabled." While we're on the subject, the Path module, which is integrated into Drupal's core as long as you're running Drupal 4.3 or higher, allows you to rename URL paths. No need to download this module for most of us.
- Finally, the Search 404 module is another important module for preventing 404 errors. If a visitor lands on a page that generates a 404 error, the Search 404 module redirects that visitor to a new page with a internal site search related to the page. The hope with this module is that the visitor finds his piece of content or something similar within the search results.
How to Monitor Crawl Errors
While these modules will help to prevent crawl errors from occurring, they are not a guarantee against crawl errors. We recommend regularly monitoring your crawl errors using the following techniques.
At least once a month, check Drupal's built in reports for the "Top 'page not found' errors" and "Top 'access denied' errors". To find those reports, use the following URLs:
The Link Checker module extends the functionality of Drupal's built in reports. This module provides you with a report of all of the crawl errors that are on your website. The Link Checker module has a highly customizable interface if you only care about crawl errors on particular content types.
Although not specific to Drupal, Google Webmaster Tools is one of the easiest ways of finding your 404, 403, 500 and other errors. In addition to finding your crawl errors, you should submit your XML sitemaps to Google using this tool to increase the number of pages indexed and identify possible indexing issues. Google Webmaster Tools also gives users the ability to run an on demand crawl of websites to identify hidden issues. The Site Verify module can help with the installation of Google Webmaster Tools.
One final tool for monitoring errors is the Screaming Frog SEO Spider. The SEO spider attempts to duplicate the functionality of Google's search engine spiders. You can run a crawl of the site and it will often identify many hidden crawl errors and issues.
There are a lot of moving parts that maintain your website's search engine optimization-- which is why I always recommend using a calendar to keep yourself organized. Setup daily, weekly, monthly, quarterly, and annual reminders so that your can address crawl errors and make sure your website stays at the top of the search engine rankings. Tell us, what techniques do you use to prevent crawl errors?Keep your website crawl error free using these modulesdrupal seo, 404 error, Planet Drupal
In my first post on Internationalization and Drupal we discussed, in detail, why translation is so important and how Drupal determines the correct language to use when serving content to the user.
This next post focus will be on configuring Drupal to use different languages, and then demonstrating how to translate content into the enabled languages.