clemens-tolboom pushed to develop in clemens-tolboom/godot_3_spawn_points

On github - Thu, 2020/11/12 - 9:44am
clemens-tolboom pushed to develop in clemens-tolboom/godot_3_spawn_points Nov 12, 2020 2 commits to develop Blog: Top Drupal blog posts from October 2020

Planet Drupal - Thu, 2020/11/12 - 7:26am

Like every month, we’ve compiled some of the top Drupal blog posts written the previous month. Take a look at our list for October.

Categories: Core web vitals - how to debug and improve cumulative layout shift (CLS) issues

Planet Drupal - Wed, 2020/11/11 - 9:15pm

TLDR : Check your cookie popup!

It seems everyone is talking about core web vitals at the moment, spurred on by Googles’ recent announcement that page experience (which includes core web vitals) will start influencing search ranking in May 2021.

We won’t go into detail on web vitals in this post - there is plenty of information already on the web, including from Google themselves on the excellent site.

Instead, this post will look specifically at cumulative layout shift - or CLS as it’s known. I like to think of this as the jerkiness measure of your site - the higher the number the worse the jerkiness.

Getting your CLS score is pretty easy - you can use pagespeed or lighthouse (built right into chrome). I will assume (because you are reading this post) that you have done this already AND you are not happy with your score. So - what next - how do you go about diagnosing and fixing the issue?

The reading online makes lots of great suggestions, mostly around helping the browser reserve space for elements that are late loaded (images, video etc). This is all good stuff - however - it didn’t help me and the sites I was working on.

So first off I switched to incognito mode (I wanted to simulate a fresh first-time visit to the site - for various reasons) in chrome, loaded the site and then fired up the performance tab in the chrome dev tools. This is a scary looking tab - there is a lot going on here - and you can safely ignore 98% of it (at least for now). You just need to make sure the ‘Screenshots’ tick box is ticked - then hit the little refresh icon - this will refresh the page and start profiling the page load. It’s worth pointing out that this is running locally so you can use it on your local dev sites.

This takes a few seconds and when complete you should have a lovely looking film strip of screenshots along the top - mouseover and you get a larger version. Start at the left and move rightwards - and keep your eyes open for any obvious content shifts.

I did this for 3 individual and unrelated client sites - and found the cookie popup to be the culprit in 2 of the sites - it was appearing mid-way through the load and pushing ALL the content down - fixing this took around .4 off the CLS score (which is a lot). The other site had the ENTIRE expanded mobile menu briefly rendering at the top of the page - which then disappeared (as it should) and shifted all the page content up by about 800px! Fixing this took about .5 off the CLS score.

So - the takeaway from this is probably before you spend ages fiddling with width and height attributes on your img tags, have a quick look to make sure there isn’t some low hanging fruit massively impacting your CLS.

Categories: blog: Live deployment previews for Drupal Core (Thanks to TugboatQA!)

Planet Drupal - Wed, 2020/11/11 - 6:30pm offers automated and on-demand deployment previews to accelerate development. In 2019, Tugboat was successfully integrated as the backbone of the community testbed Following that success, a community-lead initiative emerged to provide these previews for all of Drupal Core development, by integrating into the issue queue. Drupal Association CTO Tim Lehnen (hestenet on opened an issue to explore this option in early August.

Why automated environments for Core issues?

Reviewing and testing issues has historically been the purview of experienced Drupal developers. Designers, end-users, and other stakeholders have been relegated to the role of watching over the shoulder of developers who drive demos from local development environments. This has been detrimental to fully involving those stakeholders in a development process that could improve Drupal for all users. With Drupal's ease-of-use, accessibility, and front-end features being central to the current strategic initiatives, it was time to ensure that these stakeholders are fully empowered. 

Automated deploy environments help bridge the technical divide and bring the ability to review changes to more users. Longtime Drupal contributor YesCT says:

The Tugboat integration with issues makes reviewing and testing possible for people who have never been able to do it before. This project uses technology to lower the barriers of contributing to Drupal, and makes contributing more accessible to more people. It’s going to be a huge game-changer.

In practice, visitors to the issue queue can click a link to tour a live, working version of a Drupal website wherever Tugboat deploy previews are enabled. As of November 10, 2020, this includes all Drupal Core issues.

Current UI:

Upcoming UI revision: deploy previews - under the hood

The integration relied on a handful of contributors across a project that spanned months, but the core of this collaboration was a partnership between core contributor Juampy NR and architect Neil Drumm

As a senior developer at Lullabot, Juampy's continuous integration expertise, as well as his familiarity with Tugboat, made him an invaluable contributor to implementing the Tugboat side of the integration. Neil's expertise as architect, meanwhile, gave Juampy and Tugboat the guidance to find the right places in's custom logic to add code for this new integration. Simultaneous to the Tugboat integration, Juampy and Neil also worked to implement the Drupal Association GitLab integration, bringing issue forks and merge requests to the issue queue

Some of the challenges that this team faced included:

  •’s large database. Because of the size of the database, the team had to work remotely using a provisioned development environment. Remote debugging helped to catch and traverse the different events involved in the workflow.

  • Understanding where to write code. has a ton of custom logic, so finding the right place to add new code was not easy. The Drupal Association's guidance was key.

  • Integrating multiple systems. The team had to write interactions between, Tugboat, and GitLab, taking into account error responses, timeouts, and firewall restrictions.

Reducing friction by making changes visible and more accessible to all contributors

Before this integration, contributors had to take and upload screenshots of their changes, and reviewers had to replicate changes locally in order to see them in action. Tugboat reduces friction by making changes visible - and more accessible - to anyone who clicks the preview URL. This shortens review time considerably and invites participation from non-developers, working toward Drupal's value of respecting and valuing inclusivity.

Check out our documentation on to learn more!

The Drupal Association gives our thanks to TugboatQA/Lullabot, for contributing this feature to the Drupal project.


Tag1 Consulting: Drupal 7 extended support: An overview of the Drupal 7 Extended Support Program - Tag1 TeamTalk #028.2

Planet Drupal - Wed, 2020/11/11 - 5:30pm

Tag1 Quo, Tag1's extended support service for Drupal, offers you peace of mind when it comes to receiving all of the important security updates that Drupal 7 Extended Support (D7ES) vendors maintain. But Tag1 Quo goes well beyond the minimum requirements of the D7ES program, because we cover all of your contributed modules and notify you right away of security patches that need your attention.

Read more preston Wed, 11/11/2020 - 08:30

OpenSense Labs: Hiring The Right Skills for Your Decoupled Drupal Development

Planet Drupal - Wed, 2020/11/11 - 2:53pm
Hiring The Right Skills for Your Decoupled Drupal Development Gurpreet Kaur Wed, 11/11/2020 - 19:23

Drupal development is not everyone’s cup of tea, however, it could be, provided that the person at the development end has the right skill set to handle all of Drupal’s potential. With Decoupled Drupal the need for these skills becomes even more prominent, you have to have excellent front-end and back-end developers separately since the two are independent of each other. And this is where the hiring process of the right set of professionals for your Decoupled Drupal projects becomes tricky and cumbersome.There are a lot of aspects to take under consideration and a lot of different skills to look for.

To make your job a tad bit easy, here is the checklist of the skill sets and the professionals that you need to successfully deliver the Decoupled Drupal projects.. 

What skills are needed for Drupal development during the decoupling process?

When you decouple Drupal, you are only going to be using it as a content repository, meaning it would only serve a purpose for backend development needs. Even if you use it for back-end, you are still going to be using it, so you would need good Drupal developers. So, here are the skills you need to be looking out for.

Proficiency in Site Building 

You must know how important it is to attend primary school, the things we learn set the pace for our entire educational journey. So, what primary school is to us, Site Building is to Drupal. It is the most basic need of a Drupal website. 

The primary purpose of a site builder is to reap all the benefits of Drupal by making it run and configuring all the options required to make a website fully functional. There isn’t a need for a custom code for this to happen, rather the Admin User Interface is equipped to handle it on its own. There are several other responsibilities of site builders as well, so, when hiring a site builder, you must keep in mind all of these.

  • Installing  Drupal manually and also doing the same with an application or a service;
  • Downloading and installing modules along with disabling, uninstalling and removing them;
  • Understanding of all core and contributed modules; 
  • Thorough knowledge of fields and entities with expertise in content and non-content fields;
  • Finally, being familiar with blocks, menus and navigation as well as the basic Views skills;

All of these are the everyday requirements for site builders, and a proficient one excels at all of them.

Proficiency in Backend Development

The decoupled Drupal requires backend developers to be at their best at all times. This is because an impeccable front-end would seem sub-standard, if the content repository is not up to the par. There when hiring backend developers, you have to be extra picky and choose one who fits the criteria to the T. And here is what the criteria looks like;

  • Unlike site builders, Backend developers are involved in writing the code in PHP and other languages, so they must have experience in PHP and MySQL at least. 
  • They must be competent in creating and executing modules. The added knowledge of building custom modules in Drupal 7, 8 and 9 (for Drupal 7 and Drupal 8 have not reached End-of-life as yet) is always preferable. 
  • They also need to have advanced knowledge of themes, consuming web services and automated deployments to name a few. 
  • The backend developer has to be aware of all the security concerns as well, along with the ways of overcoming them.
Proficiency in Theming

Theming is a part of Drupal’s front-end development. I know you must be wondering why decoupled Drupal would need front-end developers with experience in Drupal. To answer your question, I have three words; Progressively Decoupled Drupal

Because the entire front-end is not separated from Drupal, it is important to have a good themer to build around Drupal’s front-end capabilities. Themers are responsible for the front-end design as well as the development and implementation of the client-side architecture. 

For this purpose, 

  • they need to be experts in front-end technologies;
  • they need to be experts in installing themes and generating sub-themes using PHP or Twig in Drupal;
  • they need to be experts in designs and modifying them into a completely functional issue;
  • they need to be experts in creating such modules that would expose the configuration to the site builders. 

When you find someone like this, you would have the perfect themer for your progressively decoupled Drupal. 

Read these infinity stones of Drupal development to adhere to the best practices when it comes to everything ranging from site-building to backend development.

Proficiency in Drupal Architecture 

Drupal work is often regarded as web projects, and each project has to have someone who is aware of the ins and outs of the work. And in the case of Drupal that person is a Drupal Architect. 

A Drupal architect is essentially the manager of the project, who possesses knowledge of all the key areas of the project. From backend development and site building to front end development and theming, he needs to be proficient in every task as a leader. 

He should have an in-depth understanding of the ways to optimise Drupal because that is what the main role of a Drupal architect is. For the same, a certain level of expertise in PHP, MySQL, JQuery and CSS along with the knowledge of implementation tools like Varnish, GeoIP and UberCart comes in quite handy. 

Note: Some proficiency in front-end technologies is always beneficial for Drupal developers. This may seem odd to you, since we are talking about the Drupal skills in decoupling. However, it isn’t much of an oddity and let me tell you why. We know that when decoupling is done, the presentation layer is entirely separated from the content aspect of a website, yet they still have to work together and they have to be in sync. This would become all the more convenient for decoupled Drupal developers, if they have some knowledge of the current front-end technologies. HTML, CSS, React and Gatsby are some of the most used technologies, so an understanding or maybe even some experience in using it would come in very handy for the streamlined development of a decoupled Drupal website. 

Read these infinity stones of Drupal development to adhere to the best practices when it comes to everything ranging from site-building to backend development.

What is the requirement for Drupal web services?

The decoupled Drupal needs a good API layer for it to give you all the benefits it boasts. And a good API is only good when it is being handled by competent hands and these hands are your developers’. 

There are three particular web services that are being implemented during decoupling. Although all three will be achieving the same goal, the way they do it is quite different. Therefore, your developers need to be aware of even the minutest details of these web services, especially with respect to the different Drupal versions.

Starting with GraphQL, firstly, it is not available in Drupal 7; an expert developer would know this. The GraphQL module in Drupal 8 and 9 will let your developers create their own custom schema or extend an existing one, as long as they are good with coding. 

JSON:API is also not available in Drupal 7 and even in Drupal 8, it was a late addition, having been added as a stable core feature in Drupal 8.7. With the JSON:API module, a developer can decide which HTTP methods he should be using along with which response codes should be returned and when, eventually increasing productivity. A JSON:API expert would do it with ease. 

Coming to REST API, it has been a part of Drupal core for a long time. Your developers need to be equipped to configure REST resources, customise their formats, customise their authentication mechanism as well as create the plugins.

A developer who speaks fluently in Drupal web services is the developer with the right skill set for Decoupled Drupal, since the API is the thread that holds both the front and backend together. 

How do you capitalise the separated front end?

Now that Drupal specific skills are out of the way, let us move on to the presentation layer and the technologies the front-end developers need to be experienced with. 


When talking about front-end development, the first things that come to mind are HTML and CSS. As you may know, the structure and layout of a page, both of the visual and aural, depends on these two, making them quite crucial for your web pages. Henceforth, they are the  foundational technologies for building web pages, front-end developers need to be experts in these. 

JavaScript Frameworks

For many, the primary reason behind taking up decoupling is to take advantage of the advanced JavaScript framework. Although Drupal has its own JavaScript library, it still lacks in the features provided by the JS framework.

React, Vue and Angular tend to be the most sought after technologies for transitioning into decoupled Drupal., with Vue.js being the latest addition in the mix. Frontend developers need to be aware of these and get the most of them with their knowledge. 

Static Site Generators 

If you have a static site with already available input files, you would want to delve into Static Site Generators for your frontend development. For this reason, you would need experts in SSG to fully capitalise its various tools. Gatsby, Metalsmith and Tome are the ones that are the most renowned at present. 

Note: There is one more thing that you should be looking for in your front-end developer and that is the knowledge of Drupal. Like I mentioned in the previous section, the Drupal developers need to have some knowledge of the front-end technologies, similarly, the front-end developers need to have knowledge of the Drupal. Both the back-end and front-end may be different and their development may also be different, but they are going to be a part of one web project, so both teams need to have some cognisance of the other’s working. Decoupling would make a lot more sense then.

What other skills should you be looking for?

Up until now, we have discussed all the skills specific to the development of decoupled Drupal, you might think that your work is done, but it isn’t. There are certain skills that need to be held by developers, whether they are involved in decoupled Drupal or monolithic Drupal and they are going to be equally important for your decoupled Drupal project. 

Adept at Designing

The process of website building starts with designing. The very first step towards development is the making of wireframe, which is basically a design template. This wireframe sets the pace and the direction of the web project, so your designer has to know what he is doing because if he doesn’t, the end would not be as enlightening as you might want. 

Designing mandates tools, without them a designer would be helpless. Sketch, Figma, InvisionApp and Adobe XD are some of the go-to options for User Interface designing. The apprehension of these would make a designer adept at his job.

Adept at DevOps 

In essence, DevOps is an IT service delivery channel that focuses on the adoption of practises that would collaborate your operations with the development team. For this to happen, you need a DevOps Engineer or a System Admin, who would be responsible for deploying websites to the live server. 

  • Expertise in Linux;
  • Expertise in bash scripting and continuous integration;
  • Expertise in automations technologies;
  • And expertise in IAC (Infrastructure as Code) are essentials for this particular hiring objective. 
Adept at QA 

QA refers to quality assurance. It is a position held by developers to check the quality of work being churned out. They act as the targeted client and see whether what they are getting from the website is up to the standards or not. 

Someone with limited knowledge of Drupal, web technologies and the industry requirements would not be a good fit. You would only be able to check something, if you know what to look for, right?

Adept at Project management 

Like the suggests, this is a skill that oversees the project from the very beginning to the very end. From time deadlines to the day-to-day progress of the project, each and every aspect has to be monitored. 

Drupal Project Management requires the manager to be skilled at a variety of things, namely;

  • Expertise in team management and segregation of workload;
  • Expertise in dealing with the clientele to understand their requirements and acting as the middle ground between them and the team;
  • Expertise in analysing and rectifying plausible risks during the project;
  • Expertise in the Drupal and all the technologies that accompany Drupal projects; 
  • And expertise in using reporting tools and implementing sound SEO strategies.
Adept at Business analysis

Every Drupal site has a business side, so when hiring the right skill set for decoupling, business analysis holds a key to success. Through business analysis, the business and IT sides of the website find a connection and work together. This is done through the use of data analytics, which help in examining the undergoing processes, analysing its needs and effectively communicating the same to the executives and stakeholders along with running logic/system interference with them. 

While using Drupal, it is always preferable to have an analyst that has a development background with knowledge of Drupal. Extroverts are usually ideal for this position, since communication is vital here.

The Sum Total 

Drupal is a pretty diverse system and an even higher level of diversity is found when Drupal is decoupled. Since you would be trying to capitalise Drupal in addition to capitalising other frontend technologies, you would have to put in an extra effort in the hiring process. Decoupled Drupal developers need to be equipped to handle the diversity it is going to inundate them with. The right skill set would help you and them to reap the benefits of decoupling. 

blog banner blog image Decoupled Drupal Decoupled Drupal Development Drupal Drupal Developer Frontend developer Blog Type Tech Is it a good read ? On

Mediacurrent: Expanding Open Source with WordPress

Planet Drupal - Wed, 2020/11/11 - 2:26pm

If you know us at Mediacurrent, you know we create amazing digital experiences with Drupal. Did you know we also support WordPress websites?

Since 2007, Mediacurrent has been the open source expansion partner for enterprises and global brands. As certified experts, we have a reputation for providing best-in-class digital solutions and growing long-term, strategic partnerships for clients like, MagMutual, and Emory University

With thousands of implementations and thought leadership resources completed, we have been continuously looking for ways to add more value to our customers. We've seen a rising need in our Drupal community through hours of partnerships, and that need is more WordPress support. 

WordPress in the enterprise has risen 16%, driven largely by the rise of multiple CMS use.

- Source: The Rise of Multi-CMS in the Enterprise

Why the Expansion?

For over a decade, we have been helping customers migrate from WordPress to Drupal, and we've proven ourselves a trustworthy partner in the migration process. As we've grown, we’ve expanded our Drupal expertise into deep open source strategies—partnering with clients on a long-term basis to solve their technology challenges.

Many enterprise organizations that have standardized on Drupal will still have some non-Drupal sites in their ecosystem. That's where Mediacurrent comes in as a single-source digital partner. 

What We've Done So Far

Currently, Mediacurrent is assisting large-scale enterprises with their WordPress sites. What started as Drupal legacy clients have turned into an opportunity to better serve our customers. Our open source software clients came to us with similar pain points, and thanks to our long-term partnership, we were able to provide crucial benefits that provided a valuable impact on their return of investment, including but not limited to:

  • Engaging UX - Our recent WordPress customers faced the challenge of creating an engaging user experience. Mediacurrent planned for a full redesign of the website's look and feel, providing randing, design, and value proposition workshops and including considerations for persona needs and critical business objectives.
  • Data-driven Strategy - These organizations needed to maximize the return on their digital investment. Mediacurrent is continuing to incorporate best practices for content, page layout, navigation, lead generation, and search engine optimization.
  • Open Source Training - Designs were implemented using the Elementor page builder plugin for WordPress. Mediacurrent’s training team provided specialized instruction on Elementor page design to create page layouts and components. 
  • Post-Launch Support - Monthly support agreements help to optimize for performance and security, providing immediate value to our legacy customers. Security updates to WordPress and plugins can (and do) come at any moment. You must have a dedicated support team closely monitoring and upgrading the code regularly.

Where We're Going

Moving forward, we will expand our support for open source clients who maintain Drupal and WordPress websites within their organizations. If 2020 has taught us anything, it’s that Mediacurrent needs to pivot with our customers' needs and continue to provide the best solutions possible.

As your digital partner, Mediacurrent will evaluate your web properties by assessing several core functionalities including;

  • Security - Making sure your WordPress site stays updated and secure.
  • Responsive Design and Development - Mobile-first designs backed by data and user research.
  • Search Engine Optimization - We consider three factors when it comes to perfecting your on-page optimization: Page load times, implementation, and CDN.
  • Content Authoring Experience - A seamless publishing workflow is the key to empower content creators. Tools like Elementor let teams create and design new page layouts on the fly using a drag and drop interface. We've found this very similar to Drupal's Layout Builder, but more advanced and easier to use. 

We see organizations growing, and the need to evolve our services to support others who have more than one CMS to manage. 

49% of enterprises are planning to expand to additional CMSs in the future.

- Source: The Rise of Multi-CMS in the Enterprise

How We Can Help 

Mediacurrent is excited to continue to expand our unique value proposition to organizations that aren’t standardized on a single platform and require peace of mind in terms of quality, security, and consistency. We have a reputation as a valued partner that is driven by growth strategy, risk mitigation, solving complex business problems, and producing real, bottom-line value with our solutions.

If you’re already running on Drupal and need help managing additional WordPress sites, or just have a lot of questions about migration, security, or future support, please reach out to the Mediacurrent team. We are available to discuss your websites' future, how we can help you efficiently manage your existing platforms, and provide a strategic roadmap that will keep your multi-CMS organization on the path to success  


Specbee: Evaluating a Drupal Partner for your Next Project – Some Unbiased Tips and Suggestions

Planet Drupal - Wed, 2020/11/11 - 11:00am
Evaluating a Drupal Partner for your Next Project – Some Unbiased Tips and Suggestions Ashirwad Shetty 11 Nov, 2020 Top 10 best practices for designing a perfect UX for your mobile app

Building and maintaining superlative web experiences requires a focused team that specializes in delivering quality digital solutions to take your business to the next level. Some businesses have this team in-house while others don't. Mainly because the skills required of this team are not core to their production activities. Or because the activities involved don’t warrant a full-time in-house team. This is where a development partner comes in.

Trust is a clincher when it comes to choosing the right development partner. But finding a trustworthy partner takes some time and research, which will be truly worth the effort after all. Your Drupal development partner must not only be an expert with Drupal but be honest and maintain transparency right from the start; when they assess your requirements and tell you if Drupal is the right fit for you or not. Apart from honesty, transparency and trust, here is a list of pointers you should look out for when choosing a Drupal development partner. 

 1. Experience and Expertise (obviously)

All Drupal development agencies claim the best expertise and tons of experience. You need to find out if the experience is relevant to your technology, and more importantly, your business needs or not. Find an agency that has worked with and delivered at enterprises of your size. Ask for exact case studies addressing the top challenges you face and how the Drupal agency has addressed similar challenges in the past. Challenges could be with respect to specific third-party integrations, stakeholders, traffic or any other aspects.

2.  Ideal Fit

The Drupal development company you choose to partner with will be an extension of your team. They might be the best in the business but are they the right fit for you? Communication is key here. Interact with people who will be directly involved with the project. Not just the salesperson. This includes the delivery manager, technical architect, and key project personnel. You should get a feeling that the people who you are interacting with belong to your team and will treat your purpose as theirs.

3. Understanding of the Project scope

Your ideal Drupal development partner will ensure that your project scope is understood, executed, and delivered in the way you had envisioned. Make sure the team you choose understands what is involved. Don't go with a team that says, "We are compliant ... what is your requirement?". The best way to know if they have understood the project is to ask them to prepare a scope of work and see if it aligns with what you want from the project. This involves one or more detailed discussions with your team. Be prepared for this.

4. Quality of Response

This one is often overlooked by organizations while it remains one of the top qualities to be looking for in a development partner. Although the average response time is about 12 hours, it is not only the time factor that matters. The quality of response shows the way the team perceives your problems. More often than not, you will know if the team you are dealing with is responding within your expectations (of time, information). This is a good indicator of interest as well as a benchmark on how they will interact with you once the project is underway.

5. Reference calls

Your Drupal development partner’s client list speaks a lot about them. However, what can really help is to ask for reference calls with their customers. This will aid in finding out how their experience has been in terms of technical knowledge, communication, project management and in general about how happy they are. 

6. Proof of Concept (if you have the time): 

There’s so much at stake in terms of time, resources, investment, and more when you dive into a development partnership. Asking for a Proof of Concept (PoC) will not only help you identify the team’s performance but also if the end result matches your requirements. Request the team to develop a PoC. May be a vanilla Drupal release with specific features and functionality that can be done in 1-2 weeks. See how they perform there and if the way they communicate during the PoC meets your expectations.

7. Drupal community involvement

If your Drupal partner is an active community member and contributor, you know that they not only have the skill and expertise, but they also believe in giving back to the community. A commitment to Drupal shows that they truly believe Drupal is important for them and that they are in it for the long haul. Do a research on how involved they are in the Drupal community.

Every year, Dries conducts an in-depth analysis of the top 30 Drupal companies and individuals around the world that contribute to the project. That’s a good place to look out for your Drupal agency partner.

Choosing a technology partner who can envision your goals is not easy when you have tons of agencies to choose from. This list of must-haves is not exhaustive but can give you a jumpstart on your process of finding your ideal Drupal development partner. Reach out to us to find how we can help you with your next Drupal project.

Drupal Planet Drupal Development Drupal Shefali ShettyApr 05, 2017 Subscribe For Our Newsletter And Stay Updated Subscribe

Leave us a Comment

  Shefali ShettyApr 05, 2017 Recent Posts Image Evaluating a Drupal Partner for your Next Project – Some Unbiased Tips and Suggestions Image How to Import External Feeds into your Drupal 9 Website with the Feeds Module Image What To Expect From Drupal 9.1 Want to extract the maximum out of Drupal? TALK TO US Featured Success Stories

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


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.


Matt Glaman: The impact individual funding can make on open source maintenance

Planet Drupal - Wed, 2020/11/11 - 2:22am

For the past three months, Richard Sheppard has been a financial contributor to ContribKanban on OpenCollective. I'm extremely grateful for his decision to put his money towards my project every month. $5 a month may not seem like much, but the impact is greater than its monetary value. It's a reminder. A reminder that someone finds value in a project I maintain in my free time and has been a pet project for years. 

It's a project which could always use some feature development, but usually more maintenance. The monthly contribution doesn't exactly cover labor, but it does keep the project maintained and up to date.

I also want to mention those who have sponsored me in general on GitHub Sponsors.


Lullabot: The 7 Best Practices of a Good Editorial Experience

Planet Drupal - Tue, 2020/11/10 - 9:46pm

The success of a CMS project ultimately depends upon the content it contains. No matter how “on-time” or “under-budget” a project might be, editors have to be able to create and manage content, and they need to be able to do it without feeling the need to pull their own hair out.


Mediacurrent: Mediacurrent IDEA Team Charts the Course for Inclusion

Planet Drupal - Tue, 2020/11/10 - 3:05pm
Open Source for Everyone

Open source runs the digital world. As a top 10 contributor to Drupal—the software used by 1 out of 30 sites in the world—Mediacurrent feels a deep sense of responsibility to be the change we wish to see. 

From “IDEA” to Reality 

Building a culture that values open dialogue and accountability around issues of diversity and inclusion has always been our goal. This year, we took steps to define our core values and unite our voices for change by launching an employee-led diversity council. Our Inclusion, Diversity, Equity, & Awareness (IDEA) team drives an important mission. The group strives to lift up marginalized voices in tech and address difficult, ongoing challenges including societal racism, racial bias, transphobia, and homophobia. 

Opening Up About Privilege 

The IDEA committee brings many voices together. As Mediacurrent’s Director of Project Management, I’m proud to be one of those voices.

We often hear that the benefit of open source communities is that anyone can contribute. Yet, this paints a rosy picture of equality that’s far from the current reality in our Drupal community. (Drupal creator Dries Buytaert presents the issue well in this article: The Privilege of Free Time in Open Source.) My personal mission is to lead a dialogue on understanding how individual privilege can open doors for an open source community that's as wonderfully diverse as Drupal’s end users. 

What can those with privilege do to effect change? I grappled with this question in a DrupalCon Seattle session Putting Our Privilege to Work for Inclusivity in Open Source, below. It represents the types of conversations happening within our IDEA committee:

  • What does privilege look like?
  • Mindfulness and recognizing our own privilege
  • How to address privilege in others...gently
  • How to bring about real change

The Path Forward

The IDEA team is hard at work on a few upcoming initiatives, including:

  • Sharing new data about our employee diversity 
  • Making socially conscious choices together about the charities we support 
  • Updating job postings to include our values
  • Technical documentation audit for inclusive language

We look forward to introducing more members of the Mediacurrent IDEA team and sharing some of the many in-progress initiatives on our path forward.


Promet Source: Illinois Sees Sharp Spike in ADA Title III Lawsuits

Planet Drupal - Tue, 2020/11/10 - 1:01am
ADA Title III lawsuits are on the rise, but nowhere was the 2018 to 2019 increase more extreme than in the state of Illinois, where the number of federal lawsuits more than doubled from 70 in 2018 to 190 in 2019. This 171 percent increase highlights the importance of ADA web accessibility compliance.   

undpaul: DDEV - Simplify local dev environment

Planet Drupal - Tue, 2020/11/10 - 1:00am
What the craftsmen use for their workshops is the local development environment for our development team. To keep it simple and comfortable, we now use DDEV, an open-source tool based on Docker. This already simplifies the daily work for our development team enormously.

Jacob Rockowitz: One of my biggest mistakes while building the Webform module for Drupal

Planet Drupal - Mon, 2020/11/09 - 4:34pm

For the past year, I have been working towards a stable release of Webform 6.x for Drupal 8/9. Last year, I published a blog post titled, A bump in the Webform module’s road to Drupal 9, where I stated...

That post specially focused on refactoring classes to not override constructors for service objects, plugins, and controllers. The post concluded by stating the Webform module’s version number will have to be bumped up from 5.x to 6.x. Besides refactoring constructors on the Webform module’s road to Drupal 9, I have also removed deprecated code, fixed some challenging issues, and managed to correct a few mistakes. That said, there are some issues and bad-smelling code that are not easy to fix.

Drupal provides a robust and well-thought-out API and UI for translating content and configuration. If you have a reasonably simple module that correctly defines a schema/metadata for configuration entities and uses Field API for content entities, Drupal’s translation system works as expected. The Webform module is not a simple module and using the basic schema/metadata definitions for configuration entities wasn’t always an option. Before I get into some technical details around these mistakes, there is a much simpler reason I made mistakes around translations: I only speak English and rarely use Drupal’s translation system.

As a non-disabled English speaking Drupal module developer, I made two mistakes while building the Webform module…

Fortunately, I started caring about accessibility and fixed most of the Webform module’s accessibility issues. Now, accessibility is one of the first things I consider when adding a new UI feature. I also did not think...Read More


Tag1 Consulting: Core Confidential with Angie Byron (webchick) : The many faces of Drupal over 15 years - Pt. 2

Planet Drupal - Mon, 2020/11/09 - 1:03pm

Part 1 | Part 2 Drupal is notorious for its "everyone has a voice" approach to open-source development, but it isn't easy to reach consensus across thousands of people with different backgrounds and opinions. In addition, Drupal has witnessed countless paradigm shifts in its lengthy history, both in the surrounding world of web development and in its internal workings. As Drupal has grown to power over two percent of the websites on the entire internet, many new workflows and governance structures have had to be put in place to guarantee the continued longevity of the Drupal community. In addition, with end-of-life quickly approaching for Drupal 7, contributors now have to juggle a widening range of versions. In this very special two-part series, join Angie Byron (Senior Director, Product and Community Development at Acquia), Michael Meyers (Managing Director at Tag1 Consulting), and your Core Confidential host Preston So (Editor in Chief at Tag1 Consulting), for a fireside chat with the one and only Angie Byron. We dove into some of the amazing (and not so amazing) things Angie has seen over the course of her fifteen years deeply involved in Drupal core development as well as what people need...

Read more preston Mon, 11/09/2020 - 04:03

Dries Buytaert: Who sponsors Drupal development? (2019-2020 edition)

Planet Drupal - Mon, 2020/11/09 - 12:17pm

For the past few years, I've examined's contribution data to understand how the Drupal project works. Who develops Drupal? How diverse is the Drupal community? How much of Drupal's maintenance and innovation is sponsored? Where do sponsorships come from?

The report might be of interest even if you don't use Drupal. It provides insights into the inner workings of one of the largest Open Source projects in the world.

This year's report shows that:

  • The recorded number of contributions increased year over year.
  • More and more contributions are sponsored, but volunteer contributions remain important to Drupal's success.
  • Drupal's maintenance and innovation depends mostly on smaller Drupal agencies and Acquia. We don't see many contributions from hosting companies, multi-platform digital agencies, system integrators or end users.
  • Drupal's contributors have become more diverse, but are still not diverse enough.

You can look at the 2016 report, the 2017 report, the 2018 report, and the 2019 report.

Methodology What data did we analyze?

We looked at all issues marked "closed" or "fixed" in the 12-month period from July 1, 2019 to June 30, 2020. This for Drupal core and all contributed projects, across all major versions of Drupal.

What are issues?

Each " issue" tracks an idea, feature request, bug report, task, or more. It's similar to "issues" in GitHub or "tickets" in Jira. See for the list of all issues.

What are credits?

In the spring of 2015, I proposed some ideas for how to give credit to Drupal contributors. A year later, added the ability for contributors to attribute their work to an organization or customer sponsor, or mark it the result of volunteer efforts.

A screenshot of an issue comment on You can see that jamadar worked on this patch as a volunteer, but also as part of his day job working for TATA Consultancy Services on behalf of their customer, Pfizer.'s credit system is unique and groundbreaking within the Open Source community. It provides unprecedented insights into the inner workings of a large Open Source project. There are a few limitations with this approach, which we'll address at the end of this report.

What is the Drupal community working on?

In the 12-month period between July 1, 2019 and June 30, 2020, 31,153 issues were marked "closed" or "fixed", a 13% increase from the 27,522 issues in the 2018-2019 period. This averages out to 85 issues marked "closed" or "fixed" each day. This is compared to 75 issues in 2018-2019.

In total, the Drupal community worked on 4,195 different projects this year compared to 3,474 projects in the 2017-2018 period — a large 20% year-over-year increase. I attribute the larger than normal growth to the Drupal 9 release.

Time period Number of issues "fixed" or "closed" by day Number of projects worked on 2017 - 2018 67 3,229 2018 - 2019 75 3,474 2019 - 2020 85 4,195

The majority of the credits are the result of work on contributed modules:

Compared to the previous period, contribution credits increased across all project types:

It is nice to see the "non-product credits" grow. More and more members in the community track credits for non-product contributions. These include organizing Drupal events, presenting at Drupal events, promoting Drupal, mentoring, and more. While some of these increases reflect new contributions, others are existing contributions that are newly reported. The fact that the credit system is becoming more accurate in recognizing more types of Open Source contributions is both important and positive.

Who is working on Drupal?

For this report's time period,'s credit system received contributions from 8,303 different individuals and 1,216 different organizations. We saw a 2.5% decline in individual contributors, but a 7% increase in organizational contributors.

Consistent with previous years, approximately 50% of individual contributors received one credit. Meanwhile, the top 30 contributors (the top 0.4%) account for 20% of the total credits. In other words, a small number of individuals do the majority of the work.

Starting last year, I weighted each credit based on the adoption of the project the credit is attributed to. For example, each contribution credit to Drupal core is given a weight of 10 because Drupal core has about 1 million active installations. Credits to the Webform module, which has over 470,000 installations, get a weight of 4.7. And credits to Drupal's Commerce project get 0.6 points, as it is installed on around 60,000 sites.

The idea is that these weights capture the end user impact of each contribution, but also act as a proxy for the effort required to get a change committed. Getting a change accepted in Drupal core is both more difficult and more impactful than getting a change accepted to a much smaller, contributed project.

This weighting is far from perfect, but so is the unweighted view. For code contributions, the weighted chart may be more accurate than a purely unweighted approach. I included both charts:

No matter how you look at the data, all these individuals put an incredible amount of time and effort into Drupal.

It's important to recognize that most of the top contributors are sponsored by an organization. We value the organizations that sponsor these remarkable individuals. Without their support, it could be more challenging to contribute.

How much of the work is sponsored?

When people contribute to Drupal, they can tag their contribution as a "volunteer contribution" or a "sponsored contribution". Contributions can be marked both volunteer and sponsored at the same time (shown in jamadar's screenshot near the top of this post). This could be the case when a contributor does paid work for a customer, in addition to using unpaid time to add extra functionality or polish.

For those credits with attribution details, 15% were "purely volunteer" (8,429 credits). This is in stark contrast to the 69% that were "purely sponsored" (37,399 credits). Put simply, roughly two-thirds of all contributions are "purely sponsored".

This is the first time in Drupal's history that "purely volunteer" contributions stayed flat year over year. This might be related to COVID-19; coding sprints are harder to organize, people may have lost income, parents are busy home-schooling their children, people have Zoom-fatigue, and times are generally stressful. In contrast, we did see a very large increase in "purely sponsored" contributions.

Volunteer contribution remains very important to Drupal. Volunteers contribute across all areas of the project. A lot of volunteer time and energy goes towards non-product related contributions such as event organization, mentoring, and more.

Who is sponsoring the work?

Now that we've established that the majority of contributions are sponsored, let's study which organizations contribute to Drupal. While 1,216 organizations contributed to Drupal, 50% of them received four credits or less. The top 30 organizations (roughly the top 2.5%) account for approximately 30% of the total credits. This means that the top 30 companies play a crucial role in the health of the Drupal project.

Similar to the individual contributors, I've ranked organizations by both "unweighted contributions" and "weighted contributions". Unweighted scores are based solely on volume of contributions, while weighted scores also try to take into account both the effort and impact of each contribution.

If you are an end user looking for a company to work with, these are some of the companies I'd work with first. Not only do they know Drupal well, they also help improve your investment in Drupal. If you are a Drupal developer looking for work, these are some of the companies I'd apply to first.

A variety of different types of companies are active in Drupal's ecosystem:

Category Description Traditional Drupal businesses Small-to-medium-sized professional services companies that primarily make money using Drupal. They typically employ fewer than 100 employees. Because they specialize in Drupal, many of these companies contribute frequently and are a huge part of our community. Examples are Third & Grove, Thunder, PreviousNext, MD Systems, etc. Digital marketing agencies Larger full-service agencies that have marketing-led practices using a variety of tools, typically including Drupal, Adobe Experience Manager, Sitecore, WordPress, etc. Many of these larger agencies employ thousands of people. Examples are Wunderman, Possible, and Mirum. System integrators Larger companies that specialize in bringing together different technologies into one solution. Example system integrators are Accenture, TATA Consultancy Services, EPAM Systems, and CI&T. Hosting companies Examples are Acquia, Pantheon, and, but also Rackspace or Bluehost. End users Examples are Pfizer or bio.logis Genetic Information Management GmbH.

A few observations:

  • Most of the sponsors in the top 30 are traditional Drupal businesses with fewer than 50 employees. With the exception of Acquia, Drupal's maintenance and innovation largely depends on these small Drupal businesses.
  • The larger, multi-platform digital marketing agencies are barely contributing to Drupal. No digital marketing agencies show up in the top 30, and hardly any appear in the entire list of contributing organizations. I'm frustrated that we have not yet found the right way to communicate the value of contribution to these companies. We need to incentivize these firms to contribute with the same commitment that we see from traditional Drupal businesses.
  • The only system integrator in the top 30 is CI&T. CI&T is a smaller system integrator with approximately 2,500 employees. We see various system integrators outside of the top 30, including EPAM Systems, Globant, Capgemini, Publicis Sapient, Accenture, and TATA Consultancy Services. Accenture and Wipro, despite doing quite a bit of Drupal work, did not receive any credits.
  • Various hosting companies make a lot of money with Drupal, yet only Acquia appears in the top 30 with 1,823 credits. The contribution gap between Acquia and other hosting companies remains very large. It was great to see that Pantheon tripled its contributions from 43 to 122 this period. earned 23 credits compared to 22 in the last period. In general, there is a persistent problem with hosting companies not contributing back.
  • We only saw two end users in the top 30 this year: Thunder (815 credits) and Pfizer (201 credits). Many end users contribute though: European Commission (290 credits), bio.logis (219 credits), Google (144), University of Waterloo (111 credits), Johnson & Johnson (93 credits), University of British Columbia (91 credits), University of Texas at Austin (74 credits), NBCUniversal (48 credits), Workday (38 credits), PayPal (17 credits), and many more.

I often recommend end users to mandate contributions from their partners. Pfizer, for example, only works with agencies that contribute back to Drupal. The State of Georgia started doing the same; they made Open Source contribution a vendor selection criteria. If more end users took this stance, it could have a big impact on Drupal. We'd see many more digital agencies, hosting companies, and system integrators contribute to Drupal.

While we should encourage more organizations to sponsor Drupal contributions, we should also understand and respect that some organizations can give more than others — and that some might not be able to give back at all. Our goal is not to foster an environment that demands what and how others should give back. Instead, we need to help foster an environment worthy of contribution. This is clearly laid out in Drupal's Values and Principles.

How diverse is Drupal?

Supporting diversity and inclusion is essential to the health and success of Drupal. The people who work on Drupal should reflect the diversity of people who use the web.

I looked at both the gender and geographic diversity of contributors.

Gender diversity

Only 10-11% of the recorded contributions were made by contributors who do not identify as men. This is a very small improvement compared to last year. The gender imbalance in Drupal is profound. We need to continue fostering diversity and inclusion in our community.

Two years ago I wrote a post about the privilege of free time in Open Source. It made the case that Open Source is not a meritocracy. Not everyone has equal amounts of free time to contribute. For example, research shows that women still spend more than double the time as men doing unpaid domestic work, such as housework or childcare. This makes it more difficult for women to contribute to Open Source on an unpaid, volunteer basis. Organizations capable of giving back should consider financially sponsoring individuals from underrepresented groups to contribute to Open Source.

Compared to men, women do more sponsored work, and less volunteer work. We believe this is because men have the privilege of more free time.

Free time being a privilege is just one of the reasons why Open Source projects suffer from a lack of diversity. Other reasons include hostile environments and unconscious biases. We should consider collecting data on other systemic issues beyond gender. The Drupal Association is currently working to update demographic data collected at DrupalCon, and beyond, with the goal of better understanding our community. Knowing more about these trends could help us close existing gaps.

Geographic diversity

We saw individual contributors from six continents and 117 countries. The top countries:

The top 20 countries from which contributions originate. The data is compiled by aggregating the countries of all individual contributors behind each issue. Note that the geographical location of contributors doesn't always correspond with the origin of their sponsorship. Wim Leers, for example, works from Belgium, but his funding comes from Acquia, which has the majority of its customers in North America. Wim's contributions count towards Belgium as that is his country of residence.

Europe contributes more than North America in both absolute and relative terms.

Contribution credits per capita calculated as the amount of contributions per continent divided by the population of each continent. 0.001% means that one in 100,000 people contribute to Drupal. In North America, almost 4 in 100,000 people contributed to Drupal the last year.

Asia, South America, and Africa remain big opportunities for Drupal; their combined population accounts for 6.3 billion out of 7.5 billion people in the world.

Limitations of the credit system

It is important to note a few of the current limitations of's credit system:

  • The credit system doesn't capture all code contributions. Parts of Drupal are developed on GitHub rather than Contributions on GitHub usually aren't credited on For example, Drush is maintained on GitHub instead of, and companies like Pantheon don't get credit for that work.
  • The credit system is not used by everyone. There are many ways to contribute to Drupal that are still not captured in the credit system. Technically, that work can be captured. But because using the credit system is optional, many contributors don't. For example, not all event organizers and speakers capture their work in the credit system. As a result, contributions often have incomplete or no contribution credits. Where possible, we should automatically capture credits. For example, translation efforts on are not currently captured in the credit system, but could be automatically.
  • The credit system doesn't accurately value complexity and quality. One person might have worked several weeks for just one credit, while another person might receive a credit for 10 minutes of work. Each year we see a few individuals and organizations trying to game the credit system. In this post, I used a basic weighting system based on project adoption. In future, we should consider refining that by looking at issue priority, patch size, number of reviews, etc. This could help incentivize people to work on larger and more important problems and save smaller issues such as coding standards improvements for new contributor sprints.

Because of these limitations, the actual number of contributions and contributors could be much higher than what we report.

Like Drupal itself, the credit system needs to continue to evolve. Starting this year, the Drupal Association, with the direction of the newly formed Contribution Recognition Committee, will start to evolve and leverage the credit system in new ways.


Our data confirms that Drupal is a vibrant community full of contributors who are constantly evolving and improving the software. It's amazing to see that just in the last year, Drupal welcomed more than 8,000 individual contributors and over 1,200 corporate contributors. It's especially nice to see the growing number of contributions year over year.

To grow and sustain Drupal, we should support those that contribute to Drupal and find ways to get those that are not contributing involved in our community. Improving diversity within Drupal is critical, and we should welcome any suggestions that encourage participation from a broader range of individuals and organizations.


clemens-tolboom starred aBARICHELLO/godot-ci

On github - Sun, 2020/11/08 - 10:40pm
clemens-tolboom starred aBARICHELLO/godot-ci Nov 8, 2020 aBARICHELLO/godot-ci

Docker image to export Godot Engine games. Templates for Gitlab CI and GitHub Actions to deploy to GitLab Pages/GitHub Pages/

Dockerfile 134 Updated Nov 8

Pixelite: Finding and killing anonymous sessions in Drupal

Planet Drupal - Sun, 2020/11/08 - 9:39am

Ordinarily, sessions in Drupal are created when you log into Drupal, e.g. when you want to create content, or perform some other function that requires authentication.

You can however (just like in any PHP application) start a session without first authenticating. This is known as an anonymous session.

This is almost always a poor decision, because as soon as you start a session, this generates a session cookie, and all reverse proxy caches will refuse to cache the responses from Drupal. Drupal will also add caching headers to indicate the response is not cacheable as well.

There are often better places to store state for anonymous users, e.g. the browsers localStorage, these have the advantage of not interfering with Drupal or caching.

This post will attempt to highlight some paths and avenues you can explore, the next time you come across this in an application you are working on.

Known contributed module offenders

Acquia publishes a fairly broad list of modules to which are known to break caching, some examples include

If you are looking to store state (e.g. flag, textsize) then localStorage is better suited to that. If you are doing geolocation based things, most CDNs have the ability to do this lookup for you.

If you are using these modules, use with caution, and ensure you are not breaking the caching of your entire site.

Known Drupal core offenders

If you set a message using drupal_set_message() (in Drupal 7) or \Drupal::messenger()->addStatus(); (in Drupal 8/9) this will store the message in a PHP session. What sounds like a cool idea at the time - e.g. "show a message to all users on the homepage" - will end up making the site completely un-cacheable.

This can (and has) taken down high traffic sites.

Custom code

Custom code is another place you will find code that may set anonymous sessions. Doing a quick grep will speed things up:

grep -nrI --exclude-dir=web/vendor --exclude-dir=web/core '$_SESSION' web/Check the sessions table

It is fairly easy to spot the culprit when you examine the sessions table in Drupal's database. Here is a quick query to show the current count of anonymous sessions. This number ideally should be 0 or close to it.

MySQL [example]> SELECT count(*) FROM sessions WHERE uid = 0; +----------+ | count(*) | +----------+ | 10853 | +----------+ 1 row in set (0.004 sec)

If you see you have a lot of sessions, then the next step is to read the contents of one:

MySQL [example]> SELECT SUBSTR(session, 1, 650) as '' FROM sessions WHERE uid = 0 ORDER BY timestamp DESC LIMIT 1; _symfony_flashes|a:1:{s:5:"error";a:149:{i:0;O:25:"Drupal\Core\Render\Markup":1:{s:9:" * string";s:2078:"<em class="placeholder">Notice</em>: Object of class Drupal\Core\Field\FieldItemList could not be converted to int in <em class="placeholder">example_preprocess_node()</em> (line <em class="placeholder">146</em> of <em class="placeholder">themes/example/example.theme</em>). <pre class="backtrace">example_preprocess_node(Array, &#039;node&#039;, Array) (Line: 287) Drupal\Core\Theme\ThemeManager-&gt;render(&#039;node&#039;, Array) (Line: 437) Drupal\Core\Render\Renderer-&gt;doRender(Array, ) (Line: 195) Drupal\Core\Render\Renderer-&gt;render(Array, ) (Line: 1 row in set (0.001 sec)

So now you know that there is a bug in the code example_preprocess_node() around line 146. This is the source of the messages in the first place.

After reading this great answer on stackoverflow this is likely due to the fact that the messages block is not rendered in the theme.

After checking the block layout page, the block is listed there

The Drupal core messages block attempting to render in the highlighted region.

However checking the page templates, the variable {{ page.highlighted }} was completely omitted. This was the root cause of the messages not being able to sent to the browser, and thus they keep piling up in the sessions table.

If you want to see how much data you are storing for these sessions:

MySQL [example]> SELECT uid, CONCAT(SUM(LENGTH(session)) / 1048576.0, ' MB') as size FROM sessions WHERE uid = 0 GROUP BY uid; +-----+--------------+ | uid | size | +-----+--------------+ | 0 | 2433.6637 MB | +-----+--------------+ 1 row in set (0.513 sec)

Around 2.4GB for this one site 😱. That is a lot of messages.


If you have any other tips and tricks for hunting down anonymous sessions, or even any (anonymized) war stories - please let me know in the comments.