Planet Drupal

Subscribe to Planet Drupal feed
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 15 hours 12 min ago

Commerce Guys: Drupal Commerce 2.0 released in time for DrupalCon Vienna

25 September 2017 - 7:30pm

We released Drupal Commerce 2.0-beta1 at DrupalCon Dublin one year ago. Over the next 9 months we tagged 6 more beta releases comprising over 500 commits by 70 different contributors working for at least 10 different companies. Now, just in time for DrupalCon Vienna, we have tagged the full 2.0 release, celebrating the achievement with Drupal contributors around the world on September 20th and 21st.


Celebrating Commerce 2.0 with Circle WF in Pancevo, Serbia.

Our release candidate phase was refreshingly uneventful (as you want it to be), giving us confidence to recommend developers begin using Drupal 8 and Commerce 2.x more broadly to develop their new eCommerce sites. Our team has contributed to a dozen projects directly, including architectural consulting and development. We also continue to see more case studies demonstrating how the new version is performing well at scale, making development teams more productive.

Additionally, not only has Commerce 2.x eliminated the need for half of the top 60 contributed modules in Commerce 1.x, many of the major contributed modules still required have seen their own releases or very active development to address important use cases. For example, we released a third beta of Commerce Shipping for Drupal 8 to support stores selling physical products with multiple shipments, flat rate, calculated rates and more. We continue to work on those feature modules ourselves (e.g. Commerce License / Recurring) and in partnership with other Drupal contributors (e.g. Commerce Stock) to make Commerce 2.x ready for more and more use cases.


Drupal Commerce deserves cake!

We're believe in Dries Buytaert's vision for Drupal as empowering ambitious digital experiences. For us that means continuing to improve Drupal Commerce to better support any company aspiring to grow their online sales. While our work on the project will never be "done", at this milestone, we couldn't help but pause to celebrate with a bit of cake.

If you'd like to join us in celebrating this achievement, we're hosting a release party with our whole team and our friends from Commerce Guys by Actualys on Tuesday, September 26th, at DrupalCon Vienna a short walk away from the venue. We've timed it for dinner between the opening reception at the venue and the party later in the evening, with drinks and food on us until the tab dries up. Stop by our booth to get your ticket / directions, and come find the dozens of contributors here at DrupalCon to share your Drupal Commerce story with them in turn.

Categories: Drupal

Gbyte blog: Image indexation and other new features of Simple XML sitemap 2.10

25 September 2017 - 3:35pm
New features of Simple XML sitemap Version 2.10 of Simple XML sitemap is mainly a feature release with only a few minor bugs fixed. The new features are the implementation of the changefreq parameter the ability to set an interval at which to regenerate the sitemap the ability to customize XML output the ability to add arbitrary links to the sitemap image indexation See the 8.x-2.10 release page for details.
Categories: Drupal

Mediacurrent: Ask an Open Source Security Expert: What Can We Learn From the Equifax Hack?

25 September 2017 - 11:50am

Although the most likely cause of the massive Equifax data breach was the firm’s own failure to patch a two-month-old bug, the inherent security of open source software has become a trending topic in tech news.

Mediacurrent’s resident expert, Open Source Security Lead Mark Shropshire, is well-informed to join the conversation. We asked him a few questions to get his take on recent events.
 

Categories: Drupal

Drupal Association blog: Evolving Community Governance - Survey Results and a Call to Action

25 September 2017 - 9:19am

These results and analysis were initially presented at the DrupalCon Vienna community summit on September 25, 2017.

Following numerous blog posts, official statements, community discussions, social media interactions, and Slack and IRC conversations over the last few months, there is a clear consensus that it is time for Drupal's community governance to evolve. We need to not only define what governance means to us as a community, but also clarify the roles and responsibilities of those within our community leadership and governance structures. We also need to draw clearer distinctions between the different forms of community, project, and technical governance, and make sure that everyone understands how they interact with and support each other.

Ultimately, this will need to be a collaborative process that involves all stakeholders, including Dries and the Drupal Association (especially where matters of legal and financial responsibility are concerned), but the first step is to create a framework so that the community can participate productively in the process. The question that remains to be answered is what that process will look like.

Results of the Governance Summit Survey

The Drupal Association, with help from Whitney Hess, conducted a Community Governance Summit survey in an effort to gain insight into how the community would like to proceed. 568 people responded to the survey, with most questions receiving between 200-250 responses. The Community Working Group (CWG) was given access to the raw results, which it in turn shared with David Hernandez, Nikki Stevens, and Adam Bergstein, who assisted with the writing of this blog post. We all agreed to keep any personally identifiable information from respondents confidential.

While none of the authors of this blog post were responsible for developing the survey or are trained statisticians, we did our best to analyze the results, which reflected a wide range of opinions and feelings about how the Drupal project and community is governed. While we did not feel the survey results pointed to any clear and actionable next steps, they were consistent with the feedback from the community discussions that were held this spring, which was that the process, in whatever form it takes, needs to be driven by the community.

To that end, we have worked with the Drupal Association to publish the survey data and, most importantly, make this call to action for a truly community-driven process. We are also making a sanitized version of the raw data available for download in OpenDocument format for anyone else to review and perform their own analysis. All comments and other free responses have been removed.

Selected Survey Highlights
  • 62% agreed that a governance summit is needed. Only 8% said definitely “no.”

  • 63% want the summit to be held online, so that members from all regions of our global community could participate.

  • 59% believe the summit should be overseen or facilitated by a professional governance expert, with the majority of write-ins requesting a neutral third-party facilitator not affiliated with the Drupal project or community.

  • Nearly 80% wanted the Drupal Association to provide financial support for the summit, with 36% indicating they would contribute to a crowdfunding campaign to help fund the summit.

  • About ¾ said that clarification of leadership roles and separation of project versus community governance roles should be prioritized at the summit. All of the options listed received the support of more than half of those who provided a response to this question:

    1. Clarification of leadership roles in the Drupal project (76%)

    2. Separation of project vs. community governance roles (73%)

    3. Update codes of conduct (63%)

    4. Overall community management (63%)

    5. More community-elected leadership positions throughout Drupal (60%)

    6. Clarify and update Community Working Group processes and policies (56%)

    7. Create core values statement (53%)

Percentages listed are of those who provided a response to that question, not of the total number of people who responded to the survey.

What’s Next: Getting Involved

Now is the time for people to get involved and drive the next steps in the process. We feel that as an open-source project, the governance of our community should be designed and implemented by members of that community in the most transparent and fair manner possible.

To that end, we feel that the best path forward is to create a volunteer working group that is representative of our global community, and for that group to take the lead in the process of evolving Drupal community governance, rather than any existing group or individual. While the Drupal Association, Community Working Group, and others in the project’s current governance structure are committed to providing whatever support they can to ensure the success of this working group, we feel that the community itself needs to own the process as much as possible.

We, the authors of this blog post, are not the leaders of the process, but as members of the community with interest and experience in various aspects of community governance, we are willing and able to help provide a framework for the group to self-organize and begin work to help improve the governance of our community. We stand ready to participate and help as needed, understanding that while this work will not be quick or easy, it is important and necessary for the long term sustainability of our project and community.

The next step for this is for you to get involved. Here's how to get started:

  • Join the #governance channel on Drupal Slack.

  • Attend a governance meeting in the #governance channel. Once a schedule has been determined we will publicize that information and pin it to the Slack channel. Each of the authors of this post will host at least one meeting and the entire meeting transcript will be made available after the meeting.

    • The goals of these meetings are to connect people who are interested in governance with each other, provide a forum for people to share their thoughts, and empower the community to determine the next steps.

    • We are committed to this being a community-driven process and will be present to facilitate, but not to dictate.

    • If there is interest, we can also host meetings in other forums. (IRC, video chat, etc.)

Other ways to get involved:

  • Write a blog post and share your ideas.

  • We know that people don’t always feel safe sharing their comments and feedback and we don’t yet have a long-term solution for this. In the interim, feel free to directly contact any of the writers of this post, or any member of the Community Working Group to share your thoughts.

We are at a unique inflection point in the history of the Drupal community. We have the opportunity to (once again) provide a shining example to other open source communities demonstrating our forward thinking; not only in technical decisions, but also community ones. Please join us.

Authors (listed alphabetically by Drupal.org username)

File attachments:  GovernanceSummitSanitized.ods
Categories: Drupal

Acquia Developer Center Blog: Drupal Commerce 2.0 Wisdom from Acro Media

25 September 2017 - 7:36am

If you’ve been following the Acro Media blog, you probably know that the digital agency (and Acquia partner), based in Kelowna, BC, Canada, has a special interest in Drupal Commerce.

So with the recent launch of Drupal Commerce 2.0, it made sense to check in with them.

Tags: acquia drupal planet
Categories: Drupal

Janez Urevc: Slovenian Drupal community celebrated the release of Commerce 2.0

25 September 2017 - 6:59am
Slovenian Drupal community celebrated the release of Commerce 2.0 slashrsm Mon, 25.09.2017 - 15:59

As you may already know the Commerce Guys team released the first stable Drupal 8 version of the truly flexible eCommerce suite last week. In order to celebrate this important event many parties were held all around the globe. Slovenian Drupal community definitely didn't want to miss that.

We gathered at the sprintaj.si headquarters in Izola, Slovenija. Sprintaj.si is not a classical "Drupal" business; they are a digital print shop. They are also a happy Drupal Commerce user and this was their way to show appreciation and give back to the community. Sprintaj.si was also one of the most interesting eCommerce projects I've been involved with. They support many different printed matters and their prices are always calculated on the fly based on the customer's needs. Their killer feature are custom formats and If you ever worked on an eCommerce project you can imagine that this results in some pretty hefty pricing rules.

At the party we had two sessions:

After the more educational part the more fun side of the event continued. Our hosts prepared a bunch of super tasty burgers and sponsored a small barrel of beer. OMG, we could easily repeat that!

Photos by: Aleš Rebec and Ben Rajnović

We would like to congratulate the Commerce team for this important milestone. You rock!

Categories: Drupal

Chromatic: The Tipping Point of a Flooded File System

25 September 2017 - 6:00am

The story of how we recovered from a mysterious performance meltdown related to file organization.

Categories: Drupal

Roy Scholten: Core roadmap overview @ Drupalcon Vienna Business Summit

25 September 2017 - 5:22am
25 Sep 2017 Core roadmap overview @ Drupalcon Vienna Business Summit

From organic to deliberate

At the Drupalcon Vienna Business Summit on monday I presented a quick overview of how the roadmap for Drupal core comes together. A short bit of context and then on to how the new 6-month release cycle creates room to evolve the core product faster.

Drupal 8.4 is done and just about to be released. Here’s the roadmap for Drupal 8.5 core the product management team put together. In short:

  1. Migrate
  2. Media
  3. API-First
  4. Layouts
  5. Workflow
  6. Outside-In
  7. Out-of-the-Box

Of course no talk is complete without a section about how you, yes you can help make it all happen:

  1. Help inform the roadmap priorities: share survey data, usability testing results, client feedback
  2. Help validate the roadmap: are we working on the right things? Does it help fill actual gaps?
  3. Help build, because process does not replace people: sponsor development by providing time, money, space for getting things done.
Drupal-core-roadmap-20170925.pdf Tags drupalplanet
Categories: Drupal

Vardot: Essential Things To Know About Varbase

25 September 2017 - 5:20am
Essential Things To Know About Varbase Dmitrii Susloparov Mon, 09/25/2017 - 15:20 Introduction

Varbase is a custom Drupal 8 base distribution developed by Vardot, a leading Drupal solution provider headquartered in Amman, Jordan with regional offices in Santa Clara, USA, and Cairo, Egypt. It is a software product embodying years of experience from building Drupal-based websites for high profile customers such as Al Jazeera, Georgetown University School of Foreign Service in Qatar, and the United Nations Relief and Works Agency (UNRWA).

 

Why Varbase?

Drupal is an industry-leading website building platform, renowned for its rich feature set and the ability for users to customize and extend core functionalities to satisfy their unique requirements. Its flexibility is due to its modular design, that is, Drupal functionalities are implemented in a large number of relatively small core and contributed modules, rather than in a single enormous blob object. One key element for a successful Drupal project is to start it off in the right way: namely, select and configure the best modules to do what you want, or as close to what you want in order to minimize the customization work. This can be a daunting task to most Drupal newcomers. For developers who have done this before, the task can quickly become a repetitive chore, as the same procedure is required at the beginning of each project.

 

Varbase offers Drupal site builders the important benefit of time saving. As a Drupal base distribution, Varbase makes available, in a single download, Drupal core modules as well as best-of-breed contributed modules, themes, and pre-defined configurations. Instead of starting from scratch, Varbase site builders leverage pre-installed and pre-configured industry-proven tools and modules. In addition to using the best modules that others had written, Vardot also contributed its own optimized modules to the distribution, for instance, Varbase SEO and Varbase Media. From now on you can start building and customizing your website right away, instead of wasting valuable resources in 'reinventing the wheel'.

 

The new distribution was the direct result after many hours of interaction between Vardot developers and web editors, specifically to find out how to make the editor's job easier and more efficient. Varbase users benefit from that editorial experience as the knowledge was subsequently codified into the design of Varbase modules.

 

Committing to a base distribution and a website building platform is a long-term investment by user organizations. To protect their investment, users look for a base distribution that is being actively developed and supported long-term by a quality organization. Varbase as a product is fully backed by Vardot, an award-winning enterprise web solution provider. Since 2011, Vardot has been applying its Drupal expertise to build enterprise websites spanning many industries, including corporate, non-profit, news/media, and higher education vertical industries. You can view the past history and the future roadmap of Varbase on-line. In addition to this, we've created a Slack channel where you can quickly get any information regarding the distribution or get our support in a timely manner.

 

 

Features Mobile ready

If a mobile visitor browses your website, only to find web pages served up using an oversized desktop resolution, it is very likely that the visitor (and potential customer) will bounce off and never return. Varbase prevents this event from happening by prepackaging custom responsive themes built using the industry-standard Bootstrap framework. The use of the carefully selected responsive themes guarantee that visitors will experience your website in a screen resolution that best fits the actual devices. The distribution also provides site editors with the ability to preview web pages on their mobile phones. As a result, editors can examine a page using the same screen resolution before releasing it to the target mobile user base.

High scalability

As your website gains readership over time, user experience of the site must not degrade because of the additional load on your Drupal platform. Specifically, the page load time must remain fast during peak hours in web traffic and also when your website experiences temporary spikes in traffic. Varbase is designed to be highly scalable in order to deliver the performance required to withstand a steady climb as well as a spike in web traffic.

Easy media management

 

The distribution offers optimized HTML5-compliant media management via the Varbase Media module. Support is built-in to upload, via drag-and-drop, photos, images, videos, and even documents to an on-line media library. Uploaded images and videos in the library can be assembled into sliders or carousels and displayed on your website. Varbase Media is designed to enhance both the aesthetic and the SEO performance of your media resources.

SEO ready

With a built-in SEO modules, search engine optimization is no longer hit-and-miss. Varbase provides a powerful SEO engine to grade the SEO readiness of your website, and to recommend on-page areas for improvement based on its vast SEO knowledge. Varbase enables the specification of metatags and markups to describe your web contents. Furthermore, to further increase the visibility of your web pages, Varbase supports the generation of XML sitemaps. If you are migrating your website to Drupal 8, Varbase can import all web pages from your legacy website, and set up page redirects from the old URLs to the new ones on the Drupal 8 platform.

Social media savvy

If visitors like your web content, you want to gently encourage them to share it with their social media contacts, essentially creating a viral effect. Varbase makes the integration of social media within your website as easy as just choosing the target social networks, which automatically enables the corresponding social media plugins. In addition, Varbase enables you to syndicate selected web contents to various social media networks, thereby maximizing their exposure and reach.

 

 

Summary & Conclusion

 

Varbase embodies the principle and practice of Don't Repeat Yourself (or DRY). It is a shortcut to developing your Drupal 8 website using out-of-the-box, best-of-breed modules, themes, and tools. Varbase is made available to the general Drupal community as a free and open-sourced software. Varbase users can download and modify the base software without incurring any licensing cost. For organizations that require professional services, note that Vardot offers full-cycle Drupal services ranging from implementation, customization, support, training, to hosted management. Please don’t hesitate to contact Vardot if you have any questions regarding our work!

Categories: Drupal

Annertech: Annertechies coming to DrupalCon Vienna

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

Drupal Association blog: Drupal Business Survey 2017

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

Appnovation Technologies: Appnovator Spotlight: Tim Kirby

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!

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

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

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

drunomics: Things to do around Drupalcon Vienna

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

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

Palantir: Drupal 8 is Great for Sustaining Innovation

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

Valuebound: How to secure your user’s private data from unauthorised access by enabling SSL on your web server

22 September 2017 - 6:54am

As a member of development team, I used to develop web applications using Drupal CMS without worrying about HTTP or HTTPS as it has to be added by dev operational team in my organization. On the serious note “How the Secure Sockets Layer (SSL) prepended to the existing URL” and How does it make a huge difference? Why it is important to make your web URL prepend https instead of HTTP.

Today SSL has become an eye-glazing topic and people want to know more about it so that they can protect their data from unauthorized access. In this blog post, we will take a brief look at basics of SSL and discuss how to secure the website running on Apache with HTTPS. Don’t worry! It's not a rocket science and very simple to secure your site as well as private data. In between, we will also…

Categories: Drupal

ADCI Solutions: Meet ADCI Solutions at DrupalCon Vienna

22 September 2017 - 4:08am

Hello, Drupal friends!

Our team want to make it big at DrupalCon. We prepared the session and two BoFs for you.

A LEADER OR A MANAGER? HOW TO DEFINE YOUR LEADERSHIP STAND

Our Head of Organizational development wil tell you how to define a leadership stand of yours. Knowing what you stand for in this life helps to get on your own feet and achieve outstanding results both in professional area and in self-realization.

Details

DRUPAL FOR A HIGHER EDUCATION

Our senior developer initiates the discussion on Drupal solutions for a higher education and science. The aim of this BoF is to gather Drupal experts and higher education representatives: that would allow us all to hear about the problems and the possible solutions from the first-person point of view. 

Details

MARKETING CHALLENGES IN THE DRUPAL WORLD

Another BoF is aimed at disclosing challenges we face while promoting and selling Drupal services, building the company image and communicating with a target audience. If we know the problems - we can find the solutions. 

Details

 

Drop a visit!

Categories: Drupal

ADCI Solutions: How to build a single-page application (SPA) with Vue.js

22 September 2017 - 2:10am

Everybody seems to build SPAs now. Single-page applications are a big deal: they provide good UX, speed; provide the full control over the markup in Drupal.

We played with Vue.js a bit, and created a simple SPA application. You can use Drupal on the back-end: you’ll find the necessary instructions inside of the article.

 

Read the full article.

 

 

Categories: Drupal

Pages