KnackForge: How to update Drupal 8 core?

Planet Drupal - Sat, 2018/03/24 - 6:01am
How to update Drupal 8 core?

Let's see how to update your Drupal site between 8.x.x minor and patch versions. For example, from 8.1.2 to 8.1.3, or from 8.3.5 to 8.4.0. I hope this will help you.

  • If you are upgrading to Drupal version x.y.z

           x -> is known as the major version number

           y -> is known as the minor version number

           z -> is known as the patch version number.

Sat, 03/24/2018 - 10:31
Categories:

Valuebound: Drupal 8: How to create a custom block programatically

Planet Drupal - Mon, 2016/12/19 - 8:33am
Drupal 8: How to create a custom block programatically Jaywant.Topno Mon, 12/19/2016 - 02:33
Categories:

Valuebound: Drupal 8: Custom Block Creation programmatically

Planet Drupal - Mon, 2016/12/19 - 8:33am
Drupal 8: Custom Block Creation programmatically Jaywant.Topno Mon, 12/19/2016 - 02:33
Categories:

MTech, LLC: Migration of CSV Data into Paragraphs

Planet Drupal - Fri, 2016/12/09 - 9:59pm
Migration of CSV Data into Paragraphs

With the daily work of the office it is natural that there are challenges and potential research topics. With the addition of our developer Lucas as a Drupal core Migrate system maintainer, we decided to to delve into the little documented area of migrating data into paragraphs.

Paragraphs is the new way of creating content. It allows site builders to make things cleaner so they can give more editing power to their end users.

Charlotte León Fri, 12/09/2016 - 14:59
Categories:

Brian Osborne: Preventing Drupal 8 from applying image styles to GIFs to preserve animation

Planet Drupal - Fri, 2016/12/09 - 8:44pm

I'm working on a site where the editorial staff may occasionally produce animated GIFs and place them in an article. Image styles and animated GIFs in Drupal don't play nice out of the box. Drupal's standard image processing library, GD, does not preserve GIF animation when it processes them, so any image styles applied to the image will remove the animation.

Categories:

Palantir: Competitive Analysis on a Budget

Planet Drupal - Fri, 2016/12/09 - 5:10pm
Competitive Analysis on a Budget brandt Fri, 12/09/2016 - 10:10 Michelle Jackson Dec 9, 2016

User research is a key element in meeting the needs of your audience, but can it be done on a budget? We think so.

In this post we will cover...
  • Why competitive analysis is needed

  • A cost-effective approach to meeting the needs of your audience

  • How to conduct competitive analysis on a budget

  • How to build a competitive analysis matrix

We want to make your project a success.

Let's Chat.

Your budget is tight. Project time constraints won’t accommodate extensive user interviews or surveys.

These common project parameters can make it challenging to understand the needs of the audience your website serves. Competitive analysis is an affordable way to evaluate and understand the ways in which competitor sites are succeeding or failing to meet site visitor needs.

By the time you are finished reading this post, you will have the know-how to do a competitive analysis for your organization or company’s website and will be able to see how your website measures against the competition.

What is competitive analysis?

Competitive analysis is a user experience research technique that can help you see how your site compares with competitor websites in terms of design and functionality. It can also lead to better decision-making when selecting new design and technical features for your site (e.g. search filter terms or search listing display).

Competitive analysis evaluates competitor sites at a level that goes further than first impressions. It can help you understand if the competition’s efforts to meet user needs are working before you invest in and implement new designs and technical features.

Let’s imagine you have been tasked with redesigning the Detroit Pistons website and are reviewing and bookmarking some of your competition’s websites. Taking a look at direct competitors is the first step.

First, we’ll take a look at the Chicago Bulls and the Detroit Pistons - two direct competitors. The two teams are considered direct competitors because both are professional basketball teams that offer the same service and function in the same way. Ticket sales, merchandise, team branding, and game schedules are some of the main priorities of website visitors. Both websites are hosted by the NBA.

