Drupal Planet

Search is a technique used to find the position of any element or value in the list. The search is successful or unsuccessful depends on whether the term or element being searched is found or not.

A search engine is a tool that enables users to find information on the World Wide Web. A search engine intends to get the requested information from the vast database available on the internet.

Every web application, by default, will contain a search feature in it. Search facilities are implemented in each website differently based on the requirement and nature of the application.

The Drupal Search Module helps the user search for specific content on the site. Search can be performed for both users and particular words. Under ‘Content,’ users will be able to search for words that are present in the default rendering of node content on the site, which would include the default display of any CCK (Content Construction Kit: it's a module that allows users to create new content types and extend existing content types). It also allows users to add/modify/remove fields from these content types where these fields may be text, numbers, dates, images, computed values, references to other content, taxonomies, the location fields, etc., as well as comments. Navigating to the “users” tab of Search, we can see the registered users' names on the site and their permissions and email addresses. 

On a local project with the business directory site Ecoparker, we experienced the struggle of displaying a long list of products in small display screens ie mobiles.

On this particular landing page, showcasing Solforest a vertical forest real estate project, we need to present 10 types of apartments in two categories with sizes and selling prices.

read more

When every tutorial for syntax highlighting in Gatsby talks about highlight.js markdown but you have a Drupal website, you need to write your own for posterity. Here's mine.

As we look forward to the vaccine-influenced future beyond COVID-19, one of the very few things we have lived over the past 9 months that may actually have a positive lasting impact on society is that often there are advantages to accomplishing things virtually. Working remotely, meeting via Zoom, online appointments, grocery delivery, even doctor visits have screamed past proof-of-concept for situations most of the world had previously not considered. 

So many more applications that rely on the web are more ingrained in daily life since COVID forced them on us. With this incremental leap in mass adoption of web technologies, web development (and for the purpose of this article, Drupal) will continue to play a major role as the world leverages online tools more, and for more applications. This suggests that Drupal positions (which total more than 1,600 listed on Indeed the first week of December this year), may open up even more in the future.

So, for those who conceive, create, and maintain current and future tools, or people considering these careers, the future looks pretty bright. Those of us in the community know that even beyond the new growth potential, Drupal and web development has a lot to offer; so, we humbly share these 5 great reasons you may want to consider 2021 as a good time to get serious about your Drupal dexterity if you want to expand your skills, get up to speed or even pivot your career to seize the day and opportunity: 

1. Web Development Careers have a lot of opportunity! 

 It’s hard to find an article about promising careers without web developer positions seated in the upper tiers. According to recent article by CNBC, Web Developer careers are in the Top 15 High Demand jobs over the next 5 years. Indeed puts it at #10 for careers most in demand right now; and the US Department of Labor Occupational Outlook Handbook estimates that 2019’s total 174,300 web developer positions will grow by about 14,000 over the next 10 years, a higher rate than most vocations. 

2. The Path to becoming a Drupal Web Developer is accessible. 

If you have the desire and commitment to become a Drupal professional, you can! Drupal training is available through go your own pace options like Drupalize.me, with focused training sessions live and online (Evolving Web, Mediacurrent) and of course, might we suggest the longest running, long-form career technical education program through DrupalEasy Academy; Drupal Career Online. There is also plenty of advice out there like DrupalEasy Career Resources and How to start a Web development career.

3. Flexible schedules and virtual work are prevalent in the Web Developer World

Life in 2020 changed work for a lot of people, but remote working is nothing new in the world of web developers. Drupalists, both those employed by organizations and those who choose to freelance, have a long and successful history of working from home, or wherever they find great wifi and interesting surroundings, there are state of the art tools that support teams who are spread out specifically catering to this efficient, low-overhead way of doing business. Add “virtual” to your job search on Indeed or Career builder, and you can see hundreds of positions. 

4. Salary Data for Web Developers compares pretty well

According to the U.S. Department of Labor Bureau of Labor Statistics, The median annual wage in May, 2019 for web developers was $73,760. It gets better if you choose Drupal, as Indeed reports that, based on 188 salaries reported as of November, 2020, the average salary for a drupal developer is $95,642 per year in the United States.  You will have to get some experience and hone your skills, but with commitment and patience, the high-wage jobs are yours to strive for. 

5. Drupal Web Developers have a global community for support

Come for the code, stay for the community.  It’s not just a mantra.  The Drupal community has groups connected by topic, interests, service to the community and even outside interests.  There is nothing like it.  Even here at DrupalEasy, we have a micro community of past and current students that meet up every week to help each other work through projects, issues and provide support.  It’s our DrupalEasy Learning Community, and we like to think it’s a microcosm of the Greater, Global Drupal Community that makes our content management system, and the people who support it so outstanding. 

The next session of Drupal Career Online starts March 1, 2021, with the application deadline the last week in February. If you are interested in learning Drupal, honing your Drupal skills specifically in our longform Drupal Career Online, let us know, or sign up for one of our no-cost Taste of Drupal mini webinars coming up in the beginning of 2021.  

Even if you are not a technical person and do not have coding knowledge, you should use structured data on your Drupal website.

Even though the words schema markup, structured data, and structured data markup sound like spells from Harry Potter, you should befriend them and add the necessary structured data to your Drupal 8.

In today's blog, Wishdesk web development agency will explain in detail for all Drupal site owners, or those who are planning to create a site, the answers to these questions:

Though WordPress's easy setup has made quite a name, the Open Source CMS is still far from perfect. There are instances where pen Source users prefer Drupal as their CMS of choice for the advantages it offers. 

For those who are new to the world of CMSs, WordPress is often the natural choice as it is easy to get started with. For those who would like to level up and need more customized functionality from their websites, Drupal meets these needs well. 

While these advantages take over Drupal, there are a few that both the platforms share equally. For example, both Drupal and WordPress offer eCommerce capabilities and are redesigned to be more platform-agnostic. Similarly, you can decouple Drupal as well as WordPress. The drupal site can act as a content API server on the first day itself, while REST API is now bundled in the WordPress core for developers to experiment and use it in a decoupled way.

If you are a small business, WordPress might be the solution for you, but Drupal offers significant advantages for large enterprises. In case you are one of the latter, the next section will guide you through the migration process. 

How often does one quick fix to a problem stay as only one? More often than not, a domino effect takes place and the flood gates open. Suddenly, you’re stuck in a never-ending cycle of applying band-aids to a problem that has no quit. Enter strategy. Where instead of being in a constant state of panic, you’re in the most powerful position to navigate a pandemic you didn’t see coming.

Whether you're in the middle of a Drupal upgrade or you're thinking about starting an upgrade next year, we've pulled together 19 resources—largely written by members of the Evolving Web team!—to help you succeed.

When upgrading from Drupal 7 or 8, the fact is that the content migration will probably go smoothly, but you may your customizations will require more work. If you find that you're halfway through what seemed an easy upgrade and suddenly you're having a hard time, don't worry. That's what these guides are for. :) 

