Drupal

Argue ProCons

New Drupal Modules - 25 September 2017 - 3:41am

Provides a subentity list with arguments for a topic represented by a node.

Categories: Drupal

Annertech: Annertechies coming to DrupalCon Vienna

Planet Drupal - 25 September 2017 - 3:37am
Annertechies coming to DrupalCon Vienna DrupalCon Vienna is starting this week and, as usual, most of the Annertechies will be there in force. This year we are once again delighted to be presenting five sessions at DrupalCon. Here's a quick roundup of our talks and why you won't want to miss them.
Categories: Drupal

Pardot User Register

New Drupal Modules - 25 September 2017 - 3:07am

Pardot User Registration module helps users or site builders to integrate Drupal User Registration with Pardot. All that is needed is the setup of Form Handler URL in the defined Drupal administration page.

Prerequisite
1. User Registration fields that are meant to be captured in Pardot has to be created along with Form Handler.
2. Pardot User Register module is downloaded, installed and enabled.

Categories: Drupal

Drupal Association blog: Drupal Business Survey 2017

Planet Drupal - 25 September 2017 - 3:02am

The Drupal Business Survey 2017 shows that Drupal has a steady position in the market, and Drupal 8 has secured its role as the most popular version for new Drupal projects. Further, Drupal is often becoming part of a larger set of solutions.

The Drupal Business Survey is an annual survey that aims to give insights into the key issues that Drupal agency owners and company leaders worldwide face. The survey is an initiative of Exove, One Shoe and the Drupal Association and has been carried out this year for the second time. It covers topics about Drupal business in general, Drupal projects and talent needs. This article summarizes the most important findings along with commentary and insights from a total of 239 respondents.

Drupal is growing steadily

The Drupal Business Survey gleaned its data for 2017 from 239 respondents in CEO/COO/CTO/founder role (87%), director role (4.6%) or management role (4.6%), working at Drupal companies with a total of 300 offices spread around the globe. The most popular office location (30.1%) was USA. The second most popular with 12.1% was UK, and after that Germany, Netherlands, India, Canada and France. There were respondents from Africa, Asia, Europe, North America, South America and Oceania.

Analysis of the data made immediately clear that Drupal is a healthy business:

Drupal project pipeline grows

For almost half of the respondents (48.5%) the Drupal project pipeline grew within the last year. For 28.9% it stayed roughly the same, and for 22.6% the pipeline shrank.

Size of Drupal projects grows

For a majority (52.3%) of the respondents the average size of Drupal project deals grew. For about one third (31.4%) the Drupal deal size stayed roughly the same, and for only 16.3% the size of deals shrank.

Drupal’s project win rate stays roughly the same

Despite the increasing competition in the CMS market, for many (46.4%) of the companies their Drupal project win rate has stayed on the same level over the last year, and about a third (34.7%) have managed to grow their win rate. For less than a fifth of the companies (18.8%) the win rate had decreased.

Drupal’s position as a high-demand service platform is steady, especially for projects in the Charities and Non-Profit sector, which is catered to by two thirds (64.9%) of the respondents. Other popular industries that use Drupal are Government & Public Administration (56.1%) and Healthcare & Medicine (49.4%). There are no major differences in industries served by Drupal companies compared to the 2016 survey results.  

Choosing Drupal

When choosing the right platform, Drupal clients trust the technical provider’s expertise: Drupal is often chosen by the clients as a result of the provider’s recommendation. In some cases the client’s previous experience or familiarity with Drupal is the definitive factor.

Besides Drupal being open-source and free of licensing fees, the definitive reasons for choosing Drupal are that Drupal is a reliable and flexible CMS choice with a strong reputation:

Without -most often than not- being able to precisely explain the reasons for which they prefer Drupal, those who do, sense that it is a better solution for their business; we shall imagine that this is due to the image of the CMS, which evokes a more robust, and serious CMS than the others.

Can do anything. Secure.

Choosing the company

When Drupal itself is less the dominating factor for the client, other unique aspects are often key factor for clients choosing a supplier, agency, or partner. The respondents mentioned that trust, commitment, quality, level of service, full service proposition, technical expertise, good reputation, and references were important factors for client decision making.

Drupal 8 has a strong place in the market

Drupal 8, the newest version of the CMS, seems to have taken a strong place in the market. The respondents’ new Drupal projects were most commonly (38.1%) built on Drupal 8. One fourth of the respondents stated that they build mostly with both Drupal 8 and some with Drupal 7. For 18% of the respondents most new project were built with Drupal 7 and some with Drupal 8. A few (6.7%) of the respondents said their new projects are equally often built with Drupal 7 and Drupal 8. 12.1% still built all of their new projects with Drupal 7.

Drupal companies broaden their services, skill-sets, techniques and expertise

Remarkably, despite the popularity of Drupal, the survey shows that a lot of Drupal companies have changed their business model over the last year to widen their services and respond to the demand.  

The most common way of changing the business model was by expanding services beyond building Drupal websites (35,1%). The data shows that companies start to offer more services, expand their technology stack and work with multiple CMS platforms.

The main reasons behind the changes were changing market conditions (40,0%) or to willingness to grow the pipeline better or faster (49,4%). A respondent explains: “Drupal is too restricted to cover all the market's needs; furthermore, adding other services allows us to expand our clientele and thus revenues.”

More services

In addition to pure web development – coding the sites – most of the companies provide services such as support, system integration, user experience design, visual design, hosting, and mobile development.

Changing the technology stack

The companies also found adding other technologies as a useful way of expanding the technology stack.

More than half of the respondents’ companies used also Node.js, while Angular (43.5%), Symfony (42.3%) and React.js (33.9%) were also commonly used technologies within the respondents. Some used also Laravel (17.2%), Vue.js (9.6%) and Django (5.9%).

Expanding their services by adding other services and CMS platforms to their toolkit

Almost half of the companies (45.2%) have added other CMS platforms to expand their services and getting variety to projects. WordPress is the most usual (54.67%) addition to the toolkit, serving particularly smaller projects, with Magento eCommerce platform and Grav CMS following. For most respondents (69.6%), the reason for using more than one CMS tool is being able to use the tool best suited for the project. For almost the half (40.2%) the reason arose from the client's’ wishes on the tool.

“WordPress is more popular, and customers want it because of the user experience.”

“There's still a battle out there between Drupal and WordPress. Clients are not enough informed about the differences, so their opinion is often based on information and visions by previous suppliers”

“We’re adding Adobe and wordpress. Looking into JS frameworks.”  

Drupal in a landscape of solutions

Drupal is widely considered as one of the most popular options in the CMS landscape. However, while digital solutions have become more complex, Drupal increasingly often serves as a part of a larger set of solutions. The survey data shows that Drupal companies do this in the belief that the company sells solutions rather than technology.  

There’s a broad range of options available for companies to build platforms. Every Drupal organization seeks different combinations of software products and programming languages that they seem most important for their projects. There are endless options that excel in their own right.

Our clients rarely come asking for Drupal (10% of the time ). But our technical prowess is a big part of their choice. That skill just happens to be in Drupal due to our own choice of platforms.

[Our Drupal expertise is the most definitive factor] when clients approach us for Drupal projects, if Drupal is not the main reason to approach us (the most common case) then Drupal expertise is irrelevant.

When it is a Drupal project the expertise is important but we no longer sell Drupal as a major part of projects. We just use it. We now sell the solution.

I sell solutions to digital problems, not solutions to Drupal problems.

The study made it clear that there are often other definitive factors than Drupal expertise affecting the client’s decision of choosing agencies. The clients reportedly value vendor’s portfolio and references of previous projects, reputation, communication, and services that differentiate the agency from its peers.

The Drupal talent factor

According to the survey, Drupal talent is hard to find and takes a lot of work. Only fraction (10.9%) of the companies say that they find Drupal talent easily. Compared to last year, the demand for Drupal talent at responding companies seems to be split between decreasing (23.4%) and increasing (25.5%) demand, with demand staying about the same at 36.8%.

With Drupal 8 gaining more and more popularity, most respondents say that Drupal 8 skills are somewhat in demand (38.1%) or high demand (33.5%). 15.9% say that Drupal 8 skills are not in demand.

Most respondents ranked the number of skilled Drupal 8 developers as average (40.2%). The responses indicate that more Drupal talent is needed, especially skilled Drupal 8 developers, due to the fact that Drupal 8 is more complex than its predecessors:

2016/17 and D8 has been a big shakeout for talent in Drupal. A lot of people who could operate in commercial Drupal delivery in 2012-2015 (with demand outstripping supply markedly) simply will not be viable candidates for Drupal work in 2018. There is no 'easy" work left and many people who came in during the good times will not be able to sustain careers in the new world.

The evolution of the CMS marketplace to favor more comprehensive and thus also more complex solutions is favoring bigger companies with stronger competences through number of experts in specific fields. This can be a struggle for small vendors, as mastering clients’ needs requires more expertise than is available on their staff:

Demand, as a whole, for Drupal seems to be significantly dropping as the increased complexity of each major release of Drupal cuts off greater and greater numbers of the ‘do-it-themselves’ business owning client/builder types. These types are prime candidates for initially using Drupal and then later turning their Drupal site over to a professional company.

Conclusion

Based on the study results, it is safe to say that Drupal has a steady position in the market, and Drupal 8 has secured its role as the most popular version for new Drupal projects.

The content management market is shifting towards more comprehensive and also complex solutions. Drupal agencies are well positioned to respond to this trend due to modern Drupal 8 architecture and also by combining Drupal into larger solutions. This drives Drupal business into larger deals and allows more long-term partnerships with the clients, thus giving financial stability to the companies and also to the community.

On the other end of the market, Drupal also faces competition from low-end solutions such as Wordpress. Some of the agencies now offering other content management solutions, Wordpress included.

The market might be challenging for smaller companies with only one CMS in their toolkit. Companies that can react to changing market conditions and provide a variety of solutions are going to succeed. Additiionally, companies that are able to distinguish themselves from other vendors through a good set of services, specialisation, or excellent customer service will flourish. This is all part of a natural evolution of any digital platform marketplace and it should be seen as a good juncture to raise the Drupal agencies to the next level.

Talent finding challenges indicate that there will be a need for multi-skilled developers with very good technical expertise.

Want to go in-depth?

More detailed results of the survey will be published at the DrupalCon Vienna CEO Dinner on Wednesday, September 27th. The presentation will become available for download afterwards.

-----

For more information, please contact Janne Kalliola (janne@exove.fi) or Michel van Velde (michel.vanvelde@oneshoe.com)

About Exove

Exove delivers digital growth. We help our clients to grow their digital business by designing and building solutions with agile manner, service design methodologies, and open technologies. Our clients include Sanoma, Fiskars, Neste, Informa, Trimble, and Finnlines. We serve also start-up companies, unions and public sector. Exove has offices in Helsinki, Oulu and Tampere, Finland; Tallinn, Estonia; and London, United Kingdom. For more information, please visit www.exove.com.

About One Shoe

One Shoe is an integrated advertising and digital agency with more than 10 years experience in Drupal. With more than 40 specialists, One Shoe combines strategy, UX, design, advertising, web and mobile development to deliver unique results for international clients like DHL, Shell, Sanofi, LeasePlan, MedaPharma and many more. For more information, please visit www.oneshoe.com.

About the Drupal Association

The Drupal Association is a non-profit organization headquartered in Portland, OR, USA. It helps the Drupal project and community thrive with funding, infrastructure, and events. Its vision is to help create spaces where anyone, anywhere, can use Drupal to build ambitious digital experiences. For more information, please visit drupal.org/association.

Categories: Drupal

Data Encryption

New Drupal Modules - 25 September 2017 - 2:46am

Overview:
This is developer friendly module which will used for Encryption/Decryption data based in the Key & Encryption profile.

Installation:
Download the module and extract it to the modules directory. Install it as any Drupal contributed module.

Configure/Setup all the dependent modules as per there installation instructions.

Usage:
Inject the below service in your module for custom usage:

<?php
use Drupal\data_encryption\Services\DataEncryptionService;

Categories: Drupal

Adobe DTM for Drupal

New Drupal Modules - 25 September 2017 - 12:50am

This Adobe DTM module allows the use of Adobe Systems' Dynamic Tag Manager hosted application to insert new tags into your Drupal website.

Categories: Drupal

Appnovation Technologies: Appnovator Spotlight: Tim Kirby

Planet Drupal - 25 September 2017 - 12:00am
Appnovator Spotlight: Tim Kirby Who are you? What's your story? I'm Tim Kirby, I come from a creative arts background, and started in multimedia and web site builds in 1996. I worked full time in Macromedia's Director for a couple of years, before moving to hardware and software design a few years later - building interactive digital signage systems that would respond to the touch...
Categories: Drupal

PreviousNext: Start testing your contrib and client projects on Drupal 8.4.x now!

Planet Drupal - 24 September 2017 - 4:26pm
Share:

Drupal 8.4.0 comes out in October, and at that time 8.3.x will be end-of-life (EOL).

There are two major vendor updates in 8.4.0 so the time to test your contrib and client projects is now.

In this post we talk about the coming changes and how to test your client and contrib projects.

by Lee Rowlands / 25 September 2017

The two major vendor updates in Drupal 8.4.0 are as follows:

You can start testing now by updating to Drupal 8.4.0-rc2.

Symfony 3.x

If your project interacts Symfony directly at the lower level (rather than using Drupal core APIs that in turn use Symfony), you should be sure to review your code to make sure you're not using any of the APIs impacted by the BC breaks between 2.x and 3.x. Hopefully, your automated testing will reveal these regressions for you (you have automated testing right?). See the Symfony change list for the details of BC breaks.

One thing to note with the Symfony update is that whilst core dependencies were updated, your project may rely on other third-party PHP libraries that have dependencies on Symfony 2.x components. This may cause you issues with your update - and require you to update other dependencies at the same time - including drush - so testing sooner rather than later is recommended. If you find you're having issues with composer dependencies, we have another blog post dedicated to debugging them.

jQuery 3.x

While it's most likely that you'll have automated tests to catch any issues with the Symfony upgrade, it's less likely that you'll have test coverage for the jQuery update, as JavaScript test coverage is typically low in Drupal projects, particularly in contrib modules.

Of note in the jQuery update are several BC breaks - listed here http://blog.jquery.com/2016/06/09/jquery-3-0-final-released/ and http://jquery.com/upgrade-guide/3.0/. This may have a major impact on contrib projects that are heavy on JavaScript - and your client project code if you have a large amount of custom JavaScript, both in modules and your theme.

Of particular interest

  • .load removed
  • .unload removed
  • .error removed
  • .bind deprecated (use .on)
  • .delegate deprecated
  • .on('ready', function() {}) removed
  • jQuery('#') and .find('#') throw invalid syntax errors
  • .andSelf() removed (use .addBack())

A recommended approach to auditing and tackling this is to add the jQuery migrate plugin to your project, and begin testing whilst watching the JavaScript console to detect deprecation notices thrown from the plugin.

A word on testing

Finally, if you are reading this and thinking, I really need to add some test coverage to my project, one of our team Sam Becker is presenting on all things testing at Drupalcon Vienna this week. If you can't wait that long, check out his session from the last Drupal South.

Tagged Testing, Drupal 8, Composer, jQuery

Posted by Lee Rowlands
Senior Drupal Developer

Dated 25 September 2017

Add new comment
Categories: Drupal

workout

New Drupal Modules - 24 September 2017 - 4:25pm

Workout is a set of drush commands used to flush out error and warning messages that get created when pages are rendered for viewing.

Attempts to Exercise / Load every public page on a site anonymously.
You can pass in the number of pages to limit the processing to as arg1.

Workout is multi threaded. Each thread can Exercise / Load a web page.
This allows testing many pages at the same time.
This greatly reduces the amount of time required to load all the pages on a large site.

Categories: Drupal

exerciser

New Drupal Modules - 24 September 2017 - 4:15pm

Exerciser is a set of drush commands used to flush out error and warning messages that get created when pages are rendered for viewing.

Exerciser Exercises (renders) every page of a content type.
If no content type argument is supplied a list of all content types
will be displayed for your choice.

Exerciser can load pages on the same server its loaded on or another server for the same site.

Categories: Drupal

grouper

New Drupal Modules - 24 September 2017 - 4:00pm

Grouper Slicer and Dicer

Not to be confused with Bass O Matic 76

Grouper reports on php warnings and errors gathered by Drupals dblog watchdog module.
Without dblog being enabled this module will be of little use.

The module allows you to reproduce errors by clicking on a link to a page.

For pages with Access Denied warnings and menu links, Grouper
can load all the pages in order to reproduce warnings and errors.

Categories: Drupal

Jeff Geerling's Blog: Drupal Camp St. Louis 2017 is a wrap!

Planet Drupal - 24 September 2017 - 2:30pm

The St. Louis Drupal Users Group (STLDUG) just finished it's fourth Drupal Camp, held at UMSL yesterday. I had a great time meeting with everyone, and am excited for next year! Last year I had to miss the Camp due to unexpected surgery, but this year I was able to attend and even bring some of my photo gear, to take pictures (I love contributing to open source through means other than code!); here's the obligatory 'whole camp' photo:

You can view all my photos from the camp in an album on Flickr: Drupal Camp St. Louis 2017 photos by geerlingguy

Categories: Drupal

Bulk migrate taxonomy terms

New Drupal Modules - 24 September 2017 - 1:57pm

Ever had the need on your project to create a bunch of vocabularies and terms? Or even the need to maintain existing terms and vocabularies?

This module enables you to bulk create and/or update existing or new vocabularies and terms based on a simple two column CSV file.

The module is built upon Drupal Migrate and the UUID module to enable the updating of existing terms.

Release timeline:
Drupal 7 version should be out somewhere mid October.
Drupal 8 version, no visibility on a release yet.

Categories: Drupal

drunomics: Things to do around Drupalcon Vienna

Planet Drupal - 24 September 2017 - 3:28am

While the Drupalcon webseite has a good few pointers to the well-known major tourist attractions, as locals we'd like to share our knowledge about some of our favourite places with you! So here a few recommendations:

Viennese Wine and Heurige

If you stay for the weekend after the Con, you can join the Vienna Wine Hiking day, which I can highly recommend. There are 3 possible easy hikes through the vineyards with lots of options to stop for tasting gorgeous wine directly from the producers. Furthermore you may enjoy great views of the city even if the wheather is not that great!

If you stay long enough, don't miss it! You can find details and options at https://www.wien.info/en/shopping-wining-dining/wine/wine-trail

If you cannot join the wine hiking day, be sure to visit some Viennese "Heurige" (wine taverns). Good options would be the Schreiberhaus or a little bit closer to the city-center Sissy-Huber.

Otto Wagner Buildings

The famous Viennese Jugendstil architect Otto Wagner (and friends) has left lots of traces back in the city. Apart from some of the subway stations (you won't be able to miss them) we'd recommend looking at the following buildings at least from the outside:

Cafés & Restaurants

Kaffee Alt Wien: An interesting mixture between a traditional Vienese Cafe and a "Beisl" (pub). The food can be recommended too, simple but authentice Viennese dishes, like Gulasch, Schnitzel and a variety of sausages. Although the Kaffee Alt Wien is mentioned in travel guides, it has not lost its athmosphere and is visited by tourists and locals alike.

Flatchers: Great steaks for a reasonable price. There are two restaurants in the same street: A French bistro with georgous French athmosphere and a larger one in American style.

Brunnenmarkt: A local market in one of the lesser known districts, lots of immigrants of south-eastern Europe and Turkey run market booths and Cafés around a nice plaza. You'll find great athmosphere and good food options: Kent, Cafe Ando, Cay Cafe am Yppenplatz

Barfly's: A cuban style cocktail bar with authentic athmosphere and music!

 

Categories: Drupal

Dave Hall Consulting: Drupal Puppies

Planet Drupal - 24 September 2017 - 1:41am

Over the years Drupal distributions, or distros as they're more affectionately known, have evolved a lot. We started off passing around database dumps. Eventually we moved onto using installations profiles and features to share par-baked sites.

There are some signs that distros aren't working for people using them. Agencies often hack a distro to meet client requirements. This happens because it is often difficult to cleanly extend a distro. A content type might need extra fields or the logic in an alter hook may not be desired. This makes it difficult to maintain sites built on distros. Other times maintainers abandon their distributions. This leaves site owners with an unexpected maintenance burden.

We should recognise how people are using distros and try to cater to them better. My observations suggest there are 2 types of Drupal distributions; starter kits and targeted products.

Targeted products are easier to deal with. Increasingly monetising targeted distro products is done through a SaaS offering. The revenue can funds the ongoing development of the product. This can help ensure the project remains sustainable. There are signs that this is a viable way of building Drupal 8 based products. We should be encouraging companies to embrace a strategy built around open SaaS. Open Social is a great example of this approach. Releasing the distros demonstrates a commitment to the business model. Often the secret sauce isn't in the code, it is the team and services built around the product.

Many Drupal 7 based distros struggled to articulate their use case. It was difficult to know if they were a product, a demo or a community project that you extend. Open Atrium and Commerce Kickstart are examples of distros with an identity crisis. We need to reconceptualise most distros as "starter kits" or as I like to call them "puppies".

Why puppies? Once you take a puppy home it becomes your responsibility. Starter kits should be the same. You should never assume that a starter kit will offer an upgrade path from one release to the next. When you install a starter kit you are responsible for updating the modules yourself. You need to keep track of security releases. If your puppy leaves a mess on the carpet, no one else will clean it up.

Sites build on top of a starter kit should diverge from the original version. This shouldn't only be an expectation, it should be encouraged. Installing a starter kit is the starting point of building a unique fork.

Project pages should clearly state that users are buying a puppy. Prospective puppy owners should know if they're about to take home a little lap dog or one that will grow to the size of a pony that needs daily exercise. Puppy breeders (developers) should not feel compelled to do anything once releasing the puppy. That said, most users would like some documentation.

I know of several agencies and large organisations that are making use of starter kits. Let's support people who are adopting this approach. As a community we should acknowledge that distros aren't working. We should start working out how best to manage the transition to puppies.

Categories: Drupal

None title

New Drupal Modules - 23 September 2017 - 2:16pm

This lightweight modules makes it possible to write <none> in the node title field to hide the title.

Categories: Drupal

Commerce Store Domain

New Drupal Modules - 23 September 2017 - 6:04am

This module adds a Domain field to stores. It then uses this domain to resolve the current store.

This allows de.mystore.com to represent the German store. Drupal's language can also be configured to be negotiated by domain. This allows for one Drupal Commerce site and support for multiregional stores with their own domain.

Categories: Drupal

Menu Link Modal

New Drupal Modules - 23 September 2017 - 3:34am

Menu Link Modal adds functionality to open any internal link into modal window.

Setup

Install the module and dependent modules.

- Go to structure > Menus
- Edit any of the menu.
- Create on Add link / Edit any existing menu item.
- There will be a Modal settings fieldset.
- Click on checkbox "Open link in Modal".
- Adjust width and height, if you want to change.
- Save the menu item.

Visit the site and click on the link that you just make to open in modal.

Categories: Drupal

Block content machine name

New Drupal Modules - 23 September 2017 - 12:21am

Block content machine name adds machine_name field for block_content block
content type. Which is used to define the specific block template and class name
for that specific block. (Current module does not provide machine_name support to any other block content type.)

Block content machine name module requires [machine_name_widget] module.

Categories: Drupal

Palantir: Drupal 8 is Great for Sustaining Innovation

Planet Drupal - 22 September 2017 - 3:17pm
Drupal 8 is Great for Sustaining Innovation brandt Fri, 09/22/2017 - 17:17 Ken Rickard Sep 25, 2017

The #D8isGr8 blog series will focus on why we love Drupal 8 and how it provides solutions for our clients.

We want to make your project a success.

Let's Chat.

The first post in our series comes from Ken Rickard, Director of Professional Services.

I’ve been working with Drupal since version 4.5, starting in late 2004, working as an end user, product manager, developer, team lead, core contributor, sales engineer, and sales manager. Since its release in 2015, Palantir.net has been using Drupal 8 to provide solutions for ourselves and our clients.

In that time, we’ve started to identify the long-term benefits that really make Drupal 8 shine. While many of these benefits appear to be developer-centric, the story that they tell is how the platform helps organizations of all sizes to invest in sustained innovation.

From a business perspective, we can focus on three fundamental changes in Drupal 8.

The Release Cycle

Drupal 8 adopted a more standard semantic versioning that indicates the major version, API release, and feature release status of Drupal core. As of this writing, core stands at 8.3.7, and the 8.4.0 release is in beta testing.

Along with semantic versioning came a commitment to regular release cycles -- planned for every six months -- and a commitment to maintain backwards-compatibility. These changes make core releases more predictable, both for resourcing and implementation. We know when the next version is coming, what new features are included, and how any changes will affect our existing sites and code.

This predictability brings Drupal more in line with traditional software releases, and provides a huge benefit to contributors and customers alike.

Backwards Compatibility

With the new release cycle, the project finally has a proactive plan for dealing with backwards compatibility issues. Instead of major upgrades between versions, Drupal is prepared to offer incremental changes that foster long-term stability without sacrificing innovation.

We know in advance what elements have been marked as deprecated and when they are scheduled for removal. (Hint: largely when Drupal 9 development begins in earnest.)

Component Architecture

Perhaps even more than the first two features, the shift to using a library-based approach to code -- where essential components are integrated from external libraries -- gives organizations even more control over their innovations. Drupal now uses Composer and other modern PHP development practices, so we can decouple our code -- both front-end and back-end -- from Drupal specifics.

Since we can move large sections of Drupal code into standalone libraries, we can spend less time working through specifics of a Drupal implementation and focus instead on the technical and business problems that the software needs to solve.

Sustaining Innovation Through Open Source

Taken together, these three elements are powerful. Combined with the GPL open source license that allows anyone to use, improve, and share their code, we have an overall platform devoted to innovation. From a business standpoint, the long-term value of investment in Drupal 8 will be measured in years. Since the software is free to use, companies can invest in their teams and create an environment of sustained success through innovation.

We want to make your project a success.

Let's Chat.
Categories: Drupal

Pages

Subscribe to As If Productions aggregator - Drupal