Each team uses a different approach when it comes to presenting information in the navigation. Let’s consider how the two teams differ in terms of menu labeling and hierarchy. Tickets come first and foremost for both teams. Since tickets generate revenue, prominent placement in the navigation underscores the high priority of this transaction. With the exception of “News,” the two teams place the same emphasis on “Team” and “Schedule.” At a glance the Chicago Bulls navigation is more effective in their use of menu terms that reflect distinct priorities and desired user actions on the site.

Figure 1: Chicago Bulls navigation

The Detroit Pistons’ navigation offers a host of items that may distract the user from completing key priority actions (e.g. buy a ticket, review the schedule, check out the team or buy merchandise), which are clearly prioritized in the Chicago Bulls navigation.  Looking at the Detroit Pistons navigation, it is not clear what different actions the visitor should take on the site using the navigation. “Fan Zone,” “Game Night,” could be housed under “Community.”  Diving into the “Video” navigation item, “Fan Experience,” has a similar connotation to Fan Zone which creates a more fragmented experience for visitors navigating the site. “Instagram” is listed under “Video” which may be redundant since there is already a social media icon for Instagram in the main navigation.   

Figure 2: Detroit Pistons navigationFigure 3: Detroit Pistons navigation | Video

Now that we’ve done a cursory comparison of how two direct competitor websites use their navigation, let’s talk about how competitive analysis can meet user needs without breaking the bank.

Competitive analysis on a dime

Competitive analysis is flexible. This type of research method can be customized to your budget and project needs. Evaluating the navigation for the Detroit Pistons and Chicago Bulls took about 15 - 20 minutes, but the impact (for the Detroit Pistons) of simplifying the navigation could be substantial in improving site visitor experience.

Competitive analysis can run anywhere from a few hours (if you have a tight budget) to several weeks. Research by experts in your industry and publicly available data on user trends, behavior and needs can supplement evaluation and assessment of your site against the competitions’ sites.

In addition to evaluating the usability of the features and designs of your site along competitor sites, you can also perform user tests on competitor websites to validate their assumptions about what does or doesn’t work for users. We typically implement competitive analysis after conducting a series of interviews with stakeholders. Like our process for developing personas, our competitive analysis methodology is also based on high-level stakeholder input, data produced by clients, and site analytics.

Competitive analysis in action

The competition

Selecting four-to-seven competitor sites to evaluate alongside your site is a critical first step. Depending on time and budget, competitive analysis can focus on direct competitors, or partial, parallel, or even analogous competitors.

Competitor types

  • Direct - offer the same service/functions in the same way
  • Indirect - offer the same service/functions in a different way
  • Partial - compete with some, but not all services/functions
  • Parallel - offer a similar service/function to a similar audience via a similar channel
  • Analogous - a non-competitor that might give ideas about how to provide functions in a better way

Let’s use the Detroit Pistons as our point of comparison and see how other sports and entertainment offerings in the Chicago area relate to the Detroit-based professional sports team.

The Northwestern Wildcats is an indirect competitor. The Chicago-based basketball team offers the same service as Detroit Pistons, but in a slightly different way. The fan base, or audience, is slightly different and the team competes against other college sports teams in the NCAA. Merchandise associated with the Wildcats primarily focuses on the institution and not the team itself. The team is also based in a different market.

Chicago Blackhawks, while a completely different sport, is a parallel competitor. Both hockey and basketball are spectator sports that offer similar services during the same season, and have a fan base with some overlap. Both the Detroit Pistons and Chicago Blackhawks require that spectators spend time and/or money watching a professional team compete to score against an opposing team. Both teams also sell merchandise.

Comedy theater, The Second City, is a partial competitor. The Second City not only sells tickets for live entertainment, but also has educational offerings for professionals seeking to hone their improvisation technique and relate better to customers. By including educational offerings, Second City’s services differ slightly from those offered by the Detroit Pistons.

An analogous competitor is Hamilton Broadway. The musical provides entertainment to spectators, sells merchandise and relies heavily on ticket sales. The show is also seasonal, although the show’s duration is shorter than professional and college sports.

