Skip to Content

Planet Drupal

Syndicate content
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 5 hours 49 min ago

Evolving Web: Upgrading to Drupal 8: Benefits and Gotchas

15 April 2016 - 8:32am

Thinking of upgrading your website to Drupal 8, or using it for the first time on a new project? You've surely heard about the shiny new features that the community has been cooking up. But as with any major step forward, there's a lot of changes to how things work, and not everything is fully ready, so there are challenges to be aware of before you jump into a Drupal 8 project for the first time.

read more
Categories: Drupal

Pronovix: Drupal 8 as a help center: embed documentation with the WalkHub Help Widget

15 April 2016 - 8:20am

Even though it has become much easier to create embedded help experiences, many software products still do very little to integrate their help content into their application. In this post we will explain why embedded help leads to better experiences, why we built our Help Widget, and give you an overview of its architecture.

Categories: Drupal

InternetDevels: Drupal Global Training Days: the 4-part sequel by InternetDevels and Drudesk!

15 April 2016 - 6:31am

Of course, InternetDevels Drupal development company and
 
Drudesk support service couldn’t miss Drupal Global Training
 
Days. And we bet you don’t want to miss reading more about it ;)

Read more
Categories: Drupal

Mediacurrent: Friday 5: 5 Tips to Building a Creative Team

15 April 2016 - 6:18am

We made it to the finish line of another busy work week!

Thanks for joining us for the sixth episode of The Mediacurrent Friday 5. This week, Creative Director Dante Taylor provides 5 Tips to Building a Creative Team. 

He discusses some key points to consider when working with a creative team. Watch the video to learn more about how there are no rules, putting people first, giving sandwich critiques, always keeping your door open, and trusting your teammates.

Categories: Drupal

TimOnWeb.com: JQuery.cookie in Drupal 7

15 April 2016 - 1:26am

A quick tip for all Drupalistas outhere: if you want to use jQuery.cookie in your project, you actually don't have to download and install the library. jQuery.cookie is a part of Drupal 7 and can be included as easy as typing: 

  1. drupal_add_library('system', 'jquery.cookie');

Wondering to ...

Read now

Categories: Drupal

Wunderkraut Belgium: Drupal 8 will be released on November 19

15 April 2016 - 1:26am
We're ready to celebrate and build (even more) amazing Drupal 8 websites.  On November 19 we'll put our Drupal 8 websites in the spotlight...be sure to come back and check out our website.
Categories: Drupal

Wunderkraut Belgium: 77 of us are going

15 April 2016 - 1:26am
People from across the globe who use, develop, design and support the Drupal platform will be brought together during a full week dedicated to networking, Drupal 8 and sharing and growing Drupal skills. As we have active hiring plans we’ve decided that this year’s approach should have a focus on meeting people who might want to work for Wunderkraut and getting Drupal 8 out into the world. As Signature Supporting Partner we wanted as much people as possible to attend the event. We managed to get 77 Wunderkrauts on the plane to Barcelona!  From Belgium alone we have an attendance of 17 people. The majority of our developers will be participating in sprints (a get-together for focused development work on a Drupal project) giving all they got together with all other contributors at DrupalCon. We look forward to an active DrupalCon week.   If you're at DrupalCon and feel like talking to us. Just look for the folks with Wunderkraut carrot t-shirts or give Jo a call at his cell phone +32 476 945 176.
Categories: Drupal

Wunderkraut Belgium: Open Monumentendag

15 April 2016 - 1:26am
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

15 April 2016 - 1:26am
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 Drupal.org's D7 upgrade - now they can enhance new features Hired a full engineering team committed to improving Drupal.org infrastructure Set the roadmap for Drupal.org success.
Categories: Drupal

Wunderkraut Belgium: Adapting solutions based on client input

15 April 2016 - 1:26am
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

15 April 2016 - 1:26am
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?

15 April 2016 - 1:26am
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

15 April 2016 - 1:26am
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