Pro tip: Since Drupal 9 is more of a continuation of Drupal 8 than a completely new version, the vast majority of information you’ll come across about migrating to Drupal 8 still applies to Drupal 9, too.

Most Drupal sites are still running on Drupal 7, but that’s starting to change. With the release of Drupal 9.0 and 9.1 earlier this year—and the announcement that Drupal 10 is planned for 2022—one of the most common questions we’ve been hearing from the community is “Do I need to upgrade from Drupal 7 to 8 before moving on to Drupal 9?”.

The answer, in most cases, is no. Since Drupal 9.0 is more a continuation of Drupal 8 than as a whole new beast, it's usually not needed.

So what is needed? 3 simple steps:

• A plan
• The actual migration
• Optimization and tweaks

Measure once, cut twice. When it comes to something as critical as your website, never skip the planning stage.

As Drupal.org puts it,

While the content of your previous Drupal site can most probably be migrated without issues, the configuration of your Drupal 8 site will most probably need some manual tasks. For example, Views module doesn’t have an automatic upgrade path in core at the moment which means you will need to manually create the views on your Drupal 8 site. The most suitable approach needs to be considered for each site. (source)

If any of this is news to you, we recommend reading through Drupal.org’s guide to choosing an upgrade approach before you dive in.

Once you have a high-level idea of how you’ll approach your migration, read Things to know before moving from Drupal 6 or 7 to Drupal 8.

This post covers how to prep your site for a successful migration: what needs to be refactored or rewritten, what risks might get introduced by legacy contrib modules, and how to take advantage of the pre-migration stage to work on your site’s fundamentals.

Another good page for your bookmarks is How to prepare your Drupal 7 or 8 site for Drupal 9 from Drupal.org. It contains a list of available deprecation checking tools and offers guidance on how to get ready to use Twig 2 with Drupal 9, among other handy advice. 

These articles have all been reviewed in late 2020 for accuracy and feature practical code snippets to kickstart your project setup.

The specifics of the data migration will vary based on the data types that you're using in your Drupal install and how much custom work you've put into your site. That said, these guides are all based on scores or hundreds of hours that our core team has put into migrating sites, so they should help you work through the process.

• Drupal 8 Migration: Migrating Basic Data (Part 1)
• Drupal 8 Migration: Migrating Taxonomy Term References (Part 2)
• Drupal 8 Migration: Migrating Files / Images (Part 3)
• Migrating Aliases and Redirects to Drupal 8
• Migrating hierarchical taxonomy terms
• Migrating media items and their relationships

As Drupal 8 and 9 offer a standardized way of managing translations, many sites running multilingual Drupal 7 are making the switch to a later version and discovering that they should change how they're managing translated content. In Drupal 7 there are two ways to translate content:

1. Using the content_translation module. The D7 core way of translating content, where every translation is a separate node.
2. Using the entity_translation module. Maintains one node with a unique nid, while translations take place at the field level.

We put together step-by-step instructions for migrating content that was translated according to each of the above scenarios:

• Migrating Content Translated with "Content Translation" from Drupal 7 to Drupal 8 or 9
• Migrating Content Translated with "Entity Translation" from Drupal 7 to Drupal 8 or 9

➡️ If you’re migrating translated content to Drupal 8 or Drupal 9 from a non-Drupal source, read: Migrate Translations from CSV, JSON or XML to Drupal 8. 

If your migration project requires a more bespoke solution, check out these advanced guides written by Evolving Web developers. Note that you likely don't need to worry about many of the steps covered here unless your site has a lot of customization in how you're using Drupal. That said, if you've read the above guides and don't see an answer to questions that you have, read these next. 

• Profiling and Optimizing Drupal Migrations with Blackfire
• Writing a Custom Migration Source Plugin in Drupal 8

Another good resource is the Drupal.org page Customize migrations when upgrading to Drupal 8.

Evolving Web has a Drupal training program that’s designed to help developers and site managers quickly build valuable Drupal skills. Our role-based learning tracks include Drupal Site Builder, Front-end Developer, Content Creator, and more.

If you’re stuck on a project and looking for a fun, straightforward way to grow your skillset, take a look at our course catalogue.

The Open API specification is a widely adopted industry standard used to describe RESTful APIs. Originally referred to as the Swagger Framework,  OpenAPI can be considered a RESTful API description language. It is used to provide a structured description of the API for humans as well as automated processing.  Using the OpenAPI specification helps developers save time by automatic generation of documentation and validation of the endpoints. OpenAPI supports both JSON and XML. 

Axlerant was entrusted with the task of developing a Drupal 8 based partial headless backend for a global NGO. The backend would be integrated with a React application, which would act as the Frontend of the system. 

This meant that Axelerant and the Frontend developers had to come to a mutually acceptable format for the REST-based API endpoints in the backend. After careful consideration, the OpenAPI 3.0 specification was selected as the format for describing the APIs.  

In Drupal 8 the menu system, in comparison to Drupal 7 has become much more flexible, and the areas of functionality are now separated into different systems. 

While we were working on one of our client's projects, we came across a requirement where we had to have an admin for every country and allow them to add and edit the details. 

We decided to have the Country as a Vocabulary and the Countries as the terms in the vocabulary. The details of the Country are made available through fields in the vocabulary. Having done that, now we have every Country mapped to every Country admin. The term edit page should be made available to them as a menu link so that it’s easier to edit the details of the respective Country, as shown in the below screenshot.

This is one of the ways in which the menu-link could be altered dynamically. Other preferred methods could be to opt for hooks, commonly used  hook_menu_links_discovered_alter() for statically defined menu-links, hook_link_alter to alter the parameters for links. Here is the list of hooks the Menu API had to offer.

Conversions – the most sought-after goal for businesses and their websites. Marketers work tirelessly to drive traffic to their website, but the most challenging part of their job is to enable conversions. If you have an average conversion rate of 2.35%, you’re doing pretty well. 

I’d most likely click a button that says “BUY NOW!” rather than just an “Add to Bag” button. I might have my own reasons for doing so but the latter just lost a customer because of a single harmless button! That’s the effect of user experience today. To identify what user experience works out for your website, we have A/B testing to the rescue. In this article, we will discuss more about why A/B is testing important and some of the top Drupal 8 and 9 modules for implementing A/B testing.

The benefits of A/B testing are invaluable. The fact that you know what marketing strategy works for your business and backed with proper evidence is awesome enough. By making a few small changes on your landing pages using the data received by conducting A B testing, you can gain a much higher conversion rate. On running A B split testing on your Drupal website, you will be able to:
 

• Determine the best marketing strategies for your product and business
• Lower your risks by testing customer actions
• Identify what business promotions are working out for you
• Provide your visitors with an effective user experience
• Reduce your bounce rates
• Increase your sales and conversion rate
• Run a super successful website

A/B testing can be performed on all elements of your website like the headers, paragraphs, CTA buttons, CTA text, Images, Links etc.

Our very own, most beloved Google was the first to implement A/B testing to find out exactly how many search results should they be displaying on a page. Although unsuccessful on their first shot due to sluggish load time, they victoriously ran more than 7000 A/B tests after 2011. (source:Wiki)
Let’s look at some of the top Drupal 8 and 9 modules for A/B testing your Drupal website.

The Drupal Google Optimize module integrates your Drupal site with the Google Optimize tool. It is compatible with Drupal 8 and Drupal 9. Google Optimize is an A/B testing tool that lets you create personalized experiences and run A/B tests. It integrates with the Google Analytics of your website. So, you will need the Drupal Google Analytics module installed for this module to work.

