Skip to Content

Planet Drupal

Syndicate content - aggregated feeds in category Planet Drupal
Updated: 9 hours 48 min ago

Wunderkraut Belgium: Watch our epic Drupal 8 promo video

13 November 2015 - 3:36am
Drupal 8 is coming and everyone is sprinting hard to get it over the finish line. To boost contributor morale we’ve made a motivational Drupal 8 video that will get them into the zone and tackling those last critical issues in no time.
Categories: Drupal

Wunderkraut Belgium: Open Monumentendag

13 November 2015 - 3:36am
Once again Heritage day was a huge succes. About 400 000 visitors visited Flanders monuments and heritage sites last Sunday.  The Open Monumentendag website received more than double the amount of last year's visitors. Visitors to the website organised their day out by using the powerful search tool we built that allowed them to search for activities and sights at their desired location.  Not only could they search by location (province, zip code, city name, km range) but also by activity type, keywords, category and accessibility.  Each search request being added as a (removable) filter for finding the perfect activity. By clicking on the heart icon, next to each activity, a favorite list was drawn up.  Ready for printing and taking along as route map. Our support team monitored the website making sure visitors had a great digital experience for a good start to the day's activities. Did you experience the ease of use of the Open Monumentendag website?  Are you curious about the know-how we applied for this project?  Read our Open Monumentendag case.  
Categories: Drupal

Wunderkraut Belgium: Very proud to be a part of it

13 November 2015 - 3:36am
Drupal Association Executive Director Holly Ross is thrilled that Wunderkraut is joining as first and says: "Their support for the Association and the project is, and has always been, top-notch. This is another great expression of how much Wunderkraut believes in the incredible work our community does." As Drupal Signature Supporting Partner we commit ourselves to advancing the Drupal project and empowering the Drupal community.  We're very proud to be a part of it as we enjoy contributing to the Drupal ecosystem (especially when we can be quircky and fun as CEO Vesa Palmu states). Our contribution allowed the Drupal Association to: Complete's D7 upgrade - now they can enhance new features Hired a full engineering team committed to improving infrastructure Set the roadmap for success.
Categories: Drupal

Wunderkraut Belgium: Adapting solutions based on client input

13 November 2015 - 3:36am
But in this post I'd like to talk about one of the disadvantages that here at Wunderkraut we pay close attention to. A consequence of the ability to build features in more than one way is that it's difficult to predict how different people interact (or want to interact) with them. As a result, companies end up delivering solutions to their clients that although seem perfect, turn out, in time, to be less than ideal and sometimes outright counterproductive.  Great communication with the client and interest in their problems goes a long way towards minimising this effect. But sometimes clients realise that certain implementations are not perfect and could be made better. And when that happens, we are there to listen, adapt and reshape future solutions by taking into account these experiences.  One such recent example involved the use of a certain WYSIWYG library from our toolkit on a client website. Content editors were initially happy with the implementation before they actually started using it to the full extent. Problems began to emerge, leading to editors spending way more time than they should have performing editing tasks. The client signalled this problem to us which we then proceed to correct by replacing said library. This resulted in our client becoming happier with the solution, much more productive and less frustrated with their experience on their site.  We learned an important lesson in this process and we started using that new library on other sites as well. Polling our other clients on the performance of the new library revealed that indeed it was a good change to make. 
Categories: Drupal

Wunderkraut Belgium: A brief history of Support at Wunderkraut Benelux

13 November 2015 - 3:36am
A few years ago most of the requests started with : "Dear Wunderkraut, we want to build a new website and ... "  - nowadays we are addressed as "Dear Wunderkraut, we have x websites in Drupal and are very happy with that, but we are now looking for a reliable partner to support & host ... ". By the year 2011 Drupal had been around for just about 10 years. It was growing and changing at a fast pace. More and more websites were being built with it. Increasing numbers of people were requesting help and support with their website. And though there were a number of companies flourishing in Drupal business, few considered specific Drupal support an interesting market segment. Throughout 2011 Wunderkraut Benelux (formerly known as Krimson) was tinkering with the idea of offering support, but it was only when Drupal newbie Jurgen Verhasselt arrived at the company in 2012 that the idea really took shape. Before his arrival, six different people, all with different profiles, were handling customer support in a weekly rotation system. This worked poorly. A developer trying to get his own job done plus deal with a customer issue at the same time was getting neither job done properly. Tickets got lost or forgotten, customers felt frustrated and problems were not always fixed. We knew we could do better. The job required uninterrupted dedication and constant follow-up. That’s where Jurgen came in the picture. After years of day job experience in the graphic sector and nights spent on Drupal he came to work at Wunderkraut and seized the opportunity to dedicate himself entirely to Drupal support. Within a couple of weeks his coworkers had handed over all their cases. They were relieved, he was excited! And most importantly, our customers were being assisted on a constant and reliable basis. By the end of 2012 the first important change was brought about, i.e. to have Jurgen work closely with colleague Stijn Vanden Brande, our Sys Admin. This team of two ensured that many of the problems that arose could be solved extremely efficiently. Wunderkraut being the hosting party as well as the Drupal party means that no needless discussions with the hosting took place and moreover, the hosting environment was well-known. This meant we could find solutions with little loss of time, as we know that time is an important factor when a customer is under pressure to deliver. In the course of 2013 our support system went from a well-meaning but improvised attempt to help customers in need to a fully qualified division within our company. What changed? We decided to classify customer support issues into: questions, incidents/problems and change requests and incorporated ITIL based best practices. In this way we created a dedicated Service Desk which acts as a Single Point of Contact after Warranty. This enabled us to offer clearly differing support models based on the diverse needs of our customers (more details about this here). In addition, we adopted customer support software and industry standard monitoring tools. We’ve been improving ever since, thanks to the large amount of input we receive from our trusted customers. Since 2013, Danny and Tim have joined our superb support squad and we’re looking to grow more in the months to come. When customers call us for support we do quite a bit more than just fix the problem at hand. Foremostly, we listen carefully and double check everything to ensure that we understand him or her correctly. This helps to take the edge off the huge pressure our customer may be experiencing. After which, we have a list of do’s and don’t for valuable support. Do a quick scan of possible causes by getting a clear understanding of the symptoms Do look for the cause of course, but also assess possible quick-fixes and workarounds to give yourself time to solve the underlying issue Do check if it’s a pebkac and finally, do test everything within the realm of reason. The most basic don’t that we swear by is: never, ever apply changes to the foundation of a project. Support never covers a problem that takes more than two days to fix. At that point we escalate to development. We are so dedicated to offering superior support to customers that on explicit request, we cater to our customers’ customers. Needless to say, our commitment in support has yielded remarkable  results and plenty of customer satisfaction (which makes us happy, too)
Categories: Drupal

Wunderkraut Belgium: I'm running Drupal 6, what do I do?

13 November 2015 - 3:36am
If your website is running Drupal 6, chances are it’s between 3 and 6 years old now, and once Drupal 8 comes out. Support for Drupal 6 will drop. Luckily the support window has recently been prolonged for another 3 months after Drupal 8 comes out. But still,  that leaves you only a small window of time to migrate to the latest and greatest. But why would you?  There are many great things about Drupal 8 that will have something for everyone to love, but that should not be the only reason why you would need an upgrade. It is not the tool itself that will magically improve the traffic to your site, neither convert its users to start buying more stuff, it’s how you use the tool.   So if your site is running Drupal 6 and hasn’t had large improvements in the last years it might be time to investigate if it needs a major overhaul to be up to par with the competition. If that’s the case, think about brand, concept, design, UX and all of that first to understand how your site should work and what it should look like, only then we can understand if a choice needs to be made to go for Drupal 7 or Drupal 8.   If your site is still running well you might not even need to upgrade! Although community support for Drupal 6 will end a few months after Drupal 8 release, we will continue to support Drupal 6 sites and work with you to fix any security issues we encounter and collaborate with the Drupal Security Team to provide patches. My rule of thumb is that if your site uses only core Drupal and a small set of contributed modules, it’s ok to build a new website on Drupal 8 once it comes out. But if you have a complex website running on many contributed and custom modules it might be better to wait a few months maybe a year until all becomes stable. 
Categories: Drupal

Wunderkraut Belgium: Introduction to customer journey mapping

13 November 2015 - 3:36am
So how does customer journey mapping work? In this somewhat simplified example, we map the customer journey of somebody signing up for an online course. If you want to follow along with your own use case, pick an important target audience and a customer journey that you know is problematic for the customer. 1. Plot the customer steps in the journey   Write down the series of steps a client takes to complete this journey. For example “requests brochure”, “receives brochure”, “visits the website for more information”, etc. Put each step on a coloured sticky note. 2. Define the interactions with your organisation Next, for each step, determine which people and groups the customer interacts with, like the marketing department, copywriter and designer, customer service agent, etc. Do the same for all objects and systems that the client encounters, like the brochure, website and email messages. You’ve now mapped out all people, groups, systems and objects that the customer interacts with during this particular journey. 3. Draw the line Draw a line under the sticky notes. Everything above the line is “on stage”, visible to your customers. 4. Map what happens behind the curtains   Now we’ll plot the backstage parts. Use sticky notes of a different color and collect the persons, groups, actions, objects and systems that support the on stage part of the journey. In this example these would be the marketing team that produces the prod brochure, the printer, the mail delivery partner, web site content team, IT departments, etc. This backstage part is usually more complex than the on stage part. 5. How do people feel about this? Now we get to the crucial part. Mark the parts that work well from the perspective of the person interacting with it with green dots. Mark the parts where people start to feel unhappy with yellow dots. Mark the parts where people get really frustrated with red. What you’ll probably see now is that your client starts to feel unhappy much sooner than employees or partners. It could well be that on the inside people are perfectly happy with how things work while the customer gets frustrated. What does this give you? Through this process you can immediately start discovering and solving customer experience issues because you now have: A user centred perspective on your entire service/product offering A good view on opportunities for innovation and improvement Clarity about which parts of the organisation can be made responsible to produce those improvements In a shareable format that is easy to understand Mapping your customer journey is an important first step towards customer centred thinking and acting. The challenge is learning to see things from your customers perspective and that's exactly what a customer journey map enables you to do. Based on the opportunities you identified from the customer journey map, you’ll want to start integrating the multitude of digital channels, tools and technology already in use into a cohesive platform. In short: A platform for digital experience management! That's our topic for our next post.
Categories: Drupal

Wunderkraut Belgium: Taming Facet API paths

13 November 2015 - 3:36am
In combination with the FacetAPI module, which allows you to easily configure a block or a pane with facet links, we created a page displaying search results containing contact type content and a facets block on the left hand side to narrow down those results. One of the struggles with FacetAPI are the URLs of the individual facets. While Drupal turns the ugly GET 'q' parameter into a clean URLs, FacetAPI just concatenates any extra query parameters which leads to Real Ugly Paths. The FacetAPI Pretty Paths module tries to change that by rewriting those into human friendly URLs. Our challenge involved altering the paths generated by the facets, but with a slight twist. Due to the projects architecture, we were forced to replace the full view mode of a node of the bundle type "contact" with a single search result based on the nid of the visited node. This was a cheap way to avoid duplicating functionality and wasting precious time. We used the CTools custom page manager to take over the node/% page and added a variant which is triggered by a selection rule based on the bundle type. The variant itself doesn't use the panels renderer but redirects the visitor to the Solr page passing the nid as an extra argument with the URL. This resulted in a path like this: /contacts?contact=1234. With this snippet, the contact query parameter is passed to Solr which yields the exact result we need. /** * Implements hook_apachesolr_query_alter(). */ function myproject_apachesolr_query_alter($query) { if (!empty($_GET['contact'])) { $query->addFilter('entity_id', $_GET['contact']); } } The result page with our single search result still contains facets in a sidebar. Moreover, the URLs of those facets looked like this: /contacts?contact=1234&f[0]=im_field_myfield..... Now we faced a new problem. The ?contact=1234 part was conflicting with the rest of the search query. This resulted in an empty result page, whenever our single search result, node 1234, didn't match with the rest of the search query! So, we had to alter the paths of the individual facets, to make them look like this: /contacts?f[0]=im_field_myfield. This is how I approached the problem. If you look carefully in the API documentation, you won't find any hooks that allow you to directly alter the URLs of the facets. Gutting the FacetAPI module is quite daunting. I started looking for undocumented hooks, but quickly abandoned that approach. Then, I realised that FacetAPI Pretty Paths actually does what we wanted: alter the paths of the facets to make them look, well, pretty! I just had to figure out how it worked and emulate its behaviour in our own module. Turns out that most of the facet generating functionality is contained in a set of adaptable, loosely coupled, extensible classes registered as CTools plugin handlers. Great! This means that I just had to find the relevant class and override those methods with our custom logic while extending. Facet URLs are generated by classes extending the abstract FacetapiUrlProcessor class. The FacetapiUrlProcessorStandard extends and implements the base class and already does all of the heavy lifting, so I decided to take it from there. I just had to create a new class, implement the right methods and register it as a plugin. In the folder of my custom module, I created a new folder plugins/facetapi containing a new file called This is my class: /** * @file * A custom URL processor for cancer. */ /** * Extension of FacetapiUrlProcessor. */ class FacetapiUrlProcessorMyProject extends FacetapiUrlProcessorStandard { /** * Overrides FacetapiUrlProcessorStandard::normalizeParams(). * * Strips the "q" and "page" variables from the params array. * Custom: Strips the 'contact' variable from the params array too */ public function normalizeParams(array $params, $filter_key = 'f') { return drupal_get_query_parameters($params, array('q', 'page', 'contact')); } } I registered my new URL Processor by implementing hook_facetapi_url_processors in the myproject.module file. ** * Implements hook_facetapi_url_processors(). */ function myproject_facetapi_url_processors() { return array( 'myproject' => array( 'handler' => array( 'label' => t('MyProject'), 'class' => 'FacetapiUrlProcessorMyProject', ), ), ); } I also included the .inc file in the file: files[] = plugins/facetapi/ Now I had a new registered URL Processor handler. But I still needed to hook it up with the correct Solr searcher on which the FacetAPI relies to generate facets. hook_facetapi_searcher_info_alter allows you to override the searcher definition and tell the searcher to use your new custom URL processor rather than the standard URL processor. This is the implementation in myproject.module: /** * Implements hook_facetapi_search_info(). */ function myproject_facetapi_searcher_info_alter(array &$searcher_info) { foreach ($searcher_info as &$info) { $info['url processor'] = 'myproject'; } } After clearing the cache, the correct path was generated per facet. Great! Of course, the paths still don't look pretty and contain those way too visible and way too ugly query parameters. We could enable the FacetAPI Pretty Path module, but by implementing our own URL processor, FacetAPI Pretty Paths will cause a conflict since the searcher uses either one or the other class. Not both. One way to solve this problem would be to extend the FacetapiUrlProcessorPrettyPaths class, since it is derived from the same FacetapiUrlProcessorStandard base class, and override its normalizeParams() method. But that's another story.
Categories: Drupal Drupal 6 Long-Term Support ... for after official support ends!

12 November 2015 - 6:19pm

In case you haven't heard, the Drupal project is discontinuing "official support" for Drupal 6!

Typically, only two major versions of Drupal are supported at once: the latest version, and the previous one. Right now, that means Drupal 7 and 6 are supported.

But when Drupal 8 is released on November 19th, 2015, Drupal 6 will only be officially supported for an additional 3 months (until February 24th, 2016).

Of course, you'll need to update to Drupal 7 or 8 eventually!

But what if 3 months isn't enough time for you to upgrade?

We're happy to announce Long-Term Support (LTS) for Drupal 6, in order to keep your site going long after the end of official support!

Read more to learn what the end of official support means, and the details of our Drupal 6 LTS.

Categories: Drupal

OSTraining: Change Drupal's File Permissions for sites/default and settings.php

12 November 2015 - 4:49pm

If you login to a new Drupal site and check your Status report screen, you may see this warning:

The directory sites/default is not protected from modifications and poses a security risk. You must change the directory's permissions to be non-writable. The file sites/default/settings.php is not protected from modifications and poses a security risk. You must change the file's permissions to be non-writable.

In this video from our Drupal Security class, Robert is going to show you how to fix this warning:

Categories: Drupal

Out & About On The Third Rock: An Engagement Manager’s Guide To Site Building In Drupal 8 – Week 02

12 November 2015 - 3:40pm
More a log than a guide, but you get the idea! Day 1 Day 1’s timebox went on user stories and sprint goals (1 week sprints btw); this sprint’s goals are; main menu, footer menu, social (Twitter) feed static content for pages font face Favicon The allocated time b/w days 2 and 5 are 3 […]
Categories: Drupal

Dries Buytaert: on Drupal, one year later

12 November 2015 - 1:31pm

The web has done wonders to make government more accessible to its citizens. Take the State of New York; is a perfect example of taking a people-centric approach to digital government. The site lets people easily access state government news and services, including real-time public transit updates, employment resources, healthcare information, and more.

One year ago, The State of New York redesigned and relaunched their website on Drupal in partnership with Code and Theory and Acquia. Today, one year later, they’ve nearly tripled the audience to more than 6 million users. The most-visited part of the site is the services section, which aligns well with the governor’s priority to provide better customer service to state residents. Annual pageviews have quadrupled since launch to a record high of more than 17 million and mobile usage has increased 275 percent.

For more details, check out the press release that the State of New York published today.

Categories: Drupal

Pantheon Blog: Panopoly 2.x for Drupal 8

12 November 2015 - 12:48pm
With the 8.0.0 release of Drupal scheduled for November 19th, I wanted to share the Panopoly 2.x plan for Drupal 8 that David Snopek and myself developed. For those who do not know, Panopoly is powerful “base distribution" of Drupal designed to be both a general foundation for site building and a base framework upon which to build other Drupal distributions.
Categories: Drupal

Commercial Progression: Drupal 8 overview and release party, let’s #celebr8d8! (E12)

12 November 2015 - 10:16am

Commercial Progression presents Hooked on Drupal, “Episode 12: Drupal 8 is here, let’s #celebr8d8!". With the official Drupal 8 release date set for November 19th, the CP development crew assembles for an in-depth conversation on all things Drupal 8. We predicted the release date of Drupal 8 to within 3 days on our February podcast.  This time, Hillary Lewandowski will be presenting an overview of Drupal 8 at our next meetup and Drupal 8 release party with Girl Develop It Detroit at Grand Circus. Approaches for migrating Drupal 6 and 7 sites to Drupal 8 are discussed. Changes in the development cycle for Drupal 8 going forward are mused upon. What does it mean that Drupal 8 is built on Symfony and how will the respective development communities merge, we talk it through.

Drupal 8 Release Party: Detroit, Michigan - November 19th

The wait is over, Drupal 8 is here, let's #celebr8d8! Conveniently we had a Drupal meetup scheduled for the same night as the release of Drupal 8 (Thursday November 19th, 2015), so this meetup has just been upgraded to the…

Drupal 8 Release Party: Detroit, USA

Grand Circus has been a gracious host of The Michigan Drupal User Group in 2015.  This has allowed us to meet some of the  members of the Girl Develop It Detroit community and has given rise to this opportunity for co-hosting a demo / training night for all things Drupal.

We know there is a strong development community in Detroit, and we believe this is the season for curiosity in Drupal to bloom.  The full version of Drupal 8 will be released on Nov. 19th.  Now is the time to check it out, and this is the Meetup for you to do it!

Drupal 8 Upgrade and Migration Strategies

With the release of Drupal 8, Drupal 6 website owners are also faced with an imminent deadline for upgrade and migration. Drupal 6 was released in February of 2008.  End-of-life support for Drupal 6 is February 24th 2016.  If you have a Drupal 6 website that needs core support through 2016, now is the time to execute your upgrade to Drupal 7 or Drupal 8.  In this podcast we discuss the options of a Drupal 6 website owner facing this inevitable end of support deadline.

If you have a Drupal 7 website and you are thinking about upgrading to Drupal 8, how do you decide and what should you consider?  We discuss the out of the box User Experience advantages of the Drupal 8 platform with in line editing features as well as some of the object oriented programming advancements of Drupal 8 on Symfony.

Stay tuned for the future release of 50 training videos from OSTraining specifically addressing the upgrade and migration path to Drupal 8 from previous versions of Drupal.

Launching a New Drupal 8 Website

If you are starting a new Drupal web development project, should your default choice be Drupal 8?  Are there some scenarios in which Drupal 7 is still a good candidate for web design and development? Drupal 7 is a mature development platform with long term support secured up to the release of Drupal 9.  This gives Drupal 7 developers and website owners several years of fully supported Drupal 7 development.

Every new Drupal web development project will want to seriously look at Drupal 8 and consider if there is a good reason why they should not take on the project with the latest version of Drupal. The Drupal development community will be very much focused on Drupal 8 and that is where all of the best energy and talent will be working. Going forward, new features and web integration projects will begin with Drupal 8 in mind.

Drupal 8 is Built on Symfony

Our development team has been training up on the Symfony web development framework over the last few years. Dan Reinders has attended several in-person training classes with the folks at KNP Labs, not to mention their online offerings at KNP University. In this podcast, Hillary describes how the move to Symfony shapes the Object Oriented programming future for Drupal 8. Complex website will be able to experience gradual development progress via deprecated function migrations within a predictable software release cycle. This means there will be far fewer hurdles to jump as projects upgrade to new versions of Drupal in the future. This move to Symfony also opens up Drupal development to include a global community of experienced Object Oriented programmers.

Hooked on Drupal Content Team


CHRIS KELLER - Developer



 Podcast Subscription

Tags:  Drupal8, celebr8D8, symfony, Hooked on Drupal, podcast, Upgrade, Migration, Planet Drupal
Categories: Drupal

Mediacurrent: Case Study: Proves the Value of Post-Launch Drupal Support

12 November 2015 - 8:24am
Care's Journey to Drupal
Categories: Drupal

Mediacurrent: The Business Benefits of Drupal 8: Webinar Video

12 November 2015 - 5:57am

The biggest release in Web Content Management history—Drupal 8.0.0—is scheduled for November 19th.

Categories: Drupal

OpenLucius: Automatically verifying entries in Drupal webforms in 4 steps

12 November 2015 - 2:27am

Imagine you would like to have a form on your website that let’s visitors test your Cloud application. We wanted this for people who like to try our Drupal social intranet OpenLucius for free. To achieve this we need at least the following information: email address, name and organization.

We wanted to:

  1. Keep the threshold as low as possible.
  2. Verify the entered email address.
  3. Request additional information.
  4. Avoid spam bots.

We also wanted to automate as much as possible, as to not lose time on spam bots and people that are not serious. In Drupal this is all possible without encrypting a single line: with the use of the popular Drupal modules Webform and Token. Here is how in 4 steps:

Categories: Drupal frontpage posts: DrupalCamp Santiago de Chile 2015

12 November 2015 - 2:26am

DrupalCamp Santiago de Chile - Envía tus Charlas - Submit your talks!!!

DrupalCamp Santiago de Chile is getting closer, the first DrupalCamp in Chile event will be held on 10,11 and 12 December.
We are accepting session submissions until November 15, if you are coming, hurry up and propose your talk.
Register at !
This will be the first major Drupal event with a national and international call to be held in Chile. On 10 and 11 will take place at headquarters of the Economic Commission for Latin America and the Caribbean (ECLAC), United Nations, in Vitacura next to the Bicentenario Park.
On December 12 we will extend the event with in-depth technical presentations and workshops at Faculty of Engineering of the Universidad Central next to Almagro Park.
Be prepared for a broad and diverse event, we have already confirmed the participation of government representatives, experts from different areas and drupalers from Argentina, Peru, Bolivia, Ecuador, Colombia, Costa Rica, Uruguay, Brazil, Spain and Australia.

For more information:
Original announcement of the Camp:

DrupalCamp Santiago de Chile está cada vez más cerca, el primer Drupalcamp en Chile se realizará los días 10,11 y 12 de diciembre.
Estamos recibiendo propuestas de sesiones hasta el 15 de noviembre, si piensas venir, apresúrate y postula tu charla.
Registrate en !
Este será el primer gran evento Drupal de convocatoria nacional e internacional que se realizará en Chile. Los días 10 y 11 tendrá lugar en la sede de la Comisión Económica para Latinoamérica y el Caribe (CEPAL) de Naciones Unidas, en la comuna de Vitacura al lado del parque Bicentenario.
El día 12 de diciembre tendremos charlas técnicas y talleres en la Facultad de Ingeniería de la Universidad Central, frente al parque Almagro.
Prepárate para un evento amplio y diverso, ya tenemos confirmada la participación de representantes de gobierno, especialistas de distintas áreas y drupaleros de Argentina, Perú, Bolivia, Ecuador, Colombia, Costa Rica, Uruguay, Brasil, España y Australia.

Categories: Drupal

Amazee Labs: #celebr8D8 - the Drupal 8 Release Party

11 November 2015 - 11:45pm
#celebr8D8 - the Drupal 8 Release Party Corina Schmid Thu, 11/12/2015 - 08:45

After the beta version and the release candidate 1 it is time for the real deal! Drupal 8 is coming and it’s coming soon; on November 19, 2015.

Since we at Amazee Labs love Drupal and parties almost alike we want to celebrate this very special occasion. And because we really like Drupal we’ve decided not to throw only one but three parties! Yes, that's no typo, it's three parties, one in each of our offices in Austin, Cape Town and Zurich. So if you are anywhere near one these three locations make sure you sign up und join us!

Join the party at our Zurich Office

Celebrate with our Cape Town Team

Party in Austin

Of course you could also join in at any other party near you!

We are super excited to #celebr8D8 with you.

Want to know more about Drupal 8? Check out our blog or read some facts and figures here.

Categories: Drupal

about seo