Planet Drupal

Syndicate content - aggregated feeds in category Planet Drupal
Updated: 19 hours 46 min ago

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

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

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

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

 1. Experience and Expertise (obviously)

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

2.  Ideal Fit

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

3. Understanding of the Project scope

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

4. Quality of Response

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

5. Reference calls

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

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

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

7. Drupal community involvement

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

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

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

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

Leave us a Comment

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

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


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


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


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

Wed, 11/11/2020 - 02:22

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

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

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

Lullabot: The 7 Best Practices of a Good Editorial Experience

Tue, 11/10/2020 - 21:46

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

Mediacurrent: Mediacurrent IDEA Team Charts the Course for Inclusion

Tue, 11/10/2020 - 15:05
Open Source for Everyone

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

From “IDEA” to Reality 

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

Opening Up About Privilege 

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

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

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

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

The Path Forward

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

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

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

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

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

undpaul: DDEV - Simplify local dev environment

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

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

Mon, 11/09/2020 - 16:34

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

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

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

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

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

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

Mon, 11/09/2020 - 13:03

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

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

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

Mon, 11/09/2020 - 12:17

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

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

This year's report shows that:

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

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

Methodology What data did we analyze?

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

What are issues?

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

What are credits?

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

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

What is the Drupal community working on?

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

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

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

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

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

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

Who is working on Drupal?

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

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

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

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

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

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

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

How much of the work is sponsored?

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

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

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

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

Who is sponsoring the work?

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

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

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

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

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

A few observations:

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

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

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

How diverse is Drupal?

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

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

Gender diversity

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

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

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

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

Geographic diversity

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

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

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

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

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

Limitations of the credit system

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

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

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

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


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

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

OpenSense Labs: Is Decoupled Drupal the Right Choice for You?

Fri, 11/06/2020 - 18:39
Is Decoupled Drupal the Right Choice for You? Gurpreet Kaur Fri, 11/06/2020 - 23:09

Drupal is amongst the top ranking CMSs in the world, its capabilities, both on the front-end and the back-end has made it one of the very best. Yet there were many who thought Drupal lacked somewhere, especially in harnessing the hottest technologies available. And Drupal had the answer to it with Decoupled Drupal

Decoupled Drupal has generated a lot of buzz around it, making it almost ubiquitous in the industry. The full separation of the structure from the content has aided the content management systems with appropriate means to accelerate the pace of innovation and this is the primary reason for Decoupled Drupal to gain an edge over its competitors.

If you are reading this blog, you might have some knowledge about decoupling or the buzz around it might have pulled you in and now you want to try and see whether it is suitable for you or not. Before we get into that, let me give you a clearer picture of what Decoupled Drupal actually is, even if you have some idea of what it is. So, this blog is going to accentuate all the aspects of Decoupled Drupal to help you understand whether it indeed is the right choice for you or not.

What is Decoupled Drupal?

Traditionally, websites operated in a similar fashion to a magazine, meaning they provided static communication to the users, wherein the user is only a witness and not a participant. This system worked for a long time, but no more. Today, websites excel because they are interactive and not just one platform, but many. Phone applications, social media and the answering of client questions through chatbots, all of these have altered the audience’s expectation of websites and consequently the web builders are trying to find ways to improve their user’s experience. 

Drupal, even in the conventional sense, was equipped to handle multiple channels. A Drupal website can be accessed through multiple devices, be it computers, tablets or smartphones. This speaks for Drupal’s versatility and its flexibility, which is why it became so popular. The monolithic Drupal with its ability to store content, present it to the user and create an editorial interface makes it proficient enough to run websites, yet people want more. Since flexibility is the equivalent of Drupal’s middle name, it provides yet again. Get a complete outlook on differences between monolithic and decoupled Drupal architectures here.

In simple terms, the Decoupled Drupal gives room to new technologies on your website, so that they can also work their magic on them. With decoupling, you will be able to segregate your front-end from the back-end and use React and node.js for the former, while the latter would be managed by Drupal. So basically, you will have the best of both worlds, the excellence of Drupal and the many front-end technologies available in the market.

Let us look at some of the technical aspects of Drupal to get a better understanding of decoupling. 

  • The display management is generally handled by JavaScript frameworks and Static Site Generator when decoupled as opposed to Drupal managing it.
  • The speed and performance of Decoupled Drupal sites is usually seen to be higher than the monolithic Drupal sites. 
  • The technical stack in Decoupled Drupal is usually seen to be quite complex.
  • The workflow from the front-end to the back-end is loosely connected, but the connection never falters.
  • The editors enjoy full control over the content, however, additional effort may be required to preview the content.
  • The RESTful web services have allowed Drupal 8 to become an API-first back-end serving web applications, which is absolutely necessary in decoupling.

To get a complete picture of different options of decoupling Drupal, read here.

Why Should You Decouple?

You would only be willing to try something, if you know that you are going to benefit from the trial. Am I right? The same is true for Decoupled Drupal, it has only been able to gain traction in the industry because it is advantageous to the developers. It is these advantages that become the reasoning behind implementing Decoupled Drupal architecture

Yes, it builds creative websites that have independent components making development easy and smooth. A front-end developer would not have to be reliant on a back-end developer to make a change in his presentation layer, nor would a backend developer have to worry about the impact of his changes on the presentation layer. So, can this be the only reason to take on the Decoupled approach?

Decoupled Drupal brings along several advantages that are single-handedly responsible for its adoption. Let us shine some light on these.

Impeccable Performance 

The foremost reason as to why decoupling should be taken up is because it enhances your performance more than you could have thought. The separation of concerns means less request time and that consequently makes your website respond faster and performance automatically enhances. 

Another reason for elevated performance is JavaScript. JS frameworks are known to be multi-thread and asynchronous, what this means is that it is fast. There would be performance issues that would mandate your attention, but even those become easier to tackle. Therefore, a JavaScript front-end is faster as compared to a Drupal front-end. And this is why decoupling is being sought.

Impeccable Development 

With the risk of repeating myself, I am still going to say that when you decouple, you create a clear cut separation between the front-end and back-end. This can be interpreted to mean that both the front-end and the back-end can develop at their own pace without thinking about the effects of the same on the other. They work in parallel. As long as a sound API is in place, development won’t be blocking work since the work is being done independently. 

And there is also the fact that the risk of re-platforming becomes almost non-existent with decoupled Drupal developments.

Apart from this, the 'decoupling team' is usually bigger than a 'monolithic team'. As the saying goes, the more the merrier; the higher number of developers means more ideas for development and faster development. A five-man team is going to bring more results than a one-man team. Do you agree?

Impeccable Publishing and Multiple Consumers

Decoupling comes with an omnichannel presence and the ability to support multiple consumers. Let us understand how.

The Decoupled Drupal architecture works around the API-first notion, which basically means that all your consumers are on a leveled field. This makes publishing all the more easy. You can create content for your website and with just a few clicks, it could be published on multifarious platforms, including social media, intranet and your microsites. Your content would be reused in many different ways and many different times. Since the content is not rigid to the current form of your website, you would also be able to reuse the same after a total website redesign or two.

The Decoupled Drupal is not only the driving force behind your website, but also all the other apps you have, be it on smartphones, set-top TV boxes or maybe the gaming consoles.

Impeccable Team Management 

Decoupled Drupal may mandate a larger team, but it, in fact, makes the working of the larger team smooth and result oriented. You could have 50 developers on your team, yet there won’t be any overlapping concerns. Why? Because decoupling clearly segregates the duties of all developers.

Apart from team management, it is also quite easy to create a team. You may very well know that there is a dearth of Drupal specialists in the market, however, developers proficient in JS are in abundance, for lack of a better word. This makes the process of creating a highly competent team easy, since you do not have to find developers who are skilled at every aspect of website development. 