First, you will need to create a free account at Google Optimize here and create a container(s) for your experiment. Once done, you can customize your settings in the module.

You can also use the Drupal Google Optimize Hide Page module that lets you add a JavaScript code snippet to hide the pages until the Optimize container is fully loaded and the experiment is ready.
 

With this Drupal module for A/B testing, you can test various versions of your web page. You will need to create the different versions and set different internal URLs. These URLs will be rotated on a single base URL. Users will be redirected to either the base URL or the variations depending on the test cases defined.

Use Google Analytics to identify which version worked better for you in terms of session duration, bounce rate, etc. This Drupal module supports both Drupal 8 and Drupal 9.

The Drupal Optimizely Module lets you integrate your website with Optimizely by adding the tracking code in the head of your webpage. Optimizely is an A/B testing tool that can modify the HTML and CSS of your website to perform tests on various elements of your Drupal website. It then provides you with results that will let you know which element worked out the best for your website.

This simple module integrates your Drupal website with the Crazy Egg heatmap service and performs A/B testing or split testing on various elements to test multiple versions of a page. It also lets you see and track user’s mouse patterns and scrolling patterns. 

You will first need to create an account at CrazyEgg , install the Drupal integration module for Crazyegg and configure the module. You will need to enter your Crazy egg account number and save the configuration. The module is also supported in Drupal 9!

This Drupal module lets you perform A/B and multivariate tests by inserting JavaScript code snippets into your Drupal web page. The UI and testing functionality are directly integrated into Drupal and not an external script. For evaluating your test results however, you will need an analytics platform like Google analytics, since it doesn’t have a built-in functionality to do so.

Install the A/B Test JS Drupal module and configure it as per your requirements. You can then add your conditions and experiences to test.

There really is no right or wrong when it comes to user experience. The only way to find out if we’re heading in the right direction is to test and find out. A/B testing lets you lower the risks in taking big decisions for your marketing strategies by giving you solid proof to support it. Specbee is a Drupal Development Company and we offer you unparalleled solutions that will help your business to find the right direction and maximise your revenues.

Leave us a Comment

Know more about our technology driven approach to recreate the content management workflow for [24]7.ai

Find out how we transformed the digital image of world’s largest healthcare provider, an attribute that defined their global presence in the medical world.

Discover how a Drupal powered internal portal encouraged the sellers at Flipkart to obtain the latest insights with respect to a particular domain.

VIEW ALL CASE STUDIES

On November 18th, 2020, the Drupal security team released security advisory SA-CORE-2020-012, a critical remote code execution vulnerability being patched in Drupal 7, 8, and 9. If you haven't read up on this issue, or the contrib advisories from the same day, I suggest you pause here and go take a look (and of course update your site(s)).

As always, the Drupal Security Team demonstrated their commitment and professionalism in helping all of us keep our Drupal sites more secure. But this post is not just to praise the security team, but also to report back on our first trial activation of the Drupal Steward program with a real security vulnerability.

As a reminder, the Drupal Steward program is operated jointly by the Drupal Association and the Drupal Security team, to offer protection for highly critical and mass exploitable vulnerabilities in the form of a web application firewall. This protection is offered directly by the Drupal Association to end-users, and also through our Founding Platform Partners: Acquia and Pantheon.

Drupal Steward doesn't change the site owner's responsibility to update their site. It does, however, provide a greater safety window and more flexibility for their team when scheduling the update.

In coordination with the Drupal Security Team, as well as our partners, we decided to use SA-CORE-2020-012 as our first live case for implementing this protection. This core issue was neither 'highly-critical' nor 'mass-exploitable' as the program is generally designed to protect, but because it was still a critical issue, it made a good test case.

We made a deliberate choice not to pre-advertise the protection for this first activation, because we wanted to thoroughly vet the process from end-to-end, before telling Steward customers to breathe easy when scheduling their update.

For future activations we will include a section in the PSA or SA published on Drupal.org, marked by the Drupal Steward logo, which indicates whether an upcoming security release will have this Drupal Steward coverage - giving all Drupal Steward customers the warning they need so they can responsibly schedule their site updates.

We're very pleased to say that this first program activation went very smoothly. Our coordination with Founding Partners, and our implementation of the firewall rules for the community tier went quickly and easily - and despite the short turn-around time, we were able to have protection coordinated in time for the disclosure of the issue.

If you follow Drupal security issues closely, you'll know that another Drupal security release occurred only about a week later. SA-CORE-2020-013 was released to mitigate a vulnerability in a third-party dependency of Drupal. This issue was not eligible for Drupal Steward coverage because it was a zero-day, that is, the vulnerability was already public and so there was no time to implement a preventative mitigation strategy.

You can learn more about Drupal Steward here and you can ask questions or set up a consultation here. Cost is usage0based, and we've tried to subsidize the cost as much as possible for our community site owners. For most small to medium-sized sites, coverage costs less than $200/year. Proceeds are allocated to support Drupal Association and Drupal Security Team programs. 