Competitive analysis can help establish a baseline for web design in your industry. Choosing competitor sites that capture different segments of your market and have had recent redesigns is key. It can help us understand how user needs are met by competitor websites serving the same or similar audiences. It can also help us evaluate if a competitor’s newly minted design and technical features are meeting user needs in a new and improved way. This, in turn, can lead to better and more cost-effective decisions that consider site visitor needs when designing and building your site.

Dimensions

Identifying the criteria for evaluating competitor sites is a crucial second step. Navigation was just one dimension to consider when looking at the Detroit Pistons and the Chicago Bulls. We consult closely with clients when selecting dimensions. Dimensions may include:

  • Content (e.g. stories featuring specific audiences or influential people)
  • Design (e.g. organization leader profiles)
  • Technical features (e.g. use of filters for search functionality)
  • Specific pages (e.g. Home page)
  • User support (e.g. FAQ)

During the review and evaluation process, you may add additional dimensions and dimension subcategories if new trends are uncovered when looking at competitor websites.

  • Dimension - Descriptive content
  • Subcategory 1 - Homepage
  • Subcategory 2 - Use of video
So what next?

As a first step, you develop research questions to guide your evaluation of each site.

  • How does each website help users achieve key tasks?
  • How is content prioritized on pages where key tasks take place?
  • What types of descriptive content is featured on the Homepage of each site?

Then you build a competitive analysis matrix featuring competitors (x axis) and dimensions (y axis) in a spreadsheet.

For the Detroit Pistons and its competitor sites, you can list notes about certain features of the current sites. For the navigation, you might review and compare the number of items in the primary navigation, the prioritization of navigation items and/or the type of language (formal/informal) used for navigation terms.

For tickets sales, you might look at how information about tickets and ticket promotions are presented on the homepage. You can compare display of ticket information on the tickets landing page for each site. When looking at the game schedules, you might consider how and if visitors can access the schedule from multiple parts of the website.

Use this simple competitive analysis matrix to see how these sites measure up against each other!

Figure 4: Competitive analysis matrix

Next, we:

  • Speak with stakeholders who manage the site
  • Identify the types of competitors (e.g. direct, indirect, partial, parallel and/or analogous)
  • Select four-to-seven competitor sites
  • Create a preliminary list of dimensions
  • Evaluate competitor sites
Once you’ve done your research and completed the matrix

Now it’s time to tackle competitive analysis.

  • Identify patterns and similarities across competitors
  • Highlight competitor site strengths and trends
  • Handpick design elements, technical features and content that work well
  • Collaborate with design, technical, and stakeholder experts to validate your findings

Citing your work and providing documentation in the matrix provides a point of reference for clients and team members. It can also help validate conclusions. Presenting your findings, screenshots, and recommendations in a slide deck or report can help design, technical, and stakeholder experts understand and draw inferences about your research for consideration during the design and technical implementation of your site.

In sum

Competitive analysis is an affordable user experience technique. It can establish a baseline for how competitor sites are doing. You can learn from competitor site successes and failures to make cost-effective decisions during the design and build of a site. Lastly, competitive analysis can help us achieve user-centered design and development outcomes while avoiding the web design and technical blunders of the competition.

We feel strongly that competitive analysis and other such strategy work is essential to a project's success. Let's schedule a time to talk so we can share our approach to getting to a place of success for your organization and project.

Stay connected with the latest news on web strategy, design, and development.

Sign up for our newsletter.
Categories:

Ixis.co.uk - Thoughts: Bringing pages to life with web animation

Planet Drupal - Fri, 2016/12/09 - 12:25pm

We’re using animation in a few places on ixis.co.uk, mostly subtle movements to try and inject a bit of life into the design. The key thing when we were adding these animations was to keep them subtle. If at any point they make the actual content on the site harder to read then we've failed.

On mobile, the menu button animates into a close button when it’s opened. This is fairly simple. When the menu is opened, we add an open class to the button, and use some CSS3 transforms to move things around. The relevant Sass is below, the main thing is we add a 0.3s transition on opacity and transforms, and then just move things when the open class is added.