Impeccable Innovations 

Decoupling and the latest technology go hand in hand, and you must know that the latest technology means more innovations. Decoupled Drupal architecture can aid you in implementing frameworks that are top-of-the-line. Be it Angular.js, Backbone.js, Meteor.js, Node.js, or Ember.js, you can work with any of these. 

    For creating UIs, you can take up the React library;
    For tracking state, you can take up Redux;
    For mobile applications, you can take up Google’s AMP or Polymer tools.

Using all of these would only accelerate your innovative streaks and make your web applications as innovative as it can be. Learn more on how marketers can extract the power of decoupled Drupal here.

When Should You Decouple?

By now we have established enough facts that Decoupled Drupal is a package full of advantages. Now, it’s time to delve deeper and seek the accuracy of circumstances in which it can be put into effect. 

When your back-end and front-end needs are separate 

Decoupled Drupal, by definition, states the separation of the front and backend, so if you feel the need to separate them, then why not? Having a modern JavaScript packed front-end by using React or Angular and the very proficient Drupal backend is a combination that would only bring benefits. All the abilities of JS frameworks are not yet available in Drupal and decoupling can help you capitalise them.

When you have the right team

Having a need for decoupling is not going to cut it for you, you also need to have a skilled team to execute the process of decoupling Drupal. The decoupled approach divides your team into two subdivisions along with your project. Each subdivision would be responsible for a separate codebase, which would later become a complete tech stack. These teams would have to work in sync, although parallely to make the project a success. Provided that you have the team, which has all the varying skills and experience required for the decoupled project, you can and should take on decoupling.

When you have clearly defined data roles 

For decoupling, you must also be in tune with your data needs. Since Drupal would only act as a content repository in the Decoupled approach, it becomes essential for you to remember the communication lines. In this architecture, you will end up using other data services. Such a situation demands clarity, you should be clear as to how you want the data interaction to the front-end, do you want it directly through the service or through Drupal’s API.

When you can support new architecture

Moving towards a decoupled approach means you would need to evaluate your hosting provider. The architecture post decoupling should be under its handling capabilities and that needs to evaluated beforehand. From security measures to additional caching, the host should be able to handle a non-Drupal front-end. If not, check how long your contract is and work from there.

When you have to cater to different channels

The concept of write once and publish everywhere has become synonymous with Decoupled Drupal. The ability to cater to various publishing platforms comes with ease through decoupling. So, if you have a single application that is supposed to dispense content onto various channels, decoupling is going to be great for you. Although it would take some editorial control away from you, the fact that your control will be reused, without much effort from your part makes up for it.

When metadata holds prominence 

Metadata is often considered to be a part of the page content, it encompasses the microdata such as ad targeting, meta tags and JSON LD. When content is shared on multiple platforms, the metadata becomes a prominent part of the back-end, as opposed to the front-end. So, metadata would only be shared on different publishing platforms when it is decoupled, similar to the typical content. 

When redirects are not essential 

The redirect logic only adds complexity to the decoupled architecture. So, it would only be prudent for you to decouple when you do not need control over the redirects and your architecture will support multiple redirects rules being combined as one.

When Drupal is bringing in more work 

Drupal can be as easy to use as it can become a hassle, this depends on your perception of it. For many, Drupal seems to bring in more work than not. The many built-in features are the cause of it. The node edits, tabs and screens, you would not use all of them, so they just add to your workload because you would always be working around them. 

The simple example of evites would help you understand this better. The content structure would be easy to build, however, creating the evite, its customisation along with the addition of the recipient, preview and actually sending it is a whole other ball game. In such a scenario, decoupling helps ease the work.

When you have a static menu

The traditional Drupal can effectively manage your menu lists, while doing the same in the Decoupled Drupal can become tricky. It is always preferable to avoid complexities as much as possible, so if your site has a static menu, which can be created in the front-end application, decoupled Drupal would suit you to the T.

If you and your web applications are aligning with the aforementioned scenarios, then decoupling can be beneficial for you. If not, well you are intelligent enough to answer that. 

When Not to Decouple?

Decoupled Drupal architecture indeed paints a prettier picture that is more than appealing. After reading up till now, you might have made up your mind to take on the Decoupled approach and part with the coupled Drupal and you might even be right. The decoupled Drupal could be the right choice for you, but you cannot be totally sure of that without taking into consideration the challenges it is going to dredge up for you and your site. Have a look at these first and then decide for yourself. 

When you do not want to increase costs 

The foremost consideration when deciding on a project has to be its financial implications. Whether your pocket allows you to take it on is one of the most crucial questions to ask. Although Drupal is open source, requiring little to no costs of implementation, Decoupled Drupal is a whole other ball game, since you will be building a front-end that is entirely or partially independent of Drupal. And this is the reason why decoupling becomes the opposite of cost-effective. 

  • Features that would have been free would need to be built from scratch by your developers like Website Preview and this costs money.
  • The creation of a sitemap is often done by using a third party XML sitemap application, developing it on your own would cost so much more.
  • The creation of a good API that would aid in future developments rather than constrain them costs more money.
  • The decoupling team also becomes an expensive affair since more number of developers need to be hired.

Overall, the Decoupled Drupal requires massive infrastructural investments simply because you will be losing a high degree of Drupal’s out-of-the-box functionality. So, the question comes again, can you afford it?

When you do not want to increase complexity 

Decoupled Drupal comes with a 180° change and this change mandates another 180° change in the mindset of the developers and the content authors. It would be suffice to say that it becomes complex. The simple fact that editors would not be creating pages, but reusable content that is well-structured can become a lot to digest. 

On top of this, the infrastructure becomes cumbersome and complex as well. The simplest of tasks like previewing content before publishing it is no longer an option that is available. Since the content is to be posted on multifarious platforms, the task would be meaningless anyway. 
You would also need to be extra vigilant about the coding, if the front-end logic is encoded in the API, the recipe is going to burn your tastebuds. 

Taking on the complexity of Decoupled Drupal would only turn out to be prudent, when you have multiple sites and multiple consumers. 

When you do not want to lose page control 

Control is another thing you part with along with Drupal’s out-of-the-box functionality. If you think that, as an editor, you will have free reins over the placement of your content on the page, then you, my friend, are mistaken. Editors have non-existent control over the presentation of their content, the URL included. And if you want to have the control, it can be done by certain tools. However, the process to get it done would be extremely complex.

When you do not want a web of systems

When you decouple, you don’t just do it for an app or a site. So, when you decouple, there is a high likelihood that your team is going to build much more than a website and a JS app, rather a web of systems. These networks require a lot of build and testing mechanisms and that adds to the complexity of Decoupled Drupal. Then, there is the issue of human intervention. There are many decoupled sites that manually integrate the API, which becomes a hassle when the number of clients is on the higher side.

Continuing on the point of complexity, Decoupled Drupal creates a web of systems. It would seem to work until you have to debug. Once that point comes, the web of systems turns into a nightmare because you do not know where to look. Fixing a broken link in a web is far more difficult, since you can’t be sure whether the problem lies in the API or the request.

The Right Choice 

Yes, Decoupled Drupal demands a lot of work and it is as costly as it is time-consuming, however, its benefits easily trump all the drawbacks. 

Yes, Decoupled Drupal is going to increase your costs initially, but in the long run, it would reduce your overall development costs.

Yes, Decoupled Drupal would require a lot of getting used to, but once you are used to it, you will only reap the benefits of the JavaScript powered front-end. 

I would say that Decoupled Drupal is always going to be the right choice as long as you know that you can and will overcome its drawbacks. Regardless, if you believe that your current monolithic Drupal is too good to part with and it is accomplishing all your goals, you might have to re-think the decision of decoupling. It would only serve you its benefits, when you actually have a need for it. These success stories on Decoupled Drupal would give you a glimpse of your future project and its success. So, what will your choice be?

blog banner blog image Decoupled Drupal Architecture Decoupled Drupal Drupal Blog Type Articles Is it a good read ? On

Lullabot: Lullabot Podcast: The Gin Admin Theme: A Look into Drupal's Future UI?

Thu, 11/05/2020 - 22:43

Matt and Mike talk with Sascha Eggenberger about the Gin admin theme, including its editorial interface changes, relationship to the Claro theme, future and more!

Lucius Digital: Drupal Paragraphs: let content managers easily choose a color for background and text in each row/section/block/component

Thu, 11/05/2020 - 09:59
Nowadays I use Paragraphs in almost every Drupal project: it's very flexible, has a professional ecosystem, and content managers love it. Also, I never ran into a brick wall when it came to new user stories from product owners. To choose a background -and text color per paragraph (or row/section/block/component) is something áll Drupal content managers want. So here is an explanation on how I implement that. This works in Drupal 8 and 9. PHP 7.4 for Drupal 6 Long-Term Support

Thu, 11/05/2020 - 07:33

This is a bit of an update to our update to PHP 7 that we did awhile back.

Last week we contacted all of our clients to announce our PHP 7.4 upgrade plans.

Much like the update to accomodate PHP 7, this update will necessitate some changes for some of our Drupal 6 clients.

Thankfully the scope of changes seems to be a bit smaller so far.

The important thing to note is that we are continuing to make changes to keep Drupal 6 and important contrib modules current with modern, supported (and secure) versions of PHP!

Read on to find out more! blog: What’s new on - September 2020

Wed, 11/04/2020 - 20:04

Read our roadmap to understand how this work falls into priorities set by the Drupal Association with direction and collaboration from the Board and community. You can also review the Drupal project roadmap.

We're trying something new for our September update - a video! Let us know if you like this format in the comments.

Embedded below is a video we sent out to our Supporting Partners about the engineering initiatives that their support funded in September.

Here's what you'll learn about:

  • The issue fork and merge request beta - which makes Drupal contribution faster and easier, especially for new contributors.
  • The lazy-load initiative - which will make all Drupal sites on 9.1 and beyond faster.
  • Composer 2 support - Drupal now fully supports being built with Composer 2, which is much faster and less memory-hungry than Composer 1.
  • The Auto-Updates contribution week, which the DA held with community contributors from inside and outside of Drupal.
  • New efforts to match make organizations who want to contribute with initiatives that need help.


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

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

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

Advomatic: AdvoTalk: What should you do with your Drupal 7 website?

Wed, 11/04/2020 - 18:16

  Sarah Durham (00:02): Hey everybody. Welcome to today’s webinar. I am Sarah Durham, and I am going to briefly introduce my colleagues. They will talk a little bit more in a minute and also we’d love you to introduce yourself as people start to arrive. If you are comfortable doing so, you’ll see a ...

The post AdvoTalk: What should you do with your Drupal 7 website? appeared first on Advomatic.

Drudesk: How to speed up your website with the Quicklink module for Drupal 8

Wed, 11/04/2020 - 14:38

Wondering if you need the Quicklink module for the Drupal 8 website? Wonder no more — you need this module, and we will explain why.

To attract and keep the attention of users on the Internet, you need to apply a lot of effort and ingenuity. One of the key user expectations is that your site loads quickly.

Specbee: How to Import External Feeds into your Drupal 9 Website with the Feeds Module

Tue, 11/03/2020 - 14:00
How to Import External Feeds into your Drupal 9 Website with the Feeds Module Megha Kundar 03 Nov, 2020 Top 10 best practices for designing a perfect UX for your mobile app

As a developer, you will come across several situations when you need to import data from external sources. Sometimes you will need to import data from more than one source into your Drupal 9 website. The Feeds module in Drupal is a simple, no-fuss module that enables even non-technical users to import content from different data sources. What makes it simpler than other Drupal modules like the Migrate module, is that the entire import process is done through Drupal’s UI. It delivers content to you the way you want it as soon as it is available.
Many websites import RSS / XML feeds from third party sites. In this blog, we are going to get a news feed imported through this 3rd party API that provides data in json format with the help of the Feeds module in Drupal 9

Installing the Feeds Module

The Feeds Drupal 9 module lets you import data from different formats like CSV, XML, JSON, RSS, etc. into nodes, users, and taxonomy terms via the UI.
1.Install the Feeds module (Here we will be using composer)

composer require 'drupal/feeds:^3.0@alpha'

2. Here, we are using JSON feeds for importing data. So, we require a JSON parser which will need us to install one more module which is the Feeds extensible parser. Best way to install this module is by using composer because it downloads all required libraries. (You can also skip the first step if you're downloading using composer as feeds will be a dependency for the feed_ex module).

composer require 'drupal/feeds_ex:^1.0@alpha'

Note : If you're not using composer to install then the libraries required by this module can also be installed with the Ludwig module. Install the Ludwig module and then go to /admin/reports/packages for further instructions.

3.    Enable the feeds and feeds_ex (Feeds Extensible Parsers) module either by using drush or through UI.

Configuring and Implementing the Feeds Module

Here, we are going to import the data from website articles (Topics related to “Top headlines from TechCrunch right now”) which is exposed in JSON format shown in the below screenshot. 

To get this news data we need to login to the website and get an API key. Next, select the topics for which you wish to import the data to your website.

Looking at the API, lets create a content type where our data needs to be imported.

Creating a Content Type 

Here, I have created a new content type called as “News”. Choose the field type according to your JSON for which data needs to be migrated. 

In the above screenshot, we have chosen simple fields for importing the data like Author which is Text(plain) field for the importing data from JSON key author

As you see in the above screenshot, we have added the Feeds item field of type Feed and chosen the feed type accordingly. We will be learning how to create a Feed type in the next section below.

Creating a Feed Type 

Follow the below steps to create a feed type.

  1. Navigate to Feeds overview page (/admin/structure/feeds). You can see all the feeds listed in this page.I have already created 2 feeds. Here I am going to be using News feeds. You can create your own feed type by clicking on Add feed type. 
  2.  When editing feed type or adding new feed type, we will see the below options.
  • Basic settings
    Let’s configure the Basic settings for the feed type, First, provide the Name, Description and Explanation or submission guidelines for the feed type.        

    Import period (shown in the below settings tab) helps you choose how often the import should run. This will be done through a cron job. If you select Off then the import will be done manually.

  • The Fetcher settings option shows where you’re importing the content or fetching the content from.
     It provides 3 options to choose from,
  1. Directory :- Import the content from a file or a series of files already on your website.
  2. Download from URL :- Import the content from url (Which we will be choosing in our case).
  3. Upload file :- Import content from a file.

                Based on the Fetcher selected, we will have to configure the Fetcher settings. For the secondary option of fetcher settings, we have the below list of settings.

Configure secondary settings accordingly.

•    Parser lets you configure the format of the feed. Here we have many options to choose from like CSV, HTML, OPML, JsonPath (which is our setting), etc. Choose the one from the dropdown menu according to your feed format.
Based on the parser selected, we will have to configure the parser settings. In our case we don’t have any parser settings for parsers of type JsonPath.
•    Processor settings show configurations of the type of content the feed will create.

Similarly, we have a secondary settings option for processor as shown in the image below.

Configure your secondary settings according to the requirement.
The below screenshot shows the primary settings of fetcher, parser and processor.

3. Mapping sources to target

  • Context 

The help text says base query to run, which shows root or base of the data to be targeted to import the feeds as content. In our example, we have configured as “$.articles.*” because our data resides inside the article key. Look at this path documentation to configure yours.

  • Field Mappings

Now, we can configure the Feeds to decide which value pulled in from the JSON should map to which field on the Drupal news content type.
These targets are the Drupal data fields and are pulled in based on the processor you select when creating the feed type. You can also configure other settings for the particular mappings of the fields like Language, filter format (applicable for text formatted fields), unique (unique identifier used to track if the content is new or existing one), etc.
For example, if we want to import the JSON feed news article content title as Drupal news content title field then target will be the Drupal Title field and source will be JSON news article title key as shown in below screenshot.

Here we are using the mapping configuration as shown in the below screenshot.

You can also clone the feed type using the Entity clone Drupal module that is also supported in Drupal 9.

Creating a Feed

To create a feed, navigate to content -> Feeds tab -> add feed -> select the feed type

I have already created one for News. To create a new feed, click on the + Add feed button and configure the feed as required. For our blog, we have configured as shown in the below screenshot.

After the configuration, click on Save and Import. This will import the feeds as content. When the data is getting imported, you will see the processing status as shown in the below screenshot.

Once the JSON data gets migrated to content, we can see the content added to the news content type as shown in the screenshot below.

Now, let’s compare the imported content with feeds.

    Source Content from the techcrunch article      The content imported with the Feeds module

For more detailed information you can refer to this guide.

Additional modules to extend the Feeds module 

•    Feeds Tamper module helps you modify and update he source data before it gets imported to your website.
•    Feeds extensible parsers contains a set of parsers like XPath XML & HTML, JSONPath JSON & JSON lines parser, etc.
•    Feeds Import Preview module lets you see the content in your source before importing it.
•    Commerce Feeds module helps you in importing products to your Drupal Commerce site.

The Drupal 9 Feeds module and its extendable suite of modules offers tons of capabilities other than just importing data from external sources. It extremely flexible and can also be further extended to suit every requirement. If you’re looking for further assistance in importing data to your Drupal website, contact our Drupal experts today!

Drupal Planet Drupal 9 Module Drupal 9 Drupal Tutorial Shefali ShettyApr 05, 2017 Subscribe For Our Newsletter And Stay Updated Subscribe

Leave us a Comment

  Shefali ShettyApr 05, 2017 Recent Posts Image How to Import External Feeds into your Drupal 9 Website with the Feeds Module Image What To Expect From Drupal 9.1 Image All about Progressive Web Apps and Implementing it in Drupal 9 Want to extract the maximum out of Drupal? TALK TO US Featured Success Stories

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


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


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


Acquia Developer Center Blog: Acquia Cloud IDE is the Best Drupal Development Environment

Mon, 11/02/2020 - 17:04
Acquia Cloud IDE is the Best Drupal Development Environment Matthew Grasmick Mon, 11/02/2020 - 11:39

Incredulous? Let me explain.

Setting up a local development environment for Drupal has always been painful. There are so many options out there (Lando, Drupal VM, Docker, DDEV, Docksal, etc.) They each have their pros and cons, but they all share a common characteristic: they run on your own computer. This creates a set of inescapable challenges.

With every local development solution, you have to download, install and troubleshoot. Troubleshooting is made especially difficult because your computer isn't exactly like everyone else's. Your problems are unique because your computer is unique. You're either on Windows, Mac or Linux. You have unique directory structures, unique hardware and unique security concerns.

Acquia Cloud IDE is the solution. It's the only Cloud-based IDE for Drupal. We've done all the configuration and optimizing for you.

With Cloud IDE, you still have your own development environment, but now it’s in the Cloud. That means you don’t have to download, install or troubleshoot software on your own machine. Don’t worry about Windows, admin privileges, slow hardware or firewalls. Acquia Cloud Platform will spin up a brand new environment for you and it will work “out of the box.”

You can download modules, themes, or really whatever you want. You can write code, sync easily with Acquia Cloud, or integrate with any third party service you’d like. It’s already got everything installed that you could need for development. Composer, Drush, NPM, you name it. You can even use Xdebug right out of the box. It “just works.”

That’s why it’s the best development environment for building Drupal applications. You won’t find an easier solution.


The Value of a Fast and Simple Dev Workflow

For a single engineer, Cloud IDE can materially improve daily life. Having a fast, reliable and ready-to-go environment means less time head scratching and more time coding.

It’s a stack that you don’t need to maintain or update. No more “Well, it works on my machine,” or “Can you help me with this error?”

Adopting Cloud IDE across an entire development team multiplies its impact. Standardizing on Cloud IDE means more efficient development, faster onboarding and scalable teams. Just ask Advanced Micro Devices (AMD). In their recent presentation at Acquia Engage 2020, members of AMD developer team, Andy Glover and Peter Wood shared how Acquia Cloud IDE revolutionized AMD’s development process. Here’s what they said:

“As a Windows shop, Drupal development was slow, frustrating and required a lot of manual configuration. Cloud IDE has freed up developer time to actually focus on development. The remote environments feel blazing fast by comparison, and our laptops are all faster without running Docker and Drupal on them”

Before they standardized on Cloud IDE, the AMD team often dealt with frustrating inconsistencies in their workflow. Development was frequently halted while one team member tried to figure out why they were seeing errors, but the rest weren’t. Each developer was dealing with solving separate, unique errors on their own bespoke set up. By switching to Cloud IDE’s browser-based environment, developers could write, test and deploy new code at record speeds!

If you registered for Acquia Engage, you can login to listen to the full story that AMD shared in “Build better, faster and more efficiently with Drupal.”

How Can I Get It?

If you’re not an Acquia customer, request a personalized demo of Cloud IDE.

Otherwise, you likely already have access to a Cloud IDE! All of our Acquia Site Factory and Acquia Cloud Platform customers get at least one Cloud IDE included in their subscription. Talk to your account manager or file a support ticket if you’d like more.

Where can I learn more?

If you’d like to learn more, take a look at:

Tag1 Consulting: Core Confidential with Angie Byron (webchick) : Learning about 15 Years of Drupal Contribution - Pt. 1

Mon, 11/02/2020 - 15:54

Open-source software development isn't easy. There are few people who know this more intimately well than Angie Byron (webchick), who is one of the best-known community leaders in the Drupal ecosystem and Senior Director, Product and Community Development at Acquia. Over the course of Angie's fifteen years in Drupal contribution, the content management system has undergone a series of disruptive and significant changes that have reinvented the community multiple times over. As cat-herder of over 30,000 developers all around the world, Angie has had her fair share of experiences in Drupal core development. Drupal is notorious for its "everyone has a voice" approach to open-source development, but it isn't easy to reach consensus across thousands of people with different backgrounds and opinions. In addition, Drupal has witnessed countless paradigm shifts in its lengthy history, both in the surrounding world of web development and in its internal workings. As Drupal has grown to power over two percent of the websites on the entire internet, many new workflows and governance structures have had to be put in place to guarantee the continued longevity of the Drupal community. In addition, with end-of-life quickly approaching for Drupal 7, contributors now have to juggle a...

Read more preston Mon, 11/02/2020 - 06:54 Protecting Website Content: Copy Prevention module for your Drupal site

Mon, 11/02/2020 - 15:27

Anyone who creates unique content knows that it is very difficult to protect it from being copied. One option to protect it is to use the Copy Prevention module.

You work hard to create unique content for your site and add individual images, but one sunny day someone visits your site and just copies it all. You spent days developing an individual and high-quality website, and someone just stole it from you in 5 minutes. Now what you have already created is no longer considered unique.

In order to avoid such situations, there is a simple solution — installing the Drupal Copy Prevention module. Today, web developers from Wishdesk will share the Copy Prevention module's features and how to install it on your website to protect your content.

What is the Copy Prevention module?

Last updated: 17 September 2020