As part of the Drupal Associations ongoing mission to foster contribution in the Drupal project, we’re bringing you an experimental first edition of a new blog series - with a quarterly update on initiatives across the Drupal ecosystem, as well as calls to action highlighting where contributors are most needed. We’ve heard from many people in the Drupal community that it can still be difficult to understand the major priorities of the Drupal community, the state of current initiatives, and how to get involved. 

We hope that posts like this one provide a broad overview of current priorities in Drupal, and connect the dots to the individual mentors, initiative leads, and other community organizers who can help you get involved. 

We plan to do an update each quarter. We thank the Wordpress community for their example of a concise initiative update. Based on your feedback on this first edition, this format may evolve. 

If we missed reaching out to you, but you’d like to provide an update on an initiative you are involved in, please feel free to submit your update to this form. 

In this release, we have reports from the following initiatives and community groups.This is not a comprehensive list of all initiatives and community groups, just those who were able to provide an update in time for this post:

• Active Drupal Core Initiatives
  • Mike Herchel updates us about Olivero - the new front-end theme
  • Jess updates us about Drupal 10 Readiness
  • Tim Lehnen provides the latest info about Automatic Updates
  • The Decoupled Menus Initiative is getting organized
• Additional Core Initiatives, Community Initiatives, and Community Group Updates
  • Jennifer Hodgdon updates us about Documentation and Help
  • Elli Ludwigson updates us about Contribution Mentoring
  • Tim Lehnen reports back from the Contribution Recognition Committee
  • Kaleem Clarkson updates us about Event Organizers Working Group
  • Andrii Podanenko and Alla Petrovska update us about Drupal Virtual Cafe Ukraine and the Drupal Ukraine Community
  • Jess Snyder updates us about Nonprofits
  • Nico Grienauer updates us about Drupical
  • Chris Teitzel updates us about Privacy
  • Tara King updates us about Drupal Diversity & Inclusion
  • Alex Moreno-Lopez updates us about Drupal Swag Shop working group
  • Rain Breaw Michaels updates us about Accessibility
  • Kay VanValkenburgh updates us about DrupalLadder
  • Drupal participation in Google Summer of Code
  • George DeMet updates us about the Drupal Community Working Group
• We want your feedback!

https://www.drupal.org/about/strategic-initiatives/olivero

Getting into core! We’re finally in 9.1 as a beta experimental theme. Check it out!

Getting it into core was a mad dash at the very end, but we pulled it off thanks to a lot of help from Drupal’s core contributors. Those folks are amazing! 

Getting into a beta status for core

Use it. Find and file bugs!

https://www.drupal.org/project/drupal/issues/3118143

1. Ensuring that Drupal core is internally compatible with Symfony 5.0 and 5.1 (without using deprecated APIs), so that we can easily release Drupal 10 with a dependency on Symfony 6. (Done!) 
2. Ensuring Drupal core and its upstream dependencies are fully compatible with PHP 8 as soon as possible so that Drupal 10 can set its minimum dependencies accordingly. (Done!) 
3. Initial discovery on CKEditor 5 integration for Drupal 10 (Ongoing, challenging) 
4. Replacing remaining forked jQuery UI code with modern alternatives (Ongoing) 
5. Reducing jQuery use for an easier upgrade to future versions

We have lots of JavaScript work needed, both for integrating CKEditor 5 and for reducing legacy jQuery and jQuery UI use, and few working on it these difficult problems.

Really great collaboration and problem-solving for upstream blockers to PHP 8 compatibility, and all compatibility issues with Symfony 5 are resolved, We’re now working on Symfony 6 compatibility (that is, addressing deprecations introduced in Symfony 5.1 and 5.2), which is the real goal for us for Drupal 10’s release.

Frontend contributors! We love you and we need your help!

We need help with several big changes related to core’s JavaScript: 

• https://www.drupal.org/project/drupal/issues/2966864 
• https://www.drupal.org/project/drupal/issues/3067261 
• https://www.drupal.org/project/drupal/issues/3052002 

Furthermore, we need help from theme developers and contributors to join a new initiative to build a Starterkit Theme for Drupal core. https://www.drupal.org/project/drupal/issues/3050384 This theme starterkit will replace Classy as the best way to start building a theme for a Drupal site.

The best place to stay up to date is in the Automatic Updates issue queue, or by joining us in the #Auto-Updates channel in Drupal Slack.

Current Priority: Finishing our implementation of the php-tuf client and server code, so that we can move from our secure signing implementation into our actual updater code. 

Previous Priority: Over the course of the last quarter the Drupal Association hosted three contribution weeks, with Drupal initiative contributors as well as representatives from Joomla and Typo3. We used these contribution sessions to scaffold out the php-tuf library, and to align our architectural decisions in ways that will work across the php ecosystem. 

Our update process must run the appropriate Composer updates as well, so we are currently attempting to architect a solution to account for the fact that Packagist itself does not yet have a signing solution for third party libraries. 

The Drupal Automatic Updates initiative has joined forces with both the Typo3 and Joomla communities, to share certain foundational components, like our secure signing schema. And speaking of secure signing, we are working closely with the Cloud Native Computing Foudnation’s TUF initiative for a robust and standards based signing solution. 

If you’re interested in the problem-space of securely signing software, consider contributing to the php-tuf project. If you’re more interested in understanding the update process itself, please join us in the Drupal Slack channel! 

The Decoupled Menus Initiative is in the process of organizing the official initiative team. Regular meetings are happening in the #decoupled-menus-initiative in Drupal Slack.

The main priority for the initiative has been gathering the initial group of contributors and getting organized. There is a clear path for understanding what a javascript menu component looks like, but there are much more challenging questions to be resolved about how to integrate non-php components into the Drupal core process. 

This initiative is in the first stages of getting organized and up to speed. In addition, understanding how to work on non-php for Drupal core is a major challenge. 

Just launching this initiative as an official goal is greatly important. There has been very active conversation between initiative team members, core maintainers, and the drupal association as the organization kicks off. 

If you are an expert in using a javascript front-end for a Decoupled Drupal solution, if you are familiar with open source contribution in the javascript ecosystem, or if you are a competent project manager your insight would be valuable. Please join the initiative’s slack channel and regular meetings.

User Guide: https://www.drupal.org/project/user_guide; Contributor Guide: https://www.drupal.org/community/about/getting-involved-guide-becoming-contributor-guide; Help Topics: https://www.drupal.org/project/drupal/issues/3027054

User guide: minor updates and supporting groups making translations. There has been a lot of progress lately on German and French! Help topics: mostly writing new topics, and some progress on other Roadmap issues. 

Contributor Guide: Migrating content from the old Getting Involved Guide.

Getting other contributors to review and commit patches, and to provide feedback on plans.

Migrating most of the content in the Getting Involved Guide to make several new and better-organized areas, such as the Issues documentation at https://www.drupal.org/docs/develop/issues and the Git documentation at https://www.drupal.org/docs/develop/git

You can help with curating and migrating older documentation into the newer documentation content types, or into the new Contributor Guide. Join the #documentation channel in Drupal Slack and another contributor can help you find a place to get involved. 

https://www.drupal.org/community/mentoring

Getting ready for DrupalCon Europe, updating documentation and materials

Engagement. It’s been difficult to demonstrate value and a clear path to success for contributors and mentors. Also everyone seems a little low on energy lately and we could use more fresh folks coming into leadership roles.

Updating the contributor guide! http://drupal.org/community/contributor-guide

Jennifer Hodgdon and others have reorganized and made everything much more logical. AmyJune continues to do an amazing amount of work at many many virtual events, giving contributors a place to get started with Drupal.
Prior to the last three months Rachel Lawson did a lot to rethink the contribution and mentoring process with the portal we used at DrupalCon Global. Matthew Radcliffe and Gábor Hojtsy did a lot of work on that as well. And Randy Fay is often on hand to help with any and all local development environments and general Drupal troubleshooting.

Without creating any new projects, I’d say we could use an enthusiastic and experienced person to help clean up old issues and polish the documentation work. We could also use more mentors on hand in general for virtual events across various time zones, especially outside the Americas. 

The history and current membership of the Contribution Recognition Committee is summarized on Drupal.org. You can also reach out to contact the committee at [email protected]

The major priority for the CRC has been to engage with the Drupal community at large, and gather feedback from all stakeholders about how contribution to Drupal should be recognized, recorded, and rewarded. 

The committee’s primary deliverable is to present a set of recommendations to the Drupal Association for the next generation of the contribution credit system. 

Internal scheduling challenges due to COVID disruption have been the largest barrier to progress for the committee in recent months. Like many other volunteer committees, the CRC has had significant disruptions in the personal and professional space. However, the committee is making progress, and is nearly ready to present initial recommendations. 

The committees’ largest accomplishment has been a very robust round of stakeholder conversations with people throughout the community - so that we have a fair and broad spread of perspectives informing our work. 

We’d love to hear from you if you have thoughts or ideas about the contribution credit system. You can contact the committee at [email protected]

https://www.drupal.org/community/event-organizers

Over the last three months we have mostly focused on finalizing what initiatives we should start with in 2021. 

Our greatest challenge has been attracting more global representation at our monthly community meetings. At the beginning of this year, our group made an intentional effort in attracting more global participation. Through our efforts, we were able to recruit two new board members representing India and Ukraine. Another strategy was to change our meeting times to UTC format and alternate between 12pm and 12 am UTC. We are hoping that in 2021 we can increase the number of global camps represented in our open meetings. 

I think our biggest accomplishment has been confirming our four major initiatives that our group will focus on in 2021. These initiatives will be:

• Onboarding At DrupalCon Community at Events, 
• Event Organizers Website Starter Kit
• Marketing the Events Organizer Group
• Events Database Website on Drupal.org. 

Each initiative will have committees made up of one Event Organizer’s Working Group board member and volunteers from the Drupal community. For so many reasons, we are all looking forward to working in concert with event organizer volunteers from around the world.

We need all Drupal event volunteers to help spread the word about the Drupal Events Working Group. 

We will be looking for volunteers to serve on the committees of each of our four major initiatives and we can’t do it without you. 

https://www.facebook.com/groups/drupal.ua

https://www.facebook.com/drupalcampkyiv-

https://drupalcampkyiv.org/

Supporting the Ukraine Drupal community during the pandemic

Finding the available speakers for Drupal Virtual Cafes

We have organized three Drupal Virtual Cafes.3 online events, 2 speakers per each event, 60+attendees at each event from Europe and North America 

To connect the Ukraine Drupal Community and everyone interested abroad with the speakers by organizing the Drupal Virtual Cafe monthly. We have the capacity to organize, the issue is to find available speakers. 

We need to have more information about bottlenecks for organizing virtual DrupalCamps. We have planned DrupalCamp Kyiv 2021, but unsure about the details.

https://www.drupal.org/community/nonprofit-drupal

Our top priority continues to be to provide a welcoming place for nonprofit Drupalists to get advice, share knowledge, and discuss the issues we’re all facing in this challenging time.

Aside from dealing with the curveballs the past several months have thrown at all of us, nonprofits continue to struggle with the changes in Drupal requirements that have increased the expertise and costs required to build and maintain Drupal sites.

Aside from seeing new faces on our monthly calls, which we’re always thrilled about, we’re also proud of how our community is encouraging nonprofit orgs to try new features, like Layout Builder, while also discussing the challenges that come with trying new features that are still in flux.

Come and join our monthly call! Held on the third Thursday of the month at 1pm ET/10am PT, it’s free of charge, beginner-friendly, and open to anybody working for or with nonprofits and Drupal. 

Call-in info can be found on our community page (https://www.drupal.org/community/nonprofit-drupal) or in our collaborative notes document (https://nten.org/drupal/notes).

Getting the new drupical 2.0 ready for launch

Finding time beside the global covid problems 

• Getting finally access to drupal.org/community/events
• Finalising the first version of the new drupical fronten now in vue.
• Getting work done on the new drupal 8/9 drupical backend – found a possible solution, to also display online events on a map :)
• Getting a link from the drupal main menu to drupical. 

Hopefully it will all be released in time for DrupalCon Europe!

stay healthy, stay at home and see you at one of the next virtual Drupal events!

https://www.drupal.org/project/ideas/issues/3009356

We are continuing to work with the community and project stakeholders to come to a plan for a privacy initiative and/or team that can be involved in core conversations to ensure privacy is taken into account with core features and initiatives. 

Funding of the initiative is the next hurdle to jump after receiving confirmation from Dries that he still desires it to be an initiative.

Receiving confirmation from Dries that he still desires it to be an initiative!

Continued support and talking to maintainers about the need for a formal privacy team/initiative within the community. Sponsorships as well, any individual or organization can be involved.

https://www.drupaldiversity.com/

Drupal Diversity & Inclusion has been working on: 

• Defining our roles & responsibilities: https://www.drupaldiversity.com/docs/roles-and-responsibilities
• Recruiting new leaders to our leadership team
• Holding space for our community to discuss diversity & justice
• Planning social events for marginalized individuals
• Developing talks & booth activities for Drupal events (most recently BADCamp)

2020 has been our greatest challenge. :)

We have struggled with volunteer burnout, due to both COVID-19 and the US election cycle. Many folks have very limited time to give and even less energy, so we have focused on activities that support folks rather than new programming. 

We are thrilled to have three new individuals on our leadership team: Tearyne Almendariz as Careers Lead (https://www.drupal.org/u/ninelivesblackcat), Monica Flores as Resources Contributor (https://www.drupal.org/u/monicadear) and Esaya Jokonya as Booth Contributor (https://www.drupal.org/u/esayaj). 

Please join our meetings! We are making 2021 plans, and focusing on careers & job hunting for marginalized folks. We’d love to have more hiring managers and HR professionals involved in that work. Bring your ideas and we can work together to make the Drupal community more diverse & inclusive.

https://www.drupal.org/project/swagshop and, of course, visit the Swag Shop itself, at https://www.drupal.org/swag

On one hand, helping local DrupalCamps and DrupalCon to collaborate with the shop. On the other hand we’ve been trying to make sure the products available were event specific.

Coordinating information and people, and particularly everything related to vouchers, discount codes has been particularly challenging

Watching other Drupal camps getting interested in using the swag shop and discovering that it gives them a good value as well. For example, NedCamp: https://nedcamp.org/

We need more people to talk about the initiative, and if you know a local camp, encourage the organisers to join the initiative.

https://www.drupal.org/docs/accessibility

Our main priority has been helping the Claro and Olivero themes reach a high enough accessibility standard to make it into core. We believe that these two projects will have a significant impact on enhancing Drupal’s position as an accessible authoring platform out of the box. 

A secondary priority has been increasing community involvement, and this is where we will focus our principal efforts over the next three months.

Our greatest challenge is limited time and resources, largely due to the additional strain that COVID lockdowns and distance learning/remote working has put on our maintainers. 

An additional challenge is that our documentation is woefully out of date. This makes it more difficult for us to easily onboard potential contributors.

We held a public review of Olivero with the National Federation of the Blind (NFB). This is the start of what we hope may be a long standing relationship, as well as a new process for evaluating the accessibility of core contributions. We also added a new provisional topic maintainer, Ben Mullins!

Yes! Please review issues tagged with #accessibility, and find ones to fix, or that you would like to bring to our monthly office hours! You don’t have to be an expert. 

Become accessibility champions for initiatives that interest you and start conversations with us early so that we can help you find the right resources for evaluation and feedback. 

Finally, our documentation needs to be brought up to date, and your help would be welcome. 

https://www.drupal.org/project/drupalladder and https://drupalladder.org

Feature development focused on

1. usability for learners and
2. connecting Ladder info to corresponding official docs

User experience design of the website

Seeing the value of the broad concepts and fitting together some of the major features

Help us by sharing information about how you work effectively - reach back to the people following in your footsteps and give them clear, adaptable paths to success

https://groups.drupal.org/google-summer-code – our community collaboration location  https://summerofcode.withgoogle.com/ – Google’s official program website  https://www.drupal.org/node/2415225 – where to get started for students (good read for potential mentors too). Read the 12 steps to help any student can get started on their own @ https://groups.drupal.org/node/535795

Google Summer of Code? an annual program for university students organized by Google with projects managed by open source organization mentors such as us (Drupal!). GSoC takes place during “summertime in North America” and wrapped up October with a very successful project. 

As a community, our initiative’s team of volunteers and mentors priority was supporting our student Vishal contributing to Drupal for several months. It was our responsibility to help the student learn more than writing code for a module. As mentors, we helped the student learn project management tools with professionally managed issue queues and techniques such as SCRUM. e reviewed code and tested modules with feedback helping a student who didn’t have a background in Drupal. As a community of volunteers, we made it a priority to ensure that our selected student would be as successful as possible.

Finding mentors and projects ideas. If you’re interested in mentoring, please realize that we pair each student with on average 3-5 mentors per project. Mentoring is not a full time gig and can be accomplished with a few hours per week. Even if you simply have an idea for a project without becoming a mentor, please contact us at @ https://groups.drupal.org/node/536212

Vishal Chaudhary ( https://www.drupal.org/u/vishalghyv ) was Drupal’s Google Summer of Code 2020 student and obviously our greatest success in the last year. The fact that Drupal continues to find at least one student every year who becomes a truly amazing member of our community provides evidence GSoC was a success in 2020. 

Find Vishal’s code below and read about his journey through his @vishal38785">weekly GSoC blog and review his work on the Commerce Fraud project page. 

We also conducted an interview with Vishal, one of his mentors, and the creator of Drupal Commerce:

{{insert Youtube video here}}

Do you have a project idea and/or want to be a mentor? Please edit our 2021 project idea page @ https://groups.drupal.org/node/536212 with your idea. Even a few sentences or a link to an existing module page that can be ported to D8/9 works.

https://www.drupal.org/community/cwg

1. The Community Health Team has been developing “nudge” templates to be used in issue queues to encourage all participants to engage in positive discourse: https://www.drupal.org/project/drupal_cwg/issues/3129687
2. Offering discounted Code of Conduct enforcement training for Encouraging representatives from DrupalCamps and other events: https://www.drupal.org/community/cwg/blog/a-different-kind-of-contribution-become-a-trained-drupal-event-code-of-conduct
3. Offering discounted Mental Health First Aid training for Drupal community members: https://www.drupal.org/community/cwg/blog/online-mental-health-first-aid-workshop-october-27-2020

Come to our session at DrupalCon Europe to learn more about what we’re doing and how you can get involved! https://events.drupal.org/europe2020/sessions/how-community-working-group-helping-make-healthier-community-panel

We hope that this first edition of our quarterly update has been useful. Because this first edition is an experiment, we’d very much like your feedback as a contributor or potential contributor to Drupal. 

• What do you think about the length? 
• Would it be more helpful to organize by code and non-code initiatives, or by some other method? 
• Does quarterly seem like the right cadence? 
• What would make the calls to action more clear for how to get involved?

Please let us know any ideas you have to help keep the community more informed and able to understand how to get involved.

Check out our recap of our favorite Drupal-related posts from November and stay up to date with what’s going on in the Drupalverse.