.navbar-toggle { .icon-bar { transition: opacity 0.3s, transform 0.3s; } &.open { .icon-bar-1 { transform: translate(0, 8px) rotate(45deg); } .icon-bar-2 { opacity: 0; } .icon-bar-3 { transform: translate(0, -8px) rotate(-45deg); } } }

The transforms occur in order from left to right, even though they animate all at once, which is why we move first, and then rotate. Otherwise the movement would be relative to the new rotation.

Our new service icons are SVGs, which means we can target individual elements within the icon to animate, as long as the SVG is inline and not embedded with an img tag or background-image style. To make life easier we added theme implementations for them on the Drupal side, so they can easily be added and reused. Then we have an icon-development.html.twig file that contains the SVG.

/** * Implements hook_theme(). */ function example_theme($existing, $type, $theme, $path) { return array( 'icon_development' => array( 'variables' => array(), ), // ... ); }

We’re using CSS3 keyframes for the animations themselves, which means we can easily trigger them when we scroll them into view. In our Sass a lot of the values are shared with placeholders, but I’ve tried to simplify them here, and it’s only showing the animation for one part of one of the icons.

#service-development { .bracket-left { animation-duration: 1s; animation-timing-function: ease; animation-iteration-count: 1; animation-fill-mode: forwards; animation-play-state: paused; animation-name: developmentBracketLeft; } &.scrolled-to .bracket-left { animation-play-state: running; } } @keyframes developmentBracketLeft { 0% { transform: translate(-4px, 0); } 100% { transform: translate(0, 0); } }

Since all of our animations are fairly short, we had to make sure they’d only trigger once they’re visible, otherwise it’s just a waste of time. So we’re using waypoints to add a ’scrolled-to’ class when animations should trigger. Javascript is only used for these triggers, the animations themselves are pure CSS, so they benefit from hardware acceleration. We're using this approach for virtually all of our animations, from the service icons down to subtle fade in effects on things like heading banners, testimonials and client work pages.

(function ($) { Drupal.behaviors.magicksServiceAnimation = { attach: function (context, settings) { $('.view-services').waypoint({ offset: 'bottom-in-view', handler: function() { $('.view-services').addClass('scrolled-to'); }, }); } }; })(jQuery);

The fade in effect is a combination of 2 transitions. It moves from 0 opacity up to 1, and it moves 100px up and into it's correct position. This particular effect is all wrapped in a Sass mixin, so it can be easily reused on new elements, and only ever needs to be changed in one place.

On the blogs page we have infinite scrolling, with a rotating Ixis logo to show that new content is loading in. Not much to this one: it’s the standard Drupal Ajax progress throbber, we’ve just styled it with CSS and animated with keyframes.

Categories:

Cheeky Monkey Media: Improve Website Performance & User Experience with PHP 7: An Exclusive Look at How Cheeky Monkey Media Did It

Planet Drupal - Thu, 2016/12/08 - 11:17pm
Improve Website Performance & User Experience with PHP 7: An Exclusive Look at How Cheeky Monkey Media Did It shabana Thu, 12/08/2016 - 22:17 PHP 7 Upgrade Gives Cheeky Monkey an Extra Little Something

When we decided to convert the Cheeky Monkey Media corporate site to PHP 7, we expected some improvements in web performance

  • We expected the site to run faster and smoother.
  • We expected the page loads to be quicker.
  • We expected these results to leave the end-user (the individual viewing the site) to have a more satisfactory user experience.

In reality, we got all these things, plus a new-and-improved corporate site with some mega pizzazz. The switch to PHP 7 gave our site renewed energy and speed, giving the end-user, blazing fast page loads and an overall quality experience.

You can make the shift too. Contact us today.

Categories:

Lullabot: Talking Laravel with Matt Stauffer

Planet Drupal - Thu, 2016/12/08 - 10:00pm
Matt & Mike talk with "Laravel Up and Running" author Matt Stauffer about the Laravel PHP framework and how it differs from PHP and Drupal as a whole. They are joined by Lullabot developers Andrew Berry and Matt Robison.
Categories:

roomify.us: Roomify releases community edition of Roomify for Accommodations

Planet Drupal - Thu, 2016/12/08 - 9:27pm
We are thrilled to announce that as of today, roomify for accommodations is freely available and, as always, completely open source! Today we're going to share some of our motivations for making rfa widely available, and talk about some of the projects we hope to see in the community.
Categories:

Drupal Modules: The One Percent: Drupal Modules: The One Percent — Form Placeholder (video tutorial)

Planet Drupal - Thu, 2016/12/08 - 8:52pm
Drupal Modules: The One Percent — Form Placeholder (video tutorial) NonProfit Thu, 12/08/2016 - 13:52 Episode 11

Here is where we bring awareness to Drupal modules running on less than 1% of reporting sites. Today we'll look at Form Placeholder, a module which will replace your form's textfield labels with placeholder text.

Categories:

Mediacurrent: Dropcast: Episode 26: Let Us Give Thanks

Planet Drupal - Thu, 2016/12/08 - 7:55pm

Recorded Nov 30, 2016

This episode, the whole crew is together again, and since we recorded it sort of close to the Thanksgiving holiday, we talk about the things we are most grateful for in the Drupal community. As always we have Drupal News, featured blog posts and the ever popular, Final Bell.

Categories:

Drupal.org blog: What’s new on Drupal.org? - November 2016

Planet Drupal - Thu, 2016/12/08 - 6:27pm

Read our Roadmap to understand how this work falls into priorities set by the Drupal Association with direction and collaboration from the Board and community.

The engineering team at the Drupal Association had much to be thankful for in November. With the support of the wonderful volunteers in our community and the contributions of our Supporting Partners we were able to deliver some great tools for the project. Let's dive and see what's new.

Drupal.org updates Promoting Drupal by Industry

In November we finished the technical scaffolding for the upcoming industry pages, and began working with the wider Association team on content development for these pages. Because we were ahead of our internal targets for this page and we felt it would add significant value, we've also added the ability to geotarget content on these industry pages.

This is the first instance of geo-targeting on Drupal.org, and we'll be using it to help connect Drupal evaluators with regionally appropriate content and partners on these pages. Work on the industry pages is ongoing, but we're excited to bring them to you soon.

Developer Tools Evaluation

During November the engineering team also had a two day retreat here in Portland, OR with webchick - one of the members of the Technical Advisory Committee. We used this retreat to do a deep dive into the current state of developer tools on Drupal.org, and to evaluate our options to continue evolving the tools we offer to the community.

We gave a summary of our exploration along with some next steps to the Drupal Association Board on November 22nd. You can find the minutes and a recording here.

Core release packaged with --no-dev composer dependencies

Starting with the Drupal 8.2.3 release, we are now packaging full releases of Drupal core with --no-dev composer dependencies. This means that packages downloaded will not include extraneous developer extras that should not be used in production sites, and that the release packages will be smaller. We will continue to package dev releases with the dev dependencies.

Feature branch testing support

Drupal.org allows maintainers to create feature branches for issues by using the name format [issue#]-[short-description]. Any commits made to a branch in this format will appear in the sidebar of the associated issue. To improve the utility of these feature branches, DrupalCI patch file tests now also run on push to these branches.

To add tests, users can simply click on the 'add test' link beneath the git branch in the issue sidebar, or click on the existing test result bubble to re-test or add a new test. Since this feature was introduced we've run over 200 issue branch tests.

Project maintainers can add Documentation Guides


We're continuing to support the migration of documentation to the new documentation system, and we've now enabled Project Maintainers to add related documentation guides to their projects. Once added, the related projects will appear on the documentation guides, in the sidebar.

Documentation Maintainers can find their Guides

Many community volunteers have stepped up to become maintainers of the new documentation guides. We want to make sure we're giving them the tools they need to do the work of maintaining those guides and the pages within them.

We've added a 'Your Guides' section to the user profile which will list all of the guides that a user maintains, as well as the pages within those guides. This should allow maintainers to see when pages have been recently changed or added, and to easily keep their guide content curated and up to date.

Infrastructure Virtualization and Improved Config Management

In November, we completed the majority of two major infrastructure projects. Firstly, we've virtualized the majority of the infrastructure and standardized on Debian 8 images. Secondly we've updated our configuration and user management from Puppet 3 + LDAP to Puppet 4 + Hiera. This is a significant milestone for our infrastructure, and gives us a more portable and maintainable infrastructure to manage moving forwards.

Community Initiatives

Community initiatives are a collaboration; with dedicated community volunteers building improvements to Drupal.org with the architectural guidance and oversight of the Drupal Association engineering team.

Drupal 8 User Guide Launched!

We're very happy to say that the Drupal 8 User Guide is now live on Drupal.org! This documentation guide is carefully curated to provide all the information a new user needs to become skilled at managing a Drupal 8 site. We want to give a special thanks to jhodgdon for all her work on the User Guide project.

Initiatives need your help

Are you a Drupal.org power user who relies on Dreditor? Markcarver, who is currently leading the charge to port Dreditor features to Drupal.org, has invited anyone interested in contributing to join him in #dreditor on freenode IRC or the Dreditor GitHub.

Is the written word your domain? Consider putting your skills to use by becoming a maintainer of Drupal documentation. If you are a developer interested in contributing code to the new documentation system, please contact tvn.

———

As always, we’d like to say thanks to all the volunteers who work with us, and to the Drupal Association Supporters, who made it possible for us to work on these projects.

If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association.

Follow us on Twitter for regular updates: @drupal_org, @drupal_infra

Categories:

valechatech: Switching from file system configuration management to features on existing drupal site

Planet Drupal - Thu, 2016/12/08 - 6:15pm
Switching from file system configuration management to features on existing drupal site

In my last blog post, I outlined the best practices to manage the configuration management for the site. If you have read the previous post and wanted to follow the same on your site, this post will show you how to do Switching from file system configuration management to features on existing drupal site easily.

There's not any hard and fast way to change the configuration management for an existing Drupal site. Here are the steps in brief involved in to do the following:

  • Delete all of the old configuration except user roles and permissions
  • Export all configuration using features
  • Add update hooks to start using features

Delete all of the old configuration: Delete all the configuration which is present in your $config['sync'] directory except the user roles configuration.

Export all configuration using features: Export your configuration with features and make sure to leave the user roles and permissions and manage your user roles and permissions configuration via the Filesystem.

Add update hooks to start using features: Add update hooks to enable the new features.See the same hook_update_n below.

/** * Install features based config. */ function xyz_core_update_8017() { $features = [ 'xyz_f_alert', 'xyz_f_appointment_request', 'xyz_f_page', 'xyz_f_blog', 'xyz_f_career_area', 'xyz_f_careers_landing_page', 'xyz_f_common_formats', 'xyz_f_doctor', 'xyz_f_education_research', 'xyz_f_event', 'xyz_f_foundation', 'xyz_f_job', 'xyz_f_location', 'xyz_f_news', 'xyz_f_paragraphs', 'xyz_f_person', 'xyz_f_procedure', 'xyz_f_related', 'xyz_f_search', 'xyz_f_site', 'xyz_f_testimonial', 'xyz_f_user', ]; \Drupal::service('module_installer')->install(['features', 'config_update']); \Drupal::service('module_installer')->install(['xyz_bundle']); \Drupal::service('module_installer')->install($features); }

 

naveenvalecha Thu, 12/08/2016 - 22:45
Categories:

Acquia Developer Center Blog: The Future of Drupal 8 Development: Acquia Lightning

Planet Drupal - Thu, 2016/12/08 - 3:32pm

With Acquia Lightning, site-builders or developers can build an authoring experience from the ground up in only a few hours.

Think of Acquia Lightning as “Drupal Core with afterburners.”

Development tasks that used to take days or weeks are condensed to a matter of minutes.

Tags: acquia drupal planet
Categories:

Tim Millwood: Workflow Initiative Needs Review

Planet Drupal - Thu, 2016/12/08 - 11:49am
We have been extremely hard at work this year with the Workflow Initiative bringing some quite big...
Categories:

Amazee Labs: Diversity Matters

Planet Drupal - Thu, 2016/12/08 - 10:41am
Diversity Matters

This blog post was intended to be a recap of DrupalCamp Munich. It was a very well organized conference but the event was overshadowed by an intense discussion about diversity. This is why I want to focus this blog post on the learnings and takeaways from Munich regarding diversity at Drupal community events.

Josef Dabernig Thu, 12/08/2016 - 10:41

Setting the scene

On the day before DrupalCamp Munich, a discussion about diversity came up on Twitter and at the sprints venue where organizers were working hard on preparing for the conference. There were two related sources leading to the discussion. First of all, as Ekes pointed out via Twitter - out of 47 speakers there was only 1 woman on the agenda (2%). This is already saddening but the big attention came to happen when Twitter found out that copies of a men's lifestyle and entertainment magazine were about to be handed out to participants as part of the goodie bags.

The initial responses by the organization team were defensive rather than acknowledging the problem, basically stating that the event team can’t fix the problem of there not being enough female speakers at the conference. After a while penyaskito cancelled his session: he wouldn’t because of the two issues but mainly the lack of action and communication around them. By the end of the day, the DrupalCamp team published an official statement of apology.

I cancelled my session at #dcmuc16. Hoping you learnt from to community's feedback for next events. Thanks @Lingotek for supporting me pic.twitter.com/IwXGkADTIE

— penyaskito (@penyaskito) December 2, 2016

Thinking about the facts

I’m glad to see that the issues have been taken seriously. Obviously there was a different perception of the severity of the problem. From my personal experience, bringing in diversity into tech events is a challenge, especially when they are organized by teams that aren’t diverse in the first place.

But if we look at the data, we can see that DrupalCon New Orleans (19% female and 81% male), DrupalCon Dublin: (17% female, 82% male) had quite similar ratios. Even though they still have a long way to go to improve this, they’re better than what we accomplished for DrupalCamp Vienna (13.6% female and 86.4% male). With DrupalCamp Munich only achieving 2% female speakers, I think this is a very alarming sign that we have to react upon and therefore support the call for action very much.

Everything back to normal?

The discussions were quite heated, especially on Twitter. Special thanks to Jeffrey “jam” McGuire for following up with a blog post on “Empathy, diversity, and open source”. Aside from agreeing on the problem, Jam acknowledged the hard work and best intentions of the local team to host a good conference. I think it is important to see & hear both sides of the conversation and from there continue the discussion.

And this happened through lots of talks - both online and onsite at the camp. On Saturday evening, we had a big “Diversity Matters” BoF. 7 women and 48 men discussed the issues with live notes taken.

Some of the important takeaways from the discussion for me where:

  • Diversity needs to be looked at on all levels.
  • Providing safe spaces is needed to support minorities in joining a community.
  • A code of conduct is a good foundation but needs to be lived.
  • We need to listen to the views of others before defending our own viewpoints.

Where can I get more help with this?

We are not alone in this. To figure out how to get better diversity at Drupal events in Europe, we can look at role models and the support they provide by leading by example.

JSConf for example, has documented how they reached 25% women speakers already in 2012. Their call for speakers highlights how they offer support to attendees to become confident about their wish to speak. They also embrace an anonymous submission process. If you want to find out more, you can check out “We Are All Awesome” for some great materials for both speakers and curators.

In Drupal, Ashe Dryden’s session from DrupalCon Portland provides a good overview of why diversity matters. If you want to help or join the discussion: Drupal Diversity is a working group discussing diversity & inclusion in Drupal and web development. They have extensive resources on why we should care and what we can do to improve diversity. On the Drupal slack, find us in the #diversity-inclusion channel with more than 100 members already. Also the Drupal Community Working Group is working on a response to the happenings. You can also follow them via Twitter.

What did I learn?

Since I joined the Drupal community, diversity has been important to me. One of the reasons why I joined Amazee was that I was looking for a more diverse team to work with. Working with a diverse team is still a privilege in our industry and I would like to see a bigger movement towards getting better diversity across the whole industry.

The recent incidents have made it clear to me that this needs to go further though. It’s not enough to simply say “we want more diversity”. We need to look at diversity as a common goal and everyone of us need to make more effort in order to achieve it.

The DrupalCon Baltimore call for sessions just started and shows a clear effort to inclusivity. Optionally, speakers can identify with underrepresented communities to help the session selection team ensure better diversity in the program. Also read their blog post about setting diversity as a DrupalCon goal.

As part of the Drupal Mountain Camp team, this discussion has inspired us to focus more on diversity. We agreed to think about it on all levels:

  • Promote diversity and the code of conduct on all levels of the event.
  • Set and communicate diversity as a goal for the session selection process.
  • Actively encourage diverse speakers to attend.
  • Offer support to speakers via coaching & mentoring.
  • Provide a safe and healthy environment for all attendees.
  • Educate ourselves as event organizers by reading materials stated above.

I’m looking forward to strive towards this goal for more diversity in Drupal.

Categories:

Agiledrop.com Blog: AGILEDROP: Other Top Drupal Blogs from November

Planet Drupal - Thu, 2016/12/08 - 7:41am
We recently decided that at the beginning of every month we will look at the topics we covered in our blog posts in the previous month. So, we began last week with our first overview. But we were not satisfied only with that. Therefore, we decided to also look around and gather for you the best Drupal blogs that other authors have written over the past month. Here's our first selection, which includes blogs, which were written in November. We'll start with the most obvious one. It's the one from the founder Dries Buytaert, who dedicated his post to the first anniversary of Drupal 8. He… READ MORE
Categories:

ARREA-Systems: D8 autocomplete search items in custom module

Planet Drupal - Thu, 2016/12/08 - 3:37am
D8 autocomplete search items in custom module JK Thu, 12/08/2016 - 10:37 This script will help display the results of a search by keyword instantly via an ajax call in a custom module. It can be applied to various search types. From user point of view it creates a good user experience and efficient working flow.
Categories:

Drupal Association News: DrupalCon Sprint Adjustments

Planet Drupal - Wed, 2016/12/07 - 9:50pm

As Drupal, the Project, keeps growing and changing, so does DrupalCon. As the Events Team at the Drupal Association, we are continually working to improve the event - to strengthen the programming and to better fit the needs of attendees. Over the past year, we've heard through both formal and informal conversations that DrupalCon sprints are ready for a change.


A consistent topic in those conversations was that Extended Sprints, held on weekends before and after DrupalCon, may be too much. While 9 days of sprinting at previous DrupalCons evolved informally, they were a key part of the hard push that got Drupal 8 out the door. Concerns were raised that it is not healthy for contributors to continue at this pace. Contributors said that they were a little burnt out and didn't need as many days of sprinting.


A few weeks ago, we met with some of the sprint leads to discuss DrupalCon sprints to really hear what the Project needs at this point in its life-cycle. What we heard was: "Shorter sprints, with greater support." Based on this conversation with sprint leads, informal conversations from community members, and some feedback from the attendee survey, DrupalCon staff will no longer be organizing weekend Extended Sprints at DrupalCon going forward.


We will continue to support full day sprints from Monday through Friday. There is a dedicated sprint room throughout the week at the convention center, open Monday through Friday, as well as a designated location at the host hotel for 24 hour sprinting sessions. Sprint mentors are available at the DA sponsored mentor table in the exhibit hall throughout the conference to answer any questions about the contribution process, help new contributors pick which sprint best fits them, encourage new mentors to join Friday, and help both new contributors and new mentors know what to do to prepare for the sprints on Friday. We will concentrate our support on providing sufficient quality sprint space, and lunch and coffee, sprint room signage, supplies, special t-shirts for mentors, etc. - things that will help everyone have a quality productive sprint experience.


With these changes, our main objectives for DrupalCon sprints are to support current contributors, bring in new contributors, and nurture those who've dabbled, but not fully jumped in. We believe this is an imperative for the health of Drupal.


If you've attended a sprint at DrupalCon in the past, we certainly hope you will join us again in Baltimore. Our full conference website launched this week - be sure to check out the call for papers, buy a ticket, or apply for a scholarship.

Personal blog tags: drupalcon
Categories: