Drupal Planet

Drupal Core News: Looking for a second Core Committer Team Facilitator

5 hours 33 minutes ago

The core committer team is looking for a new provisional committer team facilitator to help coordinate Drupal core release process, team communication, decision-making, and meetings. The committer team facilitator does not need to have technical knowledge about Drupal core.

The core team facilitator role was created in 2019. Several community members have contributed to core committer team facilitation, with Donna Benjamin (kattekrab) initially jumping in and Shannon Vettes (svettes) sharing the responsibilities. Ultimately Pamela Barone (pameeela) formally took on the role in mid-2019 and still holds it now. These contributors have helped keep our release process, communications, and team decision-making sustainable. It's been very helpful.

Now that there is more clarity around the role, we would like to bring another facilitator into the team to share the responsibilities. The person would start as a provisional core committer team facilitator alongside pameeela. The provisional phase of a maintainer role allows an interested contributor to see if the role works for them and the team. The needed time commitment is about 10-15 hours per month.

If you are interested, read more about the role responsibilities, and get in touch with the team!

BADCamp News: What's next for San Francisco Drupal Users Group?

7 hours 33 minutes ago
What's next for San Francisco Drupal Users Group? Thu, 08/05/2021 - 12:00 volkswagenchick Thu, 08/05/2021 - 08:21 While BADCamp may be taking a hiatus for 2021, San Francisco Drupal User’s Group continues to be in full swing providing the quality content we all love and expect from our Drupal community and beyond. Here’s what’s coming up at SFDUG... Drupal Planet

Drupal core announcements: Looking for a second Core Committer Team Facilitator

9 hours 2 minutes ago

The core committer team is looking for a new provisional committer team facilitator to help coordinate Drupal core release process, team communication, decision-making, and meetings. The committer team facilitator does not need to have technical knowledge about Drupal core.

The core team facilitator role was created in 2019. Several community members have contributed to core committer team facilitation, with Donna Benjamin (kattekrab) initially jumping in and Shannon Vettes (svettes) sharing the responsibilities. Ultimately Pamela Barone (pameeela) formally took on the role in mid-2019 and still holds it now. These contributors have helped keep our release process, communications, and team decision-making sustainable. It's been very helpful.

Now that there is more clarity around the role, we would like to bring another facilitator into the team to share the responsibilities. The person would start as a provisional core committer team facilitator alongside pameeela. The provisional phase of a maintainer role allows an interested contributor to see if the role works for them and the team. The needed time commitment is about 10-15 hours per month.

If you are interested, read more about the role responsibilities, and get in touch with the team!

OpenSense Labs: Drupal Multisite Guide: Less Work, More Output

1 day 7 hours ago
Drupal Multisite Guide: Less Work, More Output Gurpreet Kaur Wed, 08/04/2021 - 20:54

Have you ever heard that a single business has a lot of different branches or mini-businesses? It’s pretty common in the day and age we live in. The business world has grown immensely and so have its needs. And a single website isn’t enough to fulfil those needs.

So, what do businesses do? They build multiple websites, which should have been a great solution, but is really more of a stressful trigger waiting to go off. This is because managing those multiple websites is a pain, for lack of a better word. It results in slower building process, increased overheads, lack of control and scarce visibility, so yeah, a pain describes it pretty well.

What is the solution then?

A multisite structure that allows you to create multiple websites using a commonality. It would require less work to build, yet provide the much needed autonomy for the individual sites on the setup. And that is what we are going to be discussing today, but in regards to Drupal.

Drupal, being a popular CMS, has a lot to offer, when web development is considered. The sites developed using Drupal are versatile, scalable and provide amazingly powerful digital experiences. And one such feature that contributes to that power is the Drupal multisite setup. So, for whoever asked, ‘Does Drupal support multisite?’, the answer is yes and it does so exceptionally well. Let’s find out how. 

Drupal Multisite: What is the setup about?

Have you ever baked a cake? The core ingredients being flour, eggs and sugar are all the same for every cake. It's just the flavour and the toppings that are different. Drupal multisite can be understood with the same analogy.

As the name suggests, you can have multiple websites, tens and hundreds of them, working for you with ease using the multisite feature. You can have Drupal multisite with different domains as many as you want.

What is going to be the same for every website in this setup? 

The codebase would remain constant throughout. You can have hundreds of sites without having to rewrite it. The Drupal core and the available modules and themes are also shared by the multiple websites. These form the flour, eggs and sugar batter in the Drupal cake.

And what is going to be different in the multiple sites?

Everything other than the codebase is different. You would have independently running websites that would serve the needs of its target demographic.

The sites would have their own database;
The sites would have their own configuration, in terms of enabled modules and themes, content and more; 
The sites would have their own files, inclusive of images, uploads, user profiles and more; 
And the sites would even have their own base domain or URL. 

So, in essence Drupal multisite would provide you the opportunity to create multiple websites using the same codebase, however, all the sites would be different from one another, serving different audiences. 

How is that possible?

Because of server requests. Let me clarify it a bit. All of the multi sites created using this setup are stored in separate folders. Drupal multi folder structure can be separated from multisite repositories, making deployments easy for site maintainers and front-end developers alike. On top of this, each of these folders would have its own personal php file with connectivity to its own personal database.

Now, add to this equation, Drupal’s fine ability to map a request based on the domain it came from, this ability is further enhanced by loading the right database and configuration based on the said domain. The result is the website that the requester wanted being served on a platter. Pretty cool, isn’t it?

What do you gain out of it?

After understanding the basic concept and working of Drupal multisite module, the next thing that pops up in our minds is its benefits. Why should you take it up? What’s to gain out of it? And that is where I come to tell you all about the amazingness that is Drupal multisite.

Benefit from faster launches 

The best part of Drupal’s multisite feature is its ability to create newer websites in a matter of minutes and without much support from IT and developers. 

The built-in installation profiles are the reason for the faster launches. It essentially holds the functionality and configuration into installable packages, which can be launched as many times as you want them to. And you would have a new website that’s fully ready for the content entries. 

Benefit from saying no to compromises 

The second multisite benefit comes in the footsteps of the first. Because multisite helps in creating faster launches, it allows you to not compromise when deadlines are looming.

For every project, there is a deadline that needs to be met and as this deadline starts to come closer, potentially lucrative features start to move farther and out the door. Developers start making compromises and technical debt starts to build up.
Now, you could let a feature or two go out the window in a single build, however, when there are close to a hundred websites in development, that thought won’t even cross your mind. It is suffice to say that multisite architecture boasts a higher quality standard and minimal technical debt. The primary reason for that is time, creating multiple systems at once gives you ample time to think about potential and the time to make them part of the project in reality.

You create long term solutions with a multisite setup that come with a higher refactoring potential from the management because there are multiple sites involved. 

Benefit from lower maintenance and reduced costs 

Another advantage of a single code for multiple websites is that you have to spend less time on maintaining it as compared to multiple codebases for multiple websites. Wouldn’t you agree? 

If you encounter a bug on any one of these sites, you would fix it for all of them. This considerably reduces the time spent on maintenance and consequently the costs that accompany it. With Drupal multisite, you can keep track of updating and reviewing at one place, thereby, keeping a convenient grip on maintenance.

Benefit from saving your efforts 

I saved the best for last; with Drupal multisite, you actually save yourself a lot of time and effort because you can reuse your code or components of it. You would only have to build a feature once and thereon, you’d only have re-use, no wasted effort for building the same thing over again.

A reusable code with a shared library entails; 

Reusable integrations; 
Reusable functionality; 
Reusable UI components; 
Reusable workflows; 

And you can also reuse a theme with Drupal’s theme inheritance mechanism, allowing you to create a base theme for other themes to inherit the basics from. 

All of this saves a ton of effort in the development process. You should know that you can also try to reuse components for sites not on the same platform, it would be extremely difficult, but possible.

What options does Drupal multisite offer?

While setting up for Drupal 9 multisite, there are a few choices available. The essence in all of these choices is the same, which is a strong commonality through a single codebase. Moreover, you will get all the benefits we just talked about in the previous section in all of them.

So, let’s understand the kind of range Drupal multisite comes with.

Conventional approach: Classic Drupal multisite architecture

The conventional approach essentially sums up the meaning of Drupal multisite, as we talked about while understanding the concept. There would be multiple sites in this option, with multiple configurations and multiple databases, however, there would only be one codebase shared amongst all. The diagram below describes the architecture pretty aptly.

I would be wrong, if I said that it's only the codebase that is shared. Technically, out-of-the-box that is the case. However, if you want your multisites to share more than that, you have an option. The Features module, a unique trait of the conventional architecture in Drupal, can help you in that. It allows sites to have shared features by importing the configuration from it. Config Split further eases the workload by segregating which configuration needs to be shared and which needs to be quashed.

Contrastingly, I have mentioned that you can create independent and somewhat unique websites using Drupal multisite, if that is what you wish for. This is possible because it allows you to customise because of isolated configurations. As such you can create your own custom themes and modules for each of your websites.

Multi-domain architecture

The multi-domain architecture isn’t all that different from the multisite. There is a single codebase, however, along with that there is also a single and shared database, which isn’t the case in multisite. Here is a diagram for better understanding.

Through the multi-domain architecture, you’ll be maintaining a single Drupal installation, which is quite easy; on top of this, you will also be able to maintain the configuration and functionality with ease. 

The Domain Access modules are at the heart of this architecture, as it makes it possible to serve multiple sites. It also allows you to categorise your content as shared and unique, you can decide a specific piece of content for one particular domain, then you can also share it across all sites, if that is what you want.

With more sharing in this architectural design of Drupal in terms of features, functionality, content and even users, updating a single site is a walk in the park. 

In terms of the drawbacks, the one that outshines the rest is that you can’t have any exceptions. In multisite, you could add additional functionality to individual websites, but you can’t do it here. Well, you can, if you wanted to, but you see, the intention behind multi-domain architecture is simplicity. And adding exceptions to each site would contradict that big time. Even while using contrib modules you would have to be extra careful in checking their compatibility with Domain Access.

Other notable architectures

There are three other multiple site architectures in Drupal, let’s shed some light on these as well.

Based on Drupal distribution

Have you ever bought a cake mix? It's a ready-made mixture of everything that goes into the cake and all you have to do is make it into a batter and put it in the oven and you’ll have your very own baked cake. Easy, isn’t it? This is basically what a Drupal distribution is. 

You get a mix of everything you would need to start your web projects, from the required modules and libraries to custom themes and modules and from the configuration to possibly the default content. It’s a website starter pack. There are popular Drupal distributions to choose from, like Commerce Kickstart and Lightning, but you can also make your own custom distributions. Take a look at this complete list of major Drupal distributions that you must try out.

The way these are different from multisite and multi-domain is through the codebase, each site would have its own and each site would also have its own hosting account.

The major drawback here is that it requires extra work. It’s kind of ironic for a cake mix, I know. You would have to maintain the distribution codebase as well as each of the sites. Security updates and bug fixes need all the more attention, if your distribution is published on Drupal.org.

Based on data silos

A multisite architecture on data silos is similar to Drupal distributions, in the sense that the codebase is different for each site, providing greater autonomy and better security. For businesses with multiple branches and departments that seek decentralization, yet a kind of uniformity, this is a great choice. 

Based on multilingual needs

This one has a similarity to the multi-domain architecture, as there is a shared codebase and database. It allows sites to capitalise on language-based regional targeting. With less development efforts and less building costs, each site would have its own language and its own regional audience. Learn more about why Drupal is great for multilingual sites here.

When can you optimise the setup the most?

Now comes the part of knowing exactly when to optimise Drupal’s multisite architecture. There are particular use cases and considerations that make the setup an ideal choice, let’s understand them.

Do you have multiple sites?

As the name suggests, for Drupal multisite to work its charm, you have to have multiple sites as in two or more. The prime reason for this setup’s mere existence is to help you in saving time and effort in the management of multiple Drupal sites by making them run on the same Drupal core.

Think about it, if you have two or more sites not running on this setup, you’d be responsible for each code individually and it would differ drastically for each site. This difference can become a mammoth task for managing, so doesn’t choosing multisite and eliminating this worry sound like the better choice?

Are they similar to each other?

Now, you could have multiple websites, but they have to have a degree of similarity in order for the multisite setup to work. Dramatically different sites in terms of features and aesthetics are not ideal for this architecture. That’s not to say that each site has to be a clone of the next. No, every site would obviously have its own content, moreover, it could also have different functionality, but that difference cannot be dramatic, just a feature here and there.

Take a university for instance, it could need multiple sites for its varying departments. Now in this case, the university could opt for the multisite feature because despite different websites, it would most definitely maintain a sense of uniformity in them. 

In essence, Drupal multisite creates replica sites with different themes for each site, if that aligns with your requirements, you should definitely opt for it.

Do you have the technical infrastructure?

Drupal multisite is meant to make your job easy, but it can only do so if you have the right technological infrastructure and expertise to handle that. 

  • The right hosting environment to manage multiple domains and deployment mechanisms. Your hosting provider should be proficient in knowing the exact requirements of your setup.
  • The right DevOps processes that are compatible with your multisite setup. When it's said that multisite setup makes you work less, automated deployment is one reason for that, so, your DevOps need to be efficient at that. 
  • Finally, the right testing environment because you deploy multiple sites at once, the chances of errors are on the higher side. A break in functionality can become colossal and checking for it manually is hard work. So, an automated testing environment that is equipped with tools to ensure higher quality standards is crucial.
Can going multisite pose challenges?

There is always a darker side of things, and Drupal multisite is no exception to that. There are certain drawbacks that accompany the setup that can leave a sour taste in our mouth. For many, these challenges have become the reason for not opting for the multisite architecture. 

The challenge of failure 

The frontrunner in the list of multisite challenges has to be its chances of failure, which to be honest are fairly high. There are two reasons for this.

One is the fact that there is a single codebase for all the sites. This means if there is a problem with one, there is a problem with all of them. Take traffic spikes for instance, they might be great for one website, but for multisites, that one site can pose significant risks to the others.

Second is the failure due to human error, which cannot be foreseen or avoided. There is plenty of risk associated with updating a single site, imagine the level of risk when there are tens of sites. A single syntax error can become the reason for the demise of your multisite setup quite quickly.

The challenge of individuality and innovation 

Yes, we do say that the multisite feature has room for individuality for each site. And then we also say that each site has to be the same or at least similar to a great extent in order for the architecture to work. Do you see where I am going with this challenge? 

The innovative flair often seen in development is somewhat lost in the multisite setup. Why? Simply because there is a standard to be adhered to. And when you deviate from that standard, you set yourself on the path of losing all the benefits of this architecture.

Reusing components, without extra efforts, is one of the fortes of the multisite setup, and adding innovation into this mix would make it tedious and exhausting. That is why it is advisable to avoid the multisite, if your sites differ from each other in terms of features and functionality or even if you would want them to differ in the near future.

The challenge of technical insufficiencies 

I mentioned in the previous section that optimising Drupal multisite is going to serve you best, if you have the technical infrastructure for it. And this can become somewhat of a challenge, I’ll tell you why.

Compare building one site or multiple sites separately to building and maintaining a multisite installation. Now tell me, which do you think would require more technical expertise? The latter, I’m sure. The reason is the complexity of the comprehensive web of multiple sites, the amount of settings alone could give a newbie developer a headache. 

So, along with the technical infrastructure, including a suitable host, DevOps and testing system, the need for a skilled multi-site development team can become quite a challenge.

The challenge of losing open source 

Finally, the last challenge relates to the loss of Drupal functionality. With a multisite architecture, you become an SaaS provider and consequently part with a number of open source solutions. You become responsible for every feature that needs improvement or innovation, unlike the usual way of open source software, wherein the community plays a part in innovation.

Learn more about open source here:


I would say that the challenges that the multisite architecture comes with do make you rethink choosing this path. However, when you consider the benefits along with its use cases, there isn’t a more perfect solution. 

A university site would not need to add extra innovative features to one of its department’s sites and therefore, the multisite is best suited for it and for other enterprises that have similar needs. Provided that you check all the right boxes in terms of multisite’s optimisation, you’ll not regret choosing it.

blog banner blog image Drupal 9 Drupal multisite architecture Drupal development Drupal distributions Blog Type Articles Is it a good read ? Off

Palantir: Drupal 8 End-of-Life and Drupal Rector

1 day 10 hours ago

Project managers: now is the time to upgrade your site to Drupal 9

Drupal 8 will reach its end-of-life on November 2, 2021, before the release of Drupal 9.3.0, due to Symfony 3's end-of-life. If you are Using Drupal 8, you must upgrade to Drupal 9.2 to keep your site secure. 

What this means: that all of your contributed modules and custom code need to be Drupal 9 compatible in order for you to make the update. While most of your code from Drupal 8 will still work, functions, classes, and methods that have been deprecated must be updated. For more information, here's the Drupal deprecation policy

Fortunately, the most common deprecations can be updated automatically via Drupal.org's "project update bot" or by using Drupal Rector, a tool that's designed to help automate Drupal code updates. 


Image: Status of the most common code deprecations, as compiled by Acquia

These automated tools can correct a majority of PHP code issues associated with the upgrade to Drupal 9. 

While most of the information to date about using Drupal Rector has been written from a developer perspective, in this post, we'll put on our project (or product) manager hats and see what it means for your project. 

First, let's set a common scenario:

  • As a project manager, you are responsible for scheduling maintenance and upgrades to your portfolio of Drupal sites and applications
  • Drupal 8 end-of-life is set for 2 November 2021
  • Moving to Drupal 8 compatibility as soon as possible guarantees the best return on your investment in the platform



With these factors in mind, what does Rector mean for your project? Let's take a look:

  • Rector is a set of tools for automatically updating the PHP code that runs your Drupal site, and is specifically targeted at Drupal 9 compatibility
  • Your development or support team can use Drupal Rector to help prepare your site for Drupal 9 (and, as of this writing, Drupal 10!)
  • Your team can contribute to the health and stability of the Drupal project by contributing to Drupal Rector

What might a project plan look like? First, look at the resources you have. If you have developers, they can take one or more of the following steps:

  • Create new Rector rules for use by all Drupal developers
  • Use Drupal Check or Upgrade Status to get a list of deprecations in your current code
  • Use Drupal Rector to apply updates to your custom code
    • Drupal Rector can generate code updates for your custom project code, saving developer time. While not all issues can be fixed automatically, more than half of modules tested can be fixed simply with Rector

At Palantir, we have focused on Step 1 in order to enable our Managed Support team to perform Steps 2 and 3. We work in Kanban sprints with a small team, and we have seen measurable progress in as little as a week.

Taking such a proactive approach as a project manager is a great way to ensure continued project success. As Drupal 8 will likely no longer receive community support after Q4 2021, taking proactive steps to support Drupal 9 now will save your organization time and money in the future. It is also a great opportunity to contribute to the Drupal project and get organizational credit for doing so.


Photo credit: Carl Heyerdahl on Unsplash

Development Drupal Open Source Project Management Support

Community posts: Drupal Community Update - August 2021

1 day 12 hours ago

This month, we spoke with:

  • Discover Drupal Initiative, by Angie Sabin
  • Drupal Community Working Group, by Mike Anello
  • Drupal Swag Shop Working Group, by Will Huggins
  • Contribution Mentoring, by Rachel Lawson
  • Automated Updates Initiative, by Tim Lehnen
  • Local Drupal Associations, by Leslie Glynn

Each of these groups represents ways to contribute to the Drupal project. How can you help?

Discover Drupal Initiative, by Angie Sabin What have been your priorities in the last three months?

The Discover Drupal classes just started in July. The past three months included getting students onboarded making sure they received the proper equipment and Drupalize.me account. We also set up the Slack channel for students and mentors and onboarded all of the mentors.

And what has been your greatest success in the last three months?

We are thrilled that we have 23 mentors from around the globe! This ensures that no matter the time of day, someone is always available to help our students with any questions they may have.

What has been your greatest challenge in the last three months?

Making sure that all of the equipment was functional and shipped to the right places in time for class. A HUGE thank you to our volunteer, Megh Plunkett at Lullabot for configuring all of the laptops and getting them shipped to the students on time.

Do you have a "call to action" you want to make to the Drupal Community?

We still have room for sponsors for this year! Sponsorship helps cover costs such as paying to bring our students to DrupalCon 2022 and the cost of student training. Our sponsors will have direct access to the students for recruitment toward the end of the program year.

Drupal Community Working Group, by Mike Anello What have been your priorities in the last three months?

We participated in an episode of Talking Drupal (https://talkingdrupal.com/302), we have started an "Open Source Community Health Discussions" group with other open source communities (having monthly calls), we have been on-boarding a new member of the Conflict Resolution Team.

And what has been your greatest success in the last three months?

(Hoping this is published after August 3) We have been working with the Community Health Team, the Drupal Association, and the Event Organizers Working Group on best practices (including a playbook) for accessibility at Drupal events.

What has been your greatest challenge in the last three months?

The mediation tasks of the conflict resolution team.

Do you have a "call to action" you want to make to the Drupal Community?

Nudges! https://www.drupal.org/node/3193832

Drupal Swag Shop Working Group, by Will Huggins What have been your priorities in the last three months?

Following a successful DrupalCon North America in April we have been working on reviewing the products that sold best (stickers, T-shirts and Hoodies) so we can prepare for DrupalCon Europe in October.

And what has been your greatest success in the last three months?

Generating over $300 for Drupal Association. It may not be huge but it is totally incremental revenue and also helps to promote Drupal (I often get asked 'so what is Drupal?' when I am wearing my swag).

What has been your greatest challenge in the last three months?

As with all community-run initiatives, finding the time to focus on growing the swag shop is a challenge and we are always on the lookout for more volunteers. With more help, we want to focus on our next biggest challenge, which is the marketing and promotion of the swag shop.

Do you have a "call to action" you want to make to the Drupal Community?

The Drupal Swag Shop is a great way of contributing to Drupal for 'non developers' - the skills we need in the working group are marketing, project management, and design, so if you want to contribute to our brilliant community, but are not sure how... get in touch!

Contribution Mentoring, by Rachel Lawson What have been your priorities in the last three months?

Preparing for DrupalCon Europe, by creating and organizing the first-ever Drupal Contributor Mentor Summit (https://www.drupal.org/community/events/contribution-mentor-summit-2021-...).
The Mentor Summit will allow us to invite those already contributing to Drupal to learn about how they can pass on their skills to an even wider group of people so we can grow our contribution community and make a better Drupal.

And what has been your greatest success in the last three months?

Getting the Mentor Summit organized and in the calendar before DrupalCon Europe.

What has been your greatest challenge in the last three months?

Lots of people with large workloads because lots of clients want Drupal projects means little time to work on things like the Mentor Summit! While it is good that Drupal skills are in high demand, it’s important to also advocate for and emphasize the need to continue to grow Drupal as the premier CMS and supportive open source community.

Do you have a "call to action" you want to make to the Drupal Community?

If you are a contributor to the Drupal Project, as a developer, designer, documenter, project manager or marketer, please put the 17th September aside in your diary so you can join us virtually at the Contributor Mentor Summit!
Please register/login and "join the group" at https://drupalcontributions.opensocial.site/group/contribution-mentor-summit-2021/about and we will keep you up to date via email as the schedule is announced at the end of August.

Automatic Updates Initiative, Tim Lehnen What have been your priorities in the last three months?

The PHP implementation of the TUF client - PHPTUF - is essentially complete, or near enough to it. This means that the team is shifting work to the automatic updates contrib module to actual integrate this library into Drupal's Automatic Update system prototype.

Major progress has been made on actually executing the composer-based updates in an automated way as well, with work from @effulgentsia @traviscarden @tedbow and others. More recently we've been trying to complete the test coverage of this critical component of the system.

Finally, the Drupal Association has been reviewing responses to our request for proposals to help implement the server side of the TUF specification, so that Drupal.org can sign and maintain the packages we deliver.

And what has been your greatest success in the last three months?

Effective completion of the PHPTUF library is a huge milestone, and the ability to focus fire on the problem of ensuring that automated composer updating works well and has good test coverage is a crucial next step.

What has been your greatest challenge in the last three months?

We've really had two major challenges:

  1. Though we are attempting to expand our resources via the Drupal Association RFP for an external vendor to help us build out the TUF server-side signing component - it has been difficult to find a partner - as the whole Drupal ecosystem is extremely busy in this period. (A good thing, in the end!)
  2. We have to make a decision about whether we are willing to release an Alpha version, even in contrib, without the signing in place, in order to validate the user experience, workflows and do real user testing of the system - rather than block that on the signing being complete.
Do you have a "call to action" you want to make to the Drupal Community?

You can chime in on the issue about releasing an alpha version without package signing here: #3220205: Proposal: As pathway to Drupal core use new 2.x.x branch for Composer Based Updates

Local Drupal Associations, by Leslie Glynn What have been your priorities in the last three months?

The local associations have been working with the DrupalCon Europe 2021 team over the past few months to identify camps that would be willing to host their camp online in conjunction with DrupalCon Europe 4-7 OCTOBER 2021.

And what has been your greatest success in the last three months?

DrupalCon Europe 2021 announced that it is collaborating with several Drupal Camps to create a unique "Drupal Eurovision" experience. The goal is to create an experience to continue Drupal’s 20th birthday celebration.

The following camps and communities have agreed to have their event at DrupalCon Europe:

  • Drupaljam, The Netherlands
  • Drupal Mountain Camp Switzerland
  • Drupal Germany
  • DrupalCamp Kyiv
  • DrupalCamp Finland
  • Drupalcamp Belgium - Ghent 2021

Camps have an opportunity to have their own virtual space to run their own virtual event as part of DrupalCon Europe 2021.

A Drupal Slack channel was created for discussion at #dceur2021-camps or direct link: https://drupal.slack.com/archives/C02067Z7ESH

What has been your greatest challenge in the last three months?

In general Drupal Camps around the world are being impacted by dwindling participation at virtual events.

The global coronavirus situation continues to make it difficult for Local Associations around the world to plan events for the coming year. While things were looking better for a bit, countries around the globe are once again seeing increasing rates of infection. Global travel also continues to be restricted.

Do you have a "call to action" you want to make to the Drupal Community?

The DrupalCon Europe team and the Local Associations that will be holding their camps during the event have been working hard to create an engaging virtual event. Help them out by purchasing a ticket to the combined event. One ticket gives you access to DrupalCon plus all the local camps being held online during DrupalCon Europe 2021 on 4-7 OCTOBER 2021. Register at https://events.drupal.org/europe2021/registration-information

Droptica: Connecting Drupal and Bootstrap

1 day 12 hours ago

It isn’t enough for the architecture of our web page to be well-designed – the appearance is also important! Drupal comes to our aid when it comes to building websites quickly. Can we count on similar help when creating a modern look? We'll tell you a bit about the extensive library called Bootstrap, which offers a wide range of ready-made components.


The year was 2011, when a group of Twitter programmers, headed by Mark Otto and Jacob Thornton, introduced the world to an extraordinary tool that was to revolutionize in the future the process of creating a graphical interface – not only for websites but also for applications. They named it Bootstrap and decided to release it under one of the most liberal open source licenses – MIT. Currently, the latest version of Bootstrap is 4.6, but it looks like we can soon expect a stable 5.0 version (as of today it's version 5 Beta 2).

Source: Bootstrap

Bootstrap is a library of cascading style sheets (CSS), which uses ready-made HTML and JavaScript solutions. It provides predefined styles for the commonly used elements on web pages, such as text, headings, buttons, navigations, tables, links, and more. It also ensures that the elements look good in the mobile version. Everything is based on a grid structure made of up to 12 columns. The thing that makes Bootstrap so popular – in addition to the obvious benefit of having hundreds of predefined classes, so we don't have to worry about spacing and struggle with the composition of our divs – is its documentation. It's impossible to get lost in it. In terms of topics, it covers styling support and its variants for all elements.

Drupal and Bootstrap - best friends

The Drupal community didn't pass by indifferently such a widely used tool and created two themes that allow integrating the Bootstrap library with Drupal.

Bootstrap theme

The basic theme that allows you to use the power of Bootstrap in Drupal can be downloaded from the Drupal.org page. It's worth mentioning, however, that it currently supports the library version 3, but is compatible with all Drupal versions from 7 and up.

Installing the theme can be done using the command line in composer:

require 'drupal/bootstrap:^3.23'

or the admin panel under the path /admin/theme/install.


The next step is enabling the theme in the Appearance section of the admin panel or using the drush command.

theme:enable bootstrap

 (if we just want to enable the theme)

config-set system.theme default bootstrap

(if we want to enable the theme and set it as default)


This ready-made theme has many options for global configuration of individual components that make up our page – both static (forms, tables, containers) and dynamic (modal windows and pop-ups). You just need to go deeper into the settings under /admin/appearance/settings/bootstrap. We can already notice a significant difference in the appearance of our page.

Below you'll find the comparison of my test homepage. If you use the Bartik theme, you'll get the impression that suddenly the page components are mixed up and the whole thing looks "broken", but don't worry. In most cases you just need to slightly adjust the styling of the existing elements. Go to Structure -> Block layout and assign the correct regions to the blocks. Here I present the look of the Bartik theme after it's been adjusted accordingly.

Barrio theme

The process of installing and enabling the Barrio theme is the same as before. The main difference between Barrio and Bootstrap is the version of the library they use. For Barrio it's Bootstrap 4 or even 5 (for those who'd like to test version 5.0.2 of Bootstrap). The command to download Barrio via Composer looks like this:

require drupal/bootstrap_barrio

What we get in both cases are more ready-made templates that require further configuration and styling according to our needs, rather than a full, styled solution. They should be treated as the base themes which we'll inherit from in our sub-theme. This is also important in terms of future updates.

Creating own theme

Creating our own theme, which'll be based on the Bootstrap library version 3, 4 or 5, can be carried out in two ways:

  1. by using the starter kit available for both themes – under themes/Bootstrap/starterkits and themes/bootstrap_barrio/subtheme (the fastest and easiest option) respectively.
  2. using the starter kit available with both themes, but without using CDN (Content Delivery Network) (advanced option, requires a CSS preprocessor, e.g. SASS, to compile styles, and the Bootstrap library must be downloaded locally).

The first option only requires us to copy a ready set of files to a new folder in the themes path and rename the files from THEMENAME or bootstrap_barrio_subtheme to the machine name of our theme. You should also check the .theme, info.yml, schema.yml, color/color.inc and js/global.js files and make similar changes within them as well. Thanks to CDN, the Bootstrap library doesn't have to be downloaded locally.

From now on, we can start working on the appearance of our page, define the typography or colour scheme. In the theme settings, you'll find many options to modify the original configuration without having to modify the css or sass files. However, in most cases it turns out to be not enough and it's necessary to overwrite files and create templates in the .twig format.

Droopler – a high-end Bootstrap template

As a free Drupal distribution, Droopler was created with the idea of fast and comprehensive website creation in mind. Therefore, it contains a set of ready-made components and functionalities that most pages use and – thanks to its modular structure – has a highly configurable SCSS preprocessor. To perform the rest of our activities, you can install Droopler in the way described on the linked page.

Bootstrap is an integral part of Droopler. The Droopler theme uses Barrio – but unlike Barrio it provides a ready-made theme with styles, not just a template. In the scss folder, we can find ready-made style files for all components (mainly the available paragraph types, forms, etc.) and page structure elements (headers, footer, etc.).

Droopler subtheme – how to use it?

The Droopler theme also has a starter kit for creating your own sub-theme named STARTERKIT_CSS and STARTERKIT_SCSS, where we can easily modify the predefined variables. Let's check what it looks like when you want to use SCSS:


The style.css file combines the entire SCSS code from the main droopler_theme and our theme (files located in scss/config). Print.scss also combines the entire SCSS code for printing both themes. In the libraries subfolder, we can put our additional SCSS files, which we then have to add via @import in the style.scss file. When adding them, it's worth keeping the division into components and layout – as in the base theme.

You can make any changes to the settings of the Bootstrap library itself or the droopler_bootstrap base theme in the configuration files:

  • _base_theme_overrides.scss
  • _bootstrap_overrides.scss.

In the case of both files, we have at our disposal a quick guide covering the available variable modification options in the form of an extensive comment. All we need to do is uncomment the selected variable and substitute it with our value. The complete list of variables used in Bootstrap that we can overwrite can be found in the library's _variables.scss file. As it's downloaded automatically by defining the repository in the droopler_theme theme's package.json file, it can be found in the node_modules/bootstrap folder.

Suppose we want to change the colour of the submenu border that appears under the $dropdown-border-color variable in Bootstrap. In the base_theme_overrides file, we define a new colour, for example $color-example-1. Then, in the bootstrap_overrides file, we uncomment line 34, where the value for the border colour is defined. We substitute it with our newly created variable there.


You must run the compiler for the changes to become visible. In the case of Droopler, the developers also took care of it. There is a ready-made gulpfile.js file in the theme package. We just need to run the gulp watch command in the theme's directory (both droopler_theme and droopler_subtheme), so that any changes we make to scss, js or other source files are included and compiled automatically. The effect? Let's find out!


Our border is now pink. We can do the same for all variables.


Bootstrap is a powerful tool connecting graphic designers and developers. On the one hand, it allows designers to familiarize themselves with the website's architecture and the specialized terminology (e.g. a 2 column-wide sidebar instead of a narrow window that is glued to the edge of the page), on the other – it saves time of the developers who only need to use the correct class to transform a regular link into a button.

Integrating Drupal with Bootstrap may seem relatively complicated, but remember that the available Bootstrap and Barrio themes are only templates, and in the end we'll still have to assign appropriate classes for all types of links we use. In Droopler, this part is already taken care of – we only need to change the block layout or modify the existing Twig templates. We can create and implement a new colour scheme in a few moments by editing a single file – the effect is guaranteed.

Nuvole: Changes coming to Config Split

1 day 14 hours ago
Help to decide the direction of Config Split

Config Split has worked mostly the same way as it did when the first beta release was tagged in 2016. The 8.x-1.x branch is using Config Filter as the API to hook into the configuration management of Drupal. But since Drupal 8.8 we have a much better API in Drupal core which allows us to do more complex things with simpler code than the Config Filter API did. The core API was designed with the lessons learned from Config Filter in mind after all.

Config Split 2.0.0-beta2 already uses the core API, but it still does the same thing as Config Split 1.x. I think now would be a great time to change things up a bit and do the things that were too hard to do before.

But first let's revisit what Config Split does.

On export these two things happen:
Complete Split: Modules and config and all the config that depends on it is split off into the split storage and removed from the sync storage when the export is complete.
Conditional Split: The config is compared against the sync storage and is split to the split storage if it differs, the original config in the sync storage remains.

On import the config from the split storage is merged before Drupal imports the config from the sync storage.

Now what do I propose 2.x should do?

On export these very similar but different things happen:
Complete Split: Modules and config are removed from the sync storage as if it had been uninstalled. The difference of how other config (which no longer depends on the modules) changes is kept as a quasi-config-patch* together with the config of the split modules in the split storage.
Partial Split: Config is compared against the sync storage but instead of splitting the whole config to the split storage only the difference is kept in the split storage as a quasi-config-patch*.

On import the config from the split storage is merged and the quasi-patches applied before Drupal imports the config from the sync storage.

What now?

I think these changes make sense and make Config Split a better module. But the behavior is quite different, so if you have gotten accustomed to the stability of Config Split and depend on some specific way it works then this could be upsetting. And right now there is still a way to have the cake and eat it too: We keep 2.x the way it is now (in beta2) and maintain the behavior and only add "non-breaking" changes and do what I proposed in 3.x. Here is the catch though: I am not interested in supporting two branches, especially if I don't know that it is useful to anyone.

Please let me know what you think about this in a comment on the issue on drupal.org.

* What is a "quasi-patch" or a config patch?

The word quasi-patch was already introduced to the drupal world #3055872. But what I have in mind is a bit different. I think it will be easiest to explain with an example:
Imagine you install the demo Umami profile and then uninstall the Menu UI module. The recipe node type will be updated to have the third party configuration removed. A patch for the exported config file would look like this:

diff --git a/node.type.recipe.yml b/node.type.recipe.yml
index 974c2ce..8d0de1f 100644
--- a/node.type.recipe.yml
+++ b/node.type.recipe.yml
@@ -1,13 +1,6 @@
uuid: 40b74b76-6f31-4999-87bb-9700b85d43a6
langcode: en
status: true
-  module:
-    - menu_ui
-  menu_ui:
-    available_menus: {  }
-    parent: ''
   default_config_hash: '-3P1yuM15pcimXHBBhevjW-4aqojpmZbUgAqlVIeweo'
name: Recipe

The quasi-patch or config patch would be a file called config_split.partial.node.type.recipe.yml with the content:

added: {  }
      - menu_ui
      available_menus: {  }
      parent: ''

Disclaimer: The details about this are subject to change. There are likely some compromises we need to make.

Tags: Drupal PlanetConfiguration Management

Ben's SEO Blog: The Search 404 Module

2 days 5 hours ago
The Search 404 Module Don't just show a 404 page for content that has been removed or URLs that are malformed: show visitors relevant pages on your site based upon a search for the original page path. Tracy Cooper Tue, 08/03/2021 - 12:27

Tag1 Consulting: Funding your open source projects - a talk with Matt Glaman

2 days 8 hours ago

It’s no surprise to anyone in the open source software world, or any business, that funding is the center of how things get done. While some parts of projects are funded by their foundations (when these exist), most projects are maintained by independent developers or teams working in their spare time. In this Tag1 Team Talk, Managing Director Michael Meyers is joined by Matt Glaman, maintainer of Drupal-check. Drupal-check, based on PHPstan, is a static analysis tool for checking Drupal code for bugs and deprecations.

Read more [email protected]… Tue, 08/03/2021 - 07:05

OpenSense Labs: Why is Drupal CMS the first choice for Government sites?

2 days 9 hours ago
Why is Drupal CMS the first choice for Government sites? Maitreayee Bora Tue, 08/03/2021 - 19:16

In today’s modern times, the best way to connect with each other is through technology. Talking about connection, the very first thing which comes to our mind is connecting to our family and friends. The necessity of technology can be well understood if you stay away from family or friends and want to connect them instantly. So, by talking about the basic ideology of technology, what I wanted to portray is the effect of digital transformation in our lives. Now when it comes to communicating with the government, what is the most convenient way to do so? Yes, you got it right. It’s through technology again. As we know that the government’s main objective is to meet the needs of its citizens. Therefore, the best way to reach out to the citizens and provide them the necessary help is through digital services. In this article, I will tell you about the reasons why Drupal is the first choice of government when it comes to providing world class digital services. 

Significance of digital transformation for a government

When we talk about digital transformation, it's not only about new technologies but it comprises a vast subject matter like mindset, culture, work process and organizational structure. These are the areas which need to be given emphasis along with the digital technology adaptation. 

This section will provide you with information about what exact digital technologies the government adopts to deliver services more efficiently and effectively to its citizens. You will also get an overview of how digital transformation has brought a positive impact in the overall digital services leading to better outcomes for its people. 

Facilitating good customer experience

Today every citizen looks for public services to be customized and approachable as the services like that of the private sector. So, the government has to plan for some ways to deal with this expectation of the people. There is a need to create a customer centric mindset where they look for improving service quality, strengthen the level of public trust in the government and promote transparent interaction leading to better customer experience. 

Social media and mobile services like applications and SMS that are replacing the traditional channels, enable users to get access to the government services they require in the most suitable way. Such platforms can be a good medium of communication between people and the government, where everyone can report their concerns and also provide the necessary feedback to the government. 

When it comes to providing quality digital service, we can’t afford to forget about artificial intelligence (AI) that provides excellent services to its customers using chatbots within the government websites to complete necessary transactions. It helps in improving policy development, enhancing administrative efficiency, examining complex datasets and delivering new and improved services to its users. 

One more benefit which the government derives from technology is the facility of detecting geographical location that helps the users to choose their government services according to their preferred location. With this special feature in the government websites, citizens can save a lot of time and get access to the nearby government services without any concern. 

Enhancing the return on public investment

Observing an uncertain growth and rising demand in the environment, it is important for the government to find sustainable solutions to finance public services and infrastructure. This is when the government needs to adopt digital technologies which can help in exploring new models for providing services and improving the management of resources in a smart and efficient way. Predictive analytics and text mining are some of the smart managing resources procedures that help in predicting problems and facilitating preventive action like for example recognising taxpayers at the risk of non-payment.   

Maintaining citizen security

Everything comes with both pros and cons. Technology can be both a hindrance and a solution too. What I meant by this is to take your attention towards the cyber security issues. There are a lot of cyber attacks taking place all over the world. So, it is the government’s responsibility to safeguard the citizens from such threats, helping them live fearlessly without any doubt related to digital security. There are information security management systems that are introduced by the government to safeguard all the important data. Cloud computing is also a good process of increasing the computing capacity and facilitating safe payment platforms for citizen transactions. 

Improving future workforce

A country’s workforce plays an important role in the economic growth and development. As a result the government should focus on building capacities and skills in their employees to achieve better outcomes. A responsive environment is beneficial for attracting enthusiastic workers who can actively take up lead roles, contributing to the evolution of the society. The employees can be encouraged to concentrate on stimulating and value adding tasks. This is made possible by deploying intelligent automation tools to reduce the manual and repetitive work that can complement human workers. Therefore, it helps in enhancing productivity and satisfaction, further helping in improving the citizens' experience with government services. 

Upgrading infrastructure

Government has observed an increasing need of building and upgrading infrastructure, especially in the urban areas due to huge population growth. In situations like this, a new infrastructure can be beneficial to support the growing population and increased economic activity. A smart infrastructure can be built by adopting digital technology that can provide digital literacy among citizens. Some of the examples are software, smart devices and sensors that can enable secure access to government services. 

Provides better communication in emergency situations

The government websites can be a great help at the time of emergency since it is the first line of defence in such hard times that can provide the necessary support to the citizens. By building such functional websites with easy navigation, government officials can connect to the people in need and make sure that everyone is well informed about the important updates and announcements.   

Reports and surveys tell the same story

The fact that the technology revolution is offering new opportunities to the government is also agreed by some of the well known company’s reports and surveys. Let us take a look at their opinion.


Microsoft, in a study, shares four key focus areas that act as the main drivers for a digital transformation roadmap. With these pillars, Microsoft is trying to help the government in accomplishing the much needed digital transformation that can provide the best services to its citizens. 

Citizen engagement

Government is able to better engage with the citizens through connected mobile services which helps in understanding citizens' needs and necessities leading to good customer satisfaction. This helps the government in enacting mobile citizen services which leads to better communication with the citizens on a very secured and reliable platform.

The Microsoft cloud platform helps in enhancing productivity, reducing management costs and protecting government data from any cyber attacks. 

Government workers empowerment

The government workers are facilitated with the necessary digital technologies, for example, Microsoft cloud platform that helps in proper communication with the employees and work in a much efficient way. The employee tasks get easier like gaining access to real-time case information, file reports and developing effective strategies together as a team maintaining the required security and compliance.

Government operations optimization

The cloud services and solutions help in optimizing the government operations, promoting the cost and operating efficiencies. Microsoft aims at delivering an integrated, flexible and a cloud and productivity solution for government which is trustworthy, also that helps in addressing all the main transformation challenges faced by the agencies in providing quality services to citizens.   

Service transformation

With the help of digital transformation, an agency gains access to huge quantities of data from processes and also the Internet of Things to provide better analysis, insights and better decision making that can enhance operations and provide new service opportunities. Now the data can grow in value since the government takes proper advantage of self-service data analysis tools, enabling everyone to work virtually with any type of data in new and convenient ways. 


A Deloitte Digital Global Survey, The Journey to Government’s Digital Transformation explores the digital technology’s capacity to crucially transform the manner in which the public sector operates and delivers services to customers and present strategies for government leaders to measure the rate of their progress. It includes responses by more than 1,200 government officials from over 70 countries. This global survey also includes interviews with more130 government leaders and digital experts to get insight to the practices and policies influencing organizations’ “digital maturity.”

While surveying the 1,200 government officials from over 70 countries, they revealed that digital technologies are having a significant impact on the government. Among the respondents, three-fourths expressed that digital technologies are disrupting the public sector. It was also found that governments are at different stages in their journey towards digital transformation. A very small percentage can be considered as ‘maturing’ but the majority is still under the developing stage. 30 percent of the organizations surveyed confirmed that they are ahead of the public sector peers regarding digital capabilities; 70 percent said that they are behind the private sector. The two primary drivers of digital transformation i.e. cost-budget pressures and citizen demands are far away, accounting for 75 percent responses, although only 14 percent are moved by government directives.  

Deloitte surveyed 800 government officials over eight countries to analyze COVID-19’s impact on government’s digital transformation around the world. About three-fourths of respondents expressed that COVID-19 has accelerated their government’s digital transformation, although 80 percent said that there wasn’t much advancement in their organization’s digital transformation. 

The government agencies before the pandemic were majorly “doing digital” i.e. utilizing digital technologies to improve their capacities, yet majorly depending on legacy operating models. Governments were encouraged to enter into the next level of digital transformation due to COVID 19. Therefore, 77 percent of the government agencies confirmed that taking such initiatives due to this pandemic has brought a positive impact upon their organizations. Although they are “doing digital”, it's time to “be digital”. On reaching that stage of completely “being digital”, companies will be able to use some impactful technologies like cyber, AI and cloud to upgrade the human experience and entirely transform back-office operations and service delivery. Below are the stages of an organization’s digital transformation. 

Source: Deloitte

The ultimate goal of an organization’s digital transformation is to reach the stage of “being digital” as described in the above diagram. This stage consists of reinventing the strategies of meeting citizens demands and expectations leading to improved customer satisfaction by the government. By following the necessary measures, every government should opt to reach its final goal and utilize the optimum benefits of digital transformation. To know more on transformational strategies brought forth by Covid-19, read about digital readiness, how the pandemic enabled businesses to reimagine their operations, and the pandemic-driven digital transformation strategies.

CFI Group

According to CFI Group's 2020 Government Websites report, the government websites have played a major role in providing high quality, reliable information to the citizens during the hard times of COVID 19. According to the current data, the federal government websites are on the way to obtaining traffic volume of about 18 billion visits, representing nearly about a 80% increase over last year. The customer satisfaction index(CSI) of federal government websites is 73 as counted on a 0-100 scale for the fourth year in a row. The federal government websites are a reliable and cost-effective way to communicate with the citizens. The 2020 survey provides the latest update on citizen satisfaction i.e there is an increase in citizen satisfaction due to the availability of mobile access trends and easy chat facility. 

Using Drupal for digital transformation of government

Why choose Drupal for government websites? Drupal CMS tends to transform the web development scenario of the government websites dramatically. It provides excellent web services that help its users experience a dynamic digital transformation. Many prominent Drupal government websites are built with the help of the following significant Drupal features.

Open source

The Drupal project is completely open-source software. Everyone is free to download, use, work on and also share it with others.  It is based on principles like innovation, collaboration and globalism. It can be distributed under the terms of the GNU General Public License (GPL). There are no licensing fees for Drupal.
Learn more about open source here:

Content Workflow

The in-built tools in Drupal helps in content creation, workflow and publishing, making it easy for the content creators to efficiently do their work. Permission and authentication help in managing editorial workflows effectively. The facility of previews help in showing how the content will look on a device before the user approves and publishes the content. Drupal helps you in creating content with a WYSIWYG editor. It allows you to quickly track all revisions and changes, if you need to maintain a history of content changes. You can view the complete stages of your content, from creating, reviewing and publishing, enabling you to manage your roles and actions, automatically. The unique feature that Drupal provides is the ability to create a structured content i.e. describe content elements, tag content based on any attributes, form convenient taxonomy for content so that it can be looked, found, used and reused if necessary in ways that increases the customers satisfaction. 

Drupal helps in creating the convenient content architecture using the Admin Interface or even do it programatically. There is an availability of unique mode tools and views, customizable menus that can create a comfortable user experience, also creating ways to content across numerous devices.  

Read about how layout builder and paragraphs module enhance content workflow in Drupal.


Drupal CMS is fully secure and it safeguards the websites from any types of serious internet vulnerabilities. It is designed keeping robust security in mind. There is a dedicated staff team of security specialists, along with a huge professional service provider ecosystem as security remains one of the top priorities of this free and open platform. Most of the security issues are handled by Drupal’s well built coding standards and strict code review procedure.

According to the 2020 edition of the Acunetix, Web Application Vulnerability Report, Drupal was found to be the most secure CMS in the open source CMS market.

Source: Acunetix
Performance and scalability

When it comes to performance, Drupal’s built-in performance features, combined with a modern CDN provider, perform well under the pressure of supercharged databases, load-balancing and advanced caching. Drupal’s scalability refers to the fact that it can manage the largest high traffic sites in the world. To know more, read about Drupal’s performance optimisation offerings and how it scales with your needs to govern high web traffic.


Drupal's automated language translation helps in reaching different audiences with localized content. It builds customized sites in any language to complex multilingual web applications. Core modules in Drupal facilitate complete translation of every part of a site, content types and their specific fields, users, menus, taxonomy, blocks, comments and contact forms. It also permits the identification of preferred language in accordance with the user's IP address, URL, browser settings, session and more. Read more about Drupal’s multilingual capabilities here.


Drupal has a special feature of building websites accessible by people with disabilities. It ensures that all its features conform with the World Wide Web Consortium guidelines (W3C) guidelines: WCAG 2.0 and ATAG 2.0. This feature proves to be very prominent for the government sites as it successfully achieves one of the objectives to serve all its citizens regardless of any discrimination. 

Learn more about accessibility here:


Drupal builds an exclusive, personalized profile for each visitor, starting from using geolocation, browser history, behavior taxonomies and device type. It helps in gaining an overall customized experience, enabling you to track and report with A/B and multivariate testing, increasing ROI through target marketing and also provide segmentation of visitors over devices with an aim on the significant user identity for your business goals. 
Learn more about personalisation here:


Drupal has unique SEO tools that can improve your site’s visibility. The tools or modules are discussed below:

To know more, read this definitive guide to Drupal SEO in 2021.

Multi-site support

Drupal helps in managing multiple sites across your organization, geographies, brands and campaigns on a single platform that allows easy, fast website creation and deployment. Read why and when you should use Drupal multisite factory approach.

Marketing automation

By using tools and modules, in recent versions, Drupal helps in easy integration with the automation platforms that can collect customer demographics, helping in converting potential leads within the most suitable time. Learn more about how marketing automation can be leveraged with Drupal here.

Mobile first approach and mobile apps

With Drupal you can build responsive websites and create web applications that can provide optimum visitor experiences. It helps in providing responsive design best practices and guarantee your users get a perfect content experience each time, on every device. To know more, read about mobile-first design approach and mobile apps like that of Flutter-powered delivered by Drupal.

Integration with third party tools

Drupal helps in smooth integration with a vast ecosystem of digital marketing technology and other business applications, so that you can use the finest set of tools today, and also flex with new tools tomorrow. Drupal’s API-first focus refers to connecting content to other websites and applications, building content more powerful. 

You can specify Drupal exactly what you want and create limitless solutions which support your business needs. 

Strong stack foundation

Drupal lives on the latest LAMP technology stack: Linux, Apache, MySQL and PHP that meet the needs of flexible, fast-moving agile enterprises and brands creating next generation digital platforms.

Decoupled architectures

Drupal provides content flexibility that will allow an easy flow of content over websites, native apps, connected devices and are displayed on third party sites and also social networks. Since, many CMSes try to manage content in a back-end repository and move it to “front-end” templates that can serve up an experience (mostly static). Drupal allows you to decouple the back and front ends, wherever it's useful. Therefore, Drupal content exists as reusable chunks, free from presentation, ready for easy delivery to websites and apps. Content also becomes future-proof. Drupal’s presentation i.e. RESTful API and neutral content help front-end developers to come out of the restrictions, enabling them to build interactive websites and applications, according to their preferences. They are allowed to use tools like Angular, Node, Ember, Backbone, and others. With this active platform, you can attain third-party content(eg. syndicators and aggregators) and make it available to any website, app or channel. With Drupal’s content-as-a-service capability, drupal’s content can be easily consumed by other applications and websites you choose. The Drupal front-end developers can easily design content, for example, separating back-end content from front-end presentation according to their preferences.

Learn more about decoupled Drupal here:

Web Hosting

With Drupal you can choose the best hosting vendor that suits your needs, you can change hosting vendors whenever you want, and also select to host the website internally. 

Upgrades and migrations

The Drupal upgrades are considered to be very easy and convenient. The upgrade from Drupal 8 to 9, Drupal 9 being the most recent and much improved version, is very effortless, according to its makers. The developers are allowed to make the upgrade themselves with the help of Upgrade Status and Drupal Module Upgrader. This further helps you to know whether your modules and themes are competent enough for Drupal 8/9 and converting your custom code accordingly. 

Learn more about Drupal 9 upgrade here:


Drupal has plenty of modules, themes and distributions to extend the functionalities.

For example, these are some of the Drupal distributions for government:

Opigno LMS

Opigno Learning Management System (LMS) is completely open-source, 100% customizable and 100% Drupal-based. It is a fully-fledged secure LMS for any organization or industry. It is used by Governments and Government agencies, higher education and large enterprises. This is available for Drupal 8 and Drupal 9 version is said to be available towards the end of August 2021.

Dimpact WIM

WIM is a complete free reusable website model designed for local government and municipalities. With WIM every municipality can experience a great online presence; smoothly and at minimal cost. The WIM sites are considered as a cooperative initiative of the Cooperative Association Dimpact from The Netherlands. Their goal is to achieve a modern integrated public service. Please note that this distribution is only available for Drupal 7.


Using Drupal 7 core, the govCMS distribution is built along with additional software such as modules, themes, libraries, and installation profiles specific to Australian government websites. This govCMS development is carried out on GitHub. It is worth noting that this distribution is only available for Drupal 7.


deGov is the first Drupal distribution that focuses on the needs of (German) governmental organizations. It is seen using lightning media as a basis and extends it with valuable functions to meet the use cases for various scenarios:

  • Sites for governmental organizations from all levels (federal, regional, local) to publish information
  • Service-oriented E-Government portals to end the gap between citizens and your administration
  • Citizen Engagement portals to discuss and decide online
  • Open311 portals for civic issue tracking
  • Open data portals to publish and form communities around data
  • Intranet/Extranet for government employees

The Drupal 9 version of this distribution is available for download.

Drupal voor Gemeenten

DvG is the "Drupal voor Gemeenten" distribution developed particularly for Dutch municipalities. It is built around the top tasks model, putting smooth and efficient online services front and center. This is available for Drupal 7.

There are also various Drupal themes for government that come handy:


The United States Web Design System (USWDS) is a design system particularly built for the use of the Federal Government. This theme is the process to integrate the styles with Drupal. 

Government Website Template

Based on zen theme, the Government Website Template theme was efficiently modified and customized for the AO39 (administrative order no.39) Compliance. By using this foundation css theme framework (version 5.4.5), this theme provides a responsive design for the template. Additionally, it has a module helper that enhances the functionality of the template and it also adds additional blocks such as transparency seal and Philippine Standard Time(PST). 

GOV.UK Theme

The GOV.UK Design System Frontend node module is being used by this specific theme which also has Twig template files for the majority of the GOV.UK styles, components and patterns. It is completely responsive and multi-column with a mobile navigation menu. This theme shows full support to Drupal Webforms, along with client-side validation of necessary fields and identifying any error message when there is GOV.UK validation error. Also, it is compatible with Drupal 9. 

Bootstrap Rijkshuisstijl (Dutch Government Branding)

Netherland’s central government owns a standard Visual Identity which is used on every website. The central government visual branding i.e. "Rijkshuisstijl" has been further translated to the Rijkshuisstijl theme. The main features of this theme include:

  • Capable of being configured with every government agency.
  • Capable of being configured with 17 preset colour schemes.
  • Availability of responsive design and mobile first facility.
  • Digitoegankelijk compliant.
  • Bootstrap v4 is used as a design framework.
  • A living style guide is provided with a KSS node.
  • The theme is completely translated into Dutch.

The theme is compatible with Dupal 9 as well.

Bootstrap 4 GovBR SASS

The Bootstrap 4 GovBR SASS is a Barrio subtheme which simplifies integrating Bootstrap 4 SASS, GovBR visual standards, and "Barra do Governo" with Drupal. This particular subtheme overrides nearly every CSS from Drupal and replaces Bootstrap variables wherever necessary to build from the roots a new set of CSS files. It is compatible with Drupal 9.

GovBR theme

It is a responsive Bootstrap based theme along with the default identity of the Federal Government of Brazil. This theme has two requirements i.e., Bootstrap base theme and jQuery 1.9.x (jQuery Update recommended).

And, you also get really useful Drupal modules for the government. For example:

USWDS Ckeditor Integration

The USWDS library has become an essential requirement for government websites. This module majorly focuses on making a user to smoothly utilize and inject USWDS classes and components into the ckeditor without even opening the source event for a single time. The USWDS Ckeditor Integration module is compatible with Drupal 9.

GovCMS Dissemination Limiting Marker (DLM)

With regards to the paper–based information, all electronic–based information requires to be marked with a suitable protecting marketing. This particular theme provides the option to a user for setting a default Email Protective Marking, like SEC=UNOFFICIAL], appended to the end of the subject line for all outgoing emails sent using drupal_mail() on your site. 

So, these are some of the Drupal government themes, modules and distributions that help extend the features and functionalities of Drupal as you like.

Support, maintenance, hiring and partnering with digital agencies

There are a lot of Drupal agencies you can opt for. They tend to provide you with the best services possible, according to your convenience. The top 4 Drupal agencies in the global Drupal marketplace are listed below. 

Source: Drupal.org
Support for Emerging technologies

Drupal never steps back from utilizing the latest technologies to deliver a better user experience. Some of the examples can be the use of artificial intelligence in the form of chatbots, virtual reality, IoT and Blockchain, cognitive search and digital voice assistants like Alexa on Drupal sites. 

Therefore, the following question, “Why drupal for government” is well answered by the above features that allow the government to build very functional and secure websites for its citizens. 

Case studies 

Here are some of the case studies that tend to prove why Drupal’s the best choice when it comes to selecting the right CMS. 

Ministry of Finance, Somalia

MoF Somalia is responsible for government revenue raising, expenditure, preparing annual budgets and economic policies among other responsibilities. They were looking for a technology partner that would help them in presenting their website with a clean architecture and design to their global audience. The main goal was to restructure the website, to integrate all the new content types, along with a user-friendly navigation, also adding a custom type of publication to publish annual reports. OpenSense Labs leveraged Drupal to complete the project within 6 weeks using the agile project methodology. We successfully built a website which was a lot more user-friendly along with faceted search application features and loads in less time than before. The site became SEO friendly, with a much better architecture.  

Here is the detailed case study of the Ministry of Finance, Somalia. 

City of Boston

The City of Boston is well-known around the globe for its winning sports team, prestigious universities, New England food and rich history. It serves 4.8 million people in the Greater Boston area, supporting 23 neighborhoods. Boston, a pioneering city is famed for having the first public school, public park and subway system. The City of Boston’s website was 10 years old and was running on an outdated Content Management System which could no longer support its needs. The main aim was to build a responsive website that could meet all AA WCAG accessibility guidelines. Drupal finally built a website that dramatically enhanced the accessibility of information and services the city offers, and also marked a shift in residents’ expectations of government.  

  • The website has responsive mobile design
  • The new Boston.gov could meet all AA WCAG guidelines for accessibility and establish a 9-10th grade reading level (down from a postgraduate level)
  • Could Migrate more than 20,000 web pages and one million words to the new boston.gov
  • The website redesign could be delivered under budget
  • The new website launched 11 months after the kick-off meeting

The challenge was to opt for an open source CMS in the Amazon cloud to migrate the existing site off of a proprietary, on-premise CMS system as fast as possible without causing any service interruptions for both public visitors and content managers. NASA wanted its new website to develop a solution that could offer both a modernized display as well as provide the same user experience on both desktop browsers and mobile devices. It was important to account for live coverage events drawing even larger crowds of online visitors, as well as to scale down when the events concluded. NASA wanted it’s CMS solution to accommodate continuous integration with new services and technologies - both commercially available and custom built.

Drupal helped in reducing the complete development timeline – designing, executing and deploying the solution from development to production, also saving NASA millions of dollars in annual savings at the same time. Building with Drupal on the Amazon cloud ensures that NASA’s content was stored securely, also providing NASA the advantages of very flexible development capabilities when designing, executing and integrating new features and services. With its user-driven API’s, infinite compute scalability and storage, dynamic host provisioning, constantly developed robust new features, Drupal and AWS proved to be the perfect match to meet the content requirement of both NASA and the public.

Talk London

Talk London is an online community where Londoners can share their opinion on the city's big issues. Since it is operated and managed on behalf of the Mayor of London by City Hall, the views shared through Talk London help to control the policy decisions of the future. It is a hub for crowd-sourcing ideas, raising awareness of initiatives, connecting Londoners to each other and City Hall so they can participate in designing and delivering improvements in their neighborhoods and communities. Talk London’s website (London.gov.uk) is built on Drupal 7. There was a requirement of an upgrade to Drupal 8 that would provide the chance to make Talk London 3.0 easy for the Londoners to get involved in policy and programme design, also refreshing the design with an updated brand identity. 

The goals for Talk London 3.0 were:

  • Developing a diverse membership
  • Growing participation
  • Focus on transparency

The Talk London website was rebuilt by using an agile project management approach (Scrum) on Drupal 8, incorporating a refreshed brand execution, and also using a Storybook pattern. The basic functional requirements included:

  • Advanced user generated content functionality
  • Email notifications for end users
  • Flexible content layouts for Talk London website editors

There was also a requirement of a large-scale migration of historical content from the old Drupal 7 platform to the new Drupal 8 implementation.

Talk London 3.0 was launched in early March 2021 at the time for the Covid 19 recovery campaign. 


Digital transformation in the government has become essentially important to meet its citizens' growing expectations and needs. Such a transformation can be challenging but eventually it proves to be rewarding for both the citizens and the government. So, a government that is ready to transform themselves and adopt the necessary digital technologies can improve the citizens’ quality of life and also enhance the citizen-government relationship. And Drupal proves to be the best support in building the bridge between people and their government.

blog banner blog image Drupal Government Digital Transformation Blog Type Articles Is it a good read ? Off

Drupal Association blog: Participate in the Drupal Business Survey 2021

2 days 12 hours ago

The 6th annual Drupal Business Survey 2021 is here! We are eager to hear about your vision and experiences on the business side of Drupal. Along with One Shoe and Exove, we are calling upon Drupal agency leaders worldwide to let their voice be heard in this sixth edition of the annual Drupal Business Survey.

Take part here

The pandemic as a catalyst for investments in digital?

Last years’ edition of the Drupal Business Survey indicated that the pandemic might accelerate the demand for digital projects (and Drupal). Therefore we included questions in this year's survey about business trends, challenges and we ask people about their business outlook for Drupal companies. With your input, we can gather new insights into important issues that Drupal business leaders are facing today. Read the 2020, 2019, 2018, 2017 and 2016 reports for previous analyses.

Take the survey

Participation is completely anonymous and will take you less than 10 minutes. The responses will be used to generate anonymised, aggregate report about the state of the Drupal business ecosystem. The results and insights of this survey will be officially published on Drupal.org and presented at the Drupal CEO Virtual Drinks in October.

Talking Drupal: Talking Drupal #305 - Project Browser

3 days 7 hours ago

Today we are talking about The Project Browser Initiative with Chris Wells.


  • John - Design 4 Drupal
  • AmyJune - Roadtrip, redwoods and Banana Slugs
  • Chris - Upcoming RV roadtrip
  • Nic - Tugboat
  • Project Browser elevator pitch
  • Initiative start
  • Inspiration to join and seek leadership
  • Current status
  • Estimated timeline
  • How can someone get involved

Banana Slugs https://en.wikipedia.org/wiki/Banana_slug Project Browser Slack https://drupal.slack.com/archives/C01UHB4QG12 Project Browser Module Page https://www.drupal.org/project/project_browser Project Browser Sandbox https://dev-pb1.pantheonsite.io Project Browser Initiative https://www.drupal.org/about/core/strategic-initiatives/project-browser


Chris Wells - https://www.redfinsolutions.com @chrisfromredfin


Nic Laflin - www.nLighteneddevelopment.com @nicxvan

John Picozzi - www.epam.com @johnpicozzi

AmyJune Hineline - @volkswagenchick

eiriksm.dev: A Robot Updated my Website

3 days 12 hours ago

At Drupalcon North America this year (2021), I had a presentation named "Less human interaction, more security?". This pandemic-ridden year made sure it was an online version of the conference, which makes presenting a bit different. One interesting aspect of online presentations, is that it enables feedback and chatter in the comments section. First of all, this meant that I could get feedback on my GIFs even if I wasn't in the same room as the session participants. As we all know, GIFs are an important part of every presentation. Second, I also received a lot of relevant and interesting comments on other matters related to the presentation. Today, I want to talk about one of the subjects that came up: is it scary to let a robot update and deploy your website?

To those of you that didn't attend the presentation; let’s do a quick recap. First, I talked about how to set up a fully automatic discovery, patching and deployment of Drupal security updates using violinist.io and Gitlab CI. Next, I demonstrated how a new Drupal version was picked up automatically, updated and pushed to open a Gitlab Merge Request for the project in question.

The Merge request was then analyzed and found to be a security update, which enabled auto merge for the merge request

Finally it was tested according to the continuous integration set up for the project, and deployed to the production server for the demonstration.

No human hands were used to write commands or click buttons in the demonstration. What does this mean? Robots taking over? Reason for anxiety attacks? In this case, it's a clear "no" from me. Let me explain why.

Several things could be considered scary about letting a robot update and deploy your website. First, you´re somehow allowing third party access to your production server. In my opinion, this can actually be a step towards making your deployments more secure. Let me explain: maybe your current workflow involves a person remotely accessing the server and running deployment commands. Depending on your configuration of remote access, this can actually create a larger attack surface, instead of making sure only the machine deploy user can deploy to a server. There are of course more things to consider to this question, but my point still stands: moving towards only automated deployments will make your application more secure, more robust and more predictable.

Another potential cause of concern about letting a robot update and deploy your website, is that an update might break the website. Before deploying a change to a production server, people often like to check that their website still works in a real browser. I acknowledge this need for manual verification, but I believe there's a better way. Take the task of updating Drupal Core. I'll wager that a Drupal release has a lot more test coverage than any website you are currently maintaining. If you combine this with some basic functional testing for your website, an update like this is probably some of the safest code changes you can do. Furthermore, having a robot do it for you makes it very unlikely that the update commands will be done wrong, which could happen if done by human hands.

Of course, sometimes automatic updates will crash your site some way or another. I find this unproblematic. Not that I want websites to crash, but it happens. And this also happens when a human being is the author of code changes. However, I prefer that automatic updates crash my site, as this uncovers missing test coverage and makes me more confident about future updates. Say that your Drupal website was relying on the (fantastic) Metatag module, but one particular update made your metatags stop working on a particular content type. How come the update was deployed then? Because you did not have test coverage for that functionality. By learning from this, you can expand your test coverage, and feel even more confident about automatically updating the Metatag module the next time there is a new release.

Don´t get me wrong. You don't have to wait for your site to crash to learn that you´re missing test coverage. Start by introducing automated updates to your website through merge requests. When a new merge request comes along for an update, you´ll get a feeling about how confident you are to deploy it. Maybe it's the metatag module, and you know you have to test it manually to make sure it works. This could be an indication that you are lacking test coverage. To be able to automatically deploy the next version of metatag, just write some tests for the things you are testing manually.

Ultimately, my claim is that updating automatically will make your updates more secure and predictable. Over time, it will also increase your test coverage and the general robustness of your project. And at a certain point, maybe when your site is in more of a maintenance state, you can merge and deploy all updates automatically.

This is also why I now routinely enable automatic PHP updates of composer dependencies on all my sites and projects. And now that these concerns are addressed: Please check out the presentation and make up your own mind on how scary automatic updates really are. And if you want to start updating right away, here is a link to violinist.io

Disclaimer: I am the founder of violinist.io

Angie "webchick" Byron: Ch-ch-ch-ch-changes... (and a brief history of Drupal)

3 days 13 hours ago
What the what?!

Sad Drupal is Sad. :'(

Well, might as well get right down to it... I've made the incredibly difficult decision to leave Acquia, and my employment there officially ended last week. :'(

Some important notes about this:

  • This is in no way a negative reflection on Acquia. I have worked with SO many amazing people there in the past 10 years(!), and have endless gratitude for all of the challenges, opportunities, learning, and laughs. The leadership team has a solid strategy, and the effort everyone there puts into achieving it every day is inspiring.
  • This is in no way a negative reflection on Drupal. In my time here, I've seen Drupal through its youthful toddler years, to its surly teenage years, and now Drupal's all grown up, with a nice, stable apartment downtown. :) Drupal is and remains an amazingly powerful, flexible solution for building every single type of application one can dream of, with an incredibly strong and vibrant community behind it.
  • What this is about is about an opportunity that came up to take lessons learned from Drupal and apply them more broadly to (hopefully) make an even bigger impact (more on that below).
10 years sure is a long time…

It sure is! Here are some fun Drupal facts that help illustrate key achievements of Acquia's Drupal Acceleration Team [DAT] (née Office of the CTO [OCTO]) over the years, and hopefully provide some insight into the areas of investment Acquia has made and continues to make in Drupal.

IMPORTANT NOTE: The folks explicitly called out below are former co-workers who work / have worked at Acquia, since this post is in some ways a "farewell" to them, and an opportunity to celebrate their often unsung efforts. This is unfortunately NOT able to be a comprehensive list of ALL of the amazing people working on various initiatives, because that list would be far, far too long and I'd invariably miss someone. :( Suffice it to say, however, that none of the items listed below would be possible without hard work, input, funding, and help from literally thousands of other people across the wider Drupal community!

Did you know? Back in 2011:

Authoring Experience and Strategic Initiatives

Eat your heart out, WordPress! :D

Eas[y|ier] Upgrades

Tale as old as tiiiiiiime...

  • Drupal 7 had just come out, and the first initiative of the day was to help the community get all of the modules ported to the new version. (Sound familiar? ;)) Drupal Gardens (R.I.P.) was key to this effort, with a world-class team focusing on the biggest, gnarliest modules first. We then repeated that initiative for Drupal 8, for Drupal 9, and, because @Gábor Hojtsy is such an *amazing* overachiever, have already started it for Drupal 10 as well! Ted Bowman (@tedbow) and Katherine Druckman (@katherined) deserve shout-outs for doing a huge ton of Drupal 7 > 8 and Drupal 8 > 9 (respectively) porting in their initial Acquia assignments!
    • To assist with these efforts, OCTO/DAT has also developed numerous pieces of tooling over the years to help make upgrades easier, including:
      • Drupal Module Upgrader (originally an Acquia Hackathon project!), an automated code analysis/porting tool for Drupal 7 -> D8/9 code which @phenaproxima rocked the crap out of as an intern back in the day!
      • Upgrade Status, a dashboard of your contributed modules' porting status that gives you a dynamic "todo" list for major upgrades, which the team has shepherded over the years from Daniel Kudwien (@sun)'s original efforts back in the day!

    Three words to strike fear into any Drupal site admin.

    • In 2011, Drupal releases took the philosophy of "it's ready when it's ready," which made them basically impossible to plan around. Even security releases came out on an unpredictable, as-needed basis, so running a Drupal site required CONSTANT VIGILANCE. :P OCTO/DAT worked with the Drupal Security Team to develop the Wednesday security release windows system we all know today, and also with core contributors to develop the predictable semantic versioning release approach that Drupal 8+ uses. Major kudos go to Jess (@xjm) for making sure those trains run on time, and that they start any fires when they reach the station! :D
    • Another Drupal release philosophy from 2011 was "we'll break your code, not your data". OCTO/DAT has done extensive work, alongside other major community contributors, to enact various policies that ensure Drupal upgrades are easy from Drupal 8 onward. Governance

      I don't have a pithy caption here; this is actually sound advice.

      • Back in 2011, Drupal was very much a "do-ocracy" which meant that it pretended it didn't have a governance structure, which mostly meant that if you weren't already neck-deep in the community to know who everyone was, you were completely in the dark as to which people held key decision making powers. :P We held a Governance Sprint alongside OSCON with mindful community members, as well as various luminaries from other open source projects, and developed an explicit, scalable governance framework for the Drupal Association, for Drupal Core, and for the Drupal Community. Much of that framework exists to this day, and others have evolved as project needs have changed. Alex Bronstein (@effulgentsia) deserves some props here as he's always incredibly thoughtful of structural changes within Drupal and their longer term ramifications.

      The delicate balance...

      • Back in 2011, if you needed a Drupal 7 committer, it was down to either @Dries or me. Over the years, we've built this up to a team of 14 committers, including different specializations in Product Management, Framework Management, Frontend Framework Management, and Release Management. We've also brought onboard a Core Team Facilitator (Pamela Barone (@pameela)) to help with coordinating efforts of the team itself.
        • Another major initiative that falls under this is the Drupal.org contribution credit system, to encourage organizations to donate time back to the project and create more makers than takers.
        • In partnership with the Drupal Association, we created the Drupal 8 Accelerate grants program to bash through the final critical bugs holding Drupal 8.0 from release. The core committer team was in charge of disbursing $125,000 in the form of bug bounties, and directly resulted in Drupal 8.0 shipping in 2015 (without it, who knows :\).

      I'm sure I'm forgetting a million and a half other things that happened over the years, but hopefully this helps paint a picture for those who are newer to the company of how far Drupal has come, and the role Acquia has helped play in that growth.

      What's next?

      Webchick is going Web Scale! ;)

      Starting today, I'm going back to my community building roots at MongoDB as Principal Community Manager on the Community Team, focusing on initiatives such as building out an open source contributor program and further awesome-ifying the MongoDB Champions program.

      What drew me to this opportunity is:

      • MongoDB has focused from the outset on stellar developer experience, which is a value I believe in strongly, even since before my time in Drupal. I really appreciate that they take a strong, developer-centered view of how databases ought to work, and that they've tackled so many of the hard problems up-front.
      • Because MongoDB is a technology that is used by tons of other projects, languages, frameworks, etc. it seems like a really great opportunity to both take some of the lessons learned from Drupal over the years and apply them to other communities, while also being able to get a broader perspective from other communities and bring those back into Drupal!
      • The people. While it's really (really!) scary to think about starting out in a new place with new faces, I had the opportunity to interview with folks from a wide cross-section of the company. Every single person I spoke with fully embodied their core values. Every single person was passionate, genuine, kind, and determined to make a huge difference. In a lot of cases speaking to folks felt like speaking to a friend you've had for years.
      • MongoDB has also been a tremendous ally to Drupal (speaking of 10+ years :)), putting funding and time into efforts such as Drupal 7's database abstraction layer, the Views in Drupal Core initiative, and more.
      • From being prompted for pronouns on the initial application form, to a variety of queer/trans-inclusive benefits, to dedicated LGBTQIA+ inclusive initiatives, MongoDB takes their commitment to Diversity and Inclusion more seriously than just about any other tech company I've seen. Colour me impressed!
      • AND, to top it off, they're going to continue to give me dedicated time to work on Drupal as well! :O

      Our new chihuahua puppy Arthur wearing the MongoDB Pride bandana, more or less like a cape. :D

      So, fret not! I'll still be around in the Drupal community, hopefully with a broadened perspective and bringing in some new ideas and energy along the way! :)

      Sheesh, what's the TL;DR here?!

      So, in short:

      • I no longer work at Acquia, but want to sincerely thank everyone there for 10+ years of important work, learning opportunities, amazing friends, and of course laughs.
      • A LOT has changed in Drupal over the last 10+ years, and up above you can view a tiny sampling of it.
      • I'm starting a new position at MongoDB today as Principal Community Manager, and am really excited! (And also nervous, but hey. ;))
      • I'll still see you Drupal folk around in Drupal Slack and the issue queue. :)
      • MOST importantly, we now have a puppy. ;)

      One last thing: If we've worked together over the years in a Drupal community capacity and if you're up for it, I would be hugely appreciative of a LinkedIn recommendation. And I'll do my best to reciprocate! :)

      Tags: drupalmongodbacquiacareerfuturepastcute animals

#! code: Drupal 9: Selecting Machine Names For Content Entities And Fields

4 days 5 hours ago

Naming things is hard[citation needed] and there are a lot of things that you can name when configuring a Drupal site. Picking the right machine names for the different parts of Drupal can make your life easy in the long run. Changing labels is simply a case of tweaking the label in the interface, or through configuration updates. The issue is that once you decide on a machine name for something in Drupal it's pretty much set in stone forever.

The machine names you pick are often used in database tables, paths, interface elements and pretty much anywhere it is used. Changing entity or field machine names at a later date is difficult and can mean writing complex code or using migrations to achieve.

I have built a lot of Drupal sites over the years and done detailed audits on quite a few as well. This experience has given me a lot of insight on how to set up by machine names in Drupal. I have seem some horrific naming practices and poorly configured sites and in my experience there is a correlation between poorly named things in Drupal and bugs caused by those poor choice of names.

As far as I can tell the drupal.org documentation doesn't actually cover this aspect of setting up Drupal. It does address naming conventions in code and modules as part of the coding standards, but not with machine names for content and fields.

Recently, I got into a discussion with a couple of other Drupal developers about content entities and fields, what to name them, and what to avoid when reusing fields. Surprisingly few people have written about naming conventions in Drupal, despite the fact that it has such an effect on the life cycle of the site itself. I thought I would write down some of the conventions I use when naming things and some of the best practices when reusing fields within a Drupal site.

Read more.

54 minutes 16 seconds ago
Drupal.org - aggregated feeds in category Planet Drupal
Subscribe to Drupal Planet feed