15 April 2016 - 1:26am
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 url_processor_myproject.inc. 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 myproject.info file: files[] = plugins/facetapi/url_processor_myproject.inc 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

Appnovation Technologies: Improving Drupal Content Management Features

15 April 2016 - 12:00am

In the marketing world, content is still king. The internet is an endless ocean of content that is easily accessible at any time, on any device.

Categories: Drupal

Mediacurrent: Dropcast: Episode 18- Try Try Again

14 April 2016 - 1:58pm

This episode we are going to have an interview with Matt Davis, to talk about his work with Weather Underground, and decoupling Drupal from the presentation layer, or die trying. This is our second third take on Episode 18, and we need to thank Oscar Mejivar for coming on. We will be re-recording that episode at a later date, so please tune in because outside my horrible production skills, it’s was a great topic and we want to share it with you. Stay tuned.

Categories: Drupal

Drupal core announcements: Drupal core security release window and 8.1.0 release on Wednesday, April 20, 2016

14 April 2016 - 11:25am
Start:  2016-04-19 12:00 - 2016-04-21 12:00 UTC Organizers:  catch xjm David_Rothstein Event type:  Online meeting (eg. IRC meeting)

The monthly security release window for Drupal 8 and 7 core will take place on Wednesday, April 20.

This does not mean that a Drupal core security release will necessarily take place on that date for any of the Drupal 8 or 7 branches, only that you should watch for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).

This is also the release window for Drupal 8.1.0, the next scheduled minor release of Drupal 8. To ensure a reliable release window for the patch release, there will be a Drupal 8.1.x commit freeze from 12:00 UTC Tuesday to 12:00 UTC Thursday. Read the release candidate announcement for more information on the minor release.

The next window for a Drupal core patch (bug fix) release for all branches is Wednesday, May 04. (Drupal 6 is end-of-life and will not receive further releases.)

For more information on Drupal core release windows, see the documentation on release timing and security releases, and the discussion that led to this policy being implemented.

Categories: Drupal

DrupalCon News: DrupalCon Celebrates Diversity at 'Women in Drupal'

14 April 2016 - 10:42am

While we are above the tech average, we are still always striving to foster inclusivity and embrace the involvement of individuals across the gender spectrum. To help celebrate where we are and where we are going, we would like to formally invite you to Tuesday's Women in Drupal event. This event is open to all women, trans* individuals, those who identify outside of the gender binary, and allies.

Categories: Drupal

Palantir: On the Air with Palantir podcast, Ep. 04: Everything You Need to Know About DrupalCon New Orleans

14 April 2016 - 8:41am

DrupalCon is just a few weeks away in New Orleans, so this time around our Account Manager Allison Manley is joined by our CEO and Founder George DeMet, Drupal veteran and PHP guru Larry "Crell" Garfield, and Senior Front-End Developer Lauren Byrwa. They share thoughts about the conference generally, what they're excited about specifically, and what they're expected from the Driesnote, among other topics.

iTunes | RSS Feed | Download | Transcript

We'll be back next Tuesday with another episode of the Secret Sauce and a new installment of our long-form interview podcast On the Air With Palantir next month, but for now subscribe to all of our episodes over on iTunes.

Heading to DrupalCon this year? On the fence and need to be convinced? Let's schedule a time to talk so we can explain why you should attend this conference.


Transcript


Allison Manley [AM]: Hi, and welcome to On the Air with Palantir, a podcast by Palantir.net where we go in-depth on topics related to the business of web design and development. It’s April 2016, and this is episode #4.

I’m Allison Manley, an Account Manager at Palantir, and today we are going to give a preview of what to expect from the upcoming DrupalCon in New Orleans which is taking place May 9th through the 13th. The website is drupalcon.org if you want to see more. I’m a newbie to DrupalCon — this will be my very first one — so I gathered a bunch of my seasoned colleagues here at Palantir who have attended in the past to get their thoughts on the upcoming conference.

I am here with three of my fabulous colleagues that are going to be attending DrupalCon with me. So I have Lauren Byrwa, who’s one of our senior front-end developers.

Lauren Byrwa [LB]: Hi!

AM: George DeMet, founder and CEO.

George DeMet [GD]: Hello.

AM: And Larry Garfield, Senior Architect and Community Lead. How are you?

Larry Garfield [LG]: Hello, world.

AM: So what we’re doing here is basically a preview of DrupalCon. DrupalCon is coming up in a couple of weeks, in New Orleans, which is very exciting. How many DrupalCons is this for
each of you?

LG: I think this will be #21.

AM: Out of how many? How many have there been?

LG: Maybe 25? I’m a staple at this point [laughs].

GD: It’s a good question. Not as many as you, Larry, but probably, if I had to guess, between 15 and 20.

LB: I’m actually only at #2 for Cons. So not a whole lot compared to these guys.

AM: I’m a complete newbie, so we’ll get to that later — what I can expect — but before we get to what most people or new people can expect from DrupalCon, or what DrupalCon is about — we know that Drupal was started by Dries Buytaert. Did I pronounce that right?

LG: Close enough for an American [laughs].

AM: What is the correct pronunciation, please?

LG: Well, I’m an American too. ‘Drees Boy-thart’ I think is closer, but don’t quote me on that. Dries, feel free to correct us.

AM: I’m sure he will later [laughs]. So what is DrupalCon about?

LG: DrupalCon is the summit of the community. It is the largest Drupal in-person event in the world by a very wide margin. It’s a place for the whole community of whatever stripe to gather and discuss, learn, teach, plan, work, play, drink, and several other things along the same lines. A lot of conferences are very developer-centric or very business-centric, or very whatever. DrupalCon is — these days, DrupalCon is a Web conference with a Drupal angle to it. There’s sessions for back-end developers, there’s sessions for front-end developers, there’s sessions for project managers, there’s sessions for content strategists, there’s sessions for business owners — whatever you do, if it involves Drupal or the Web in some way, there’s at least a couple of sessions that are worth going to for you.

GD: I would agree, and I would say that even if you don’t do Drupal or you’re not someone who’s really immersed in the technology or the community, it’s still a conference with really great value. You can get a lot out of it, and I think particularly for folks who are new to DrupalCon, it’s a really great way to get immediately connected with the community. And it’s often a very overwhelming way. We’re a very friendly and welcoming community, sometimes overly so.

LB: I would like to think of DrupalCon as our family reunion, for all Drupalers. We’re there to learn, we’re there to share, but mostly we’re there to collaborate. And that can happen in sessions, that can happen at happy hour,that can happen anywhere. But it’s a great way to get plugged into the community.

AM: So I am a newbie, as I said — this will be my first. So what should I expect from DrupalCon? Am I just going to walk in and be completely overwhelmed at first?

GD: Yes.

AM: [laughs].

LB: I think at my first DrupalCon — overwhelmed? Yes, definitely expect to be overwhelmed no matter what. But feel comfortable, feel welcomed. Everybody is excited for newcomers. Everyone is excited to get to know you, to hear your ideas. So stand up and talk, and listen, and ask questions. And go up to people that intimidate you, and tell them that you’re a huge fan and that you work with their tools every day and that you like what you saw in this blog post. And they’ll be flattered and want to know what you think and why or why not you agree or disagree. But talk to everybody. Talk to them on Twitter, talk to them in person, talk to them at bars — everything you can do to soak up as much information as possible. That’s always my number one.

LG: The main thing you should expect at DrupalCon is 3000 introverts playing extroverts, who really want to talk to you and teach you things because that’s what they do. And if you’re up for talking to people you’ve only heard of, or never heard of, and just learning from every person you run across, you’ll do just fine.

GD: And I think — so when we’re at our booth, every year without fail I’ll be standing there and someone will just kind of come up to me, and they’ll have The Look in their eyes. It’s very clear that this is their first time, they’re feeling very overwhelmed. And it’s really funny, this happens every time, they’ll make eye contact, come over to the booth, pull out their program guide, and be like, where do I go? And there’s so many different things you can do and places you can go and sessions you can experience, and it really is about — I think for folks who are going, it’s really taking a look at the sessions, figuring out ‘what do I want to get out of this event’, and focusing on that. And if you are getting overwhelmed, just find a friendly face, and they’ll more than likely be able to help you out and point you in the right direction – ‘oh yeah, I know the person doing that session, they’re awesome, go to that session if you want to learn about this, so-and-so is like the world’s expert on that’. All kinds of opportunities to just soak everything in, and learn what you can. It’s a really fun, really intense time.

AM: Great, I’m really looking forward to it. So every year Dries gives a keynote. And it’s fairly spectacular, I’ve seen a bunch of them on YouTube. They’re very involved. So what are you anticipating this year from the Driesnote, as he calls it?

LG: I have no idea what Dries is planning. I think the best keynote he’s given in recent years was in Amsterdam, where he was talking about actual practical changes to our process. That’s where he introduced the plan for putting credits on the site, which got implemented later. And I think that’s been a great thing to encourage contributions from companies and clients and commercial organizations, which we absolutely need.

I’d like to see something inward-looking. By that point Drupal 8.1 will have just come out, and that’ll be the first time we’ve done that type of release in, I think, ever in Drupal. So I suspect he’ll be talking about that and the implications of being able to evolve the system more smoothly than in the past. That’s my prediction, such as it is.

[this was cut from the original recording due to audio issues, but is left intact for the transcript]

GD: I’m hoping that Dries will take this opportunity to talk a little bit more about what the vision and future direction of Drupal is going to be, not just from a technical standpoint but really from an — answering the question, why does Drupal exist? What we’ve seen over the last few years, particularly as we’ve been through the Drupal 8 cycle, is that Drupal has changed and evolved tremendously. And at the same time the kinds of people that use Drupal, and the ways that they are using it, have changed tremendously. And I think that a lot of folks in the community have moved along with those shifts, but others might be feeling a little left behind, like they’re not really sure. Maybe if you’re somebody that’s joined Drupal at a point in the past, and you’ve had a particular motivation for doing so, the project and the community may be very different now. I think as we go through that change and that evolution, having a shared understanding and grounding in what our shared values are as a Drupal community and a project would be really cool to hear from Dries.

LB: I would say we’re actually at a place right now where we don’t entirely know what’s next for Drupal. We’re not waiting on D8 any more — there’s a whole slew of things out there. And so I agree that the future of Drupal is going to be a big topic. I think in addition to that, this is our good chance and this is Dries’ good chance to really press on contribution, and to recruit people.

A lot of our hardcore developers that helped build D8 are feeling a little burnt out. They too are celebrating the release, but in addition to that, they’re feeling a little burnt out after years and years of press to get it there. So I think contribution is going to be a really big topic this year — trying to figure out how to get people involved and how to get new blood in the system and new
ideas. To really push us towards that future, that’s going to be important.

AM: That’s a lot to cover in one keynote [laughs].

GD: The expectations are always incredibly high for these things. And it’s really often almost too much to ask, that one person will be able to cover this much in an hour or an hour and 15 minutes. One thing I’ve seen is that sometimes, when Dries delivers, he really delivers in a really great way. But I also know that it’s really hard to do that. So hopefully everything will click in place. I’m looking forward to it.

AM: Me too. So what are the big talking points in Drupal right now? Obviously I can assume Drupal 8. What else do you think will be the big things?

Categories: Drupal

Zyxware Technologies: Question Bank for evaluating Drupal Developers as part of the Drupal Open Curriculum Initiative

14 April 2016 - 2:52am

We have been involved with the Drupal Open Curriculum initiative under the Curriculum and Training group in groups.drupal.org for the last few months and have been helping build up the content for the initiative. One of the important pieces of content that is expected to be developed as part of this initiative is the question bank with objective type questions that can be used to evaluate the progress of the training of Drupal developers.

DrupalgiveDrupal TrainingDrupal PlanetTeaching DrupalNews
Categories: Drupal


Google+
about seo