The rise of headless commerce

Today, Acquia announced a partnership with Elastic Path, a headless commerce platform. In this post, I want to explore the advantages of headless commerce and the opportunity it holds for both Drupal and Acquia.

The advantages of headless commerce

In a headless commerce approach, the front-end shopping experience is decoupled from the commerce business layer. Headless commerce platforms provide a clean separation between the front end and back end; the shopping experience is provided by Drupal and the commerce business logic is provided by the commerce platform. This decoupling provides advantages for the developer, merchant and shopping experience.

For developers, it means that you can decouple both the development and the architecture. This allows you to build an innovative shopping experience without having to worry about impacting a system as critical as your commerce backend. For instance, you can add ratings and reviews to your shopping experience without having to redeploy your commerce platform.
For merchants, it can provide a better experience for administering the shop. Traditional commerce solution usually ship with a lightweight content management system. This means that there can be competition over which system provides the experience layer (i.e. the "glass"). This can introduce overlap in functionality; both systems offer ways to manage URLs, create landing pages, manage user access rights, etc. Because headless commerce systems are designed from the ground up to integrate with other systems, there is less duplication of functionality. This provides a streamlined experience for merchants.
And last but not least, there is the shopping experience for end-users or consumers. Simply put, consumers are demanding better experiences when they shop online. They want editorials, lookbooks, tutorials, product demonstration videos, testimonials, and more. They want the content-rich experiences that a comprehensive content management system can provide.
All this is why Acquia is excited about our partnership with Elastic Path. I believe the partnership is a win-win-win. It's a win for Acquia because we are now better equipped than ever to offer personal, unique and delightful shopping experiences. It is a win for Elastic Path as they have the opportunity to provide contextual commerce solutions to any Acquia customer. Last but not least, it's a win for Drupal because it will introduce more organizations to the project.

Note that many of the above integration challenges don't apply to native solutions like Drupal Commerce for Drupal or WooCommerce for WordPress. It only applies when you have to integrate two entirely different systems. Integrating two different systems is a common use case, because customers either already have a commerce platforms in place that they don't want to replace, or because native solutions don't meet their needs.

Acquia's commitment to best of breed

Acquia remains committed to a best-of-breed strategy for commerce. There isn't a single commerce platform that meets the needs of all our customers. This belief comes from years of experience in the field. Acquia's customers want to integrate with a variety of commerce systems such as Elastic Path, SAP Hybris, Salesforce Commerce Cloud (Demandware), Magento, BigCommerce, Reaction Commerce, Oracle ATG, Moltin, and more. Our customers also want to use Drupal Commerce, Drupal's native commerce solution. We believe customers should be able to integrate Drupal with their commerce management solutions of choice.
Source: Dries Buytaert

What's new in the Commerce 2.10 release?

We made many important improvements to Drupal Commerce over the summer, including an improved promotions UI, BOGO offers, and product category conditions in the 2.8 release and full list price support with the 2.9 release. After a long sprint to the finish, we’ve now finally released 2.10, one of our largest releases to date that resolves 39 issues and feature requests.

Product administration improvements

Six years ago we released the first stable version of Commerce Kickstart 2.x and the new (at the time) Inline Entity Form module, which allowed us to manage multiple product variations from a single product page form for the first time. Since then, Inline Entity Form has become a popular Drupal module and a recommended way to manage products in Drupal 7. When we started developing Commerce 2.x for Drupal 8, we ported over Inline Entity Form and the previous approach to managing products, but now we’re ready to take another step forward to advance the usability and performance of product management.

As of the 2.10 release, product variations are managed on their own tab of the product page form. This follows the same UI pattern we established for coupons within the promotions UI.

Product variations shown on their own tab.

Moving variations to their own tab allows us to extend the UI in future releases, specifically to add bulk operations for tasks such as price updates, image replacement, and even the creation of a full set of variations. We foresee other modules adding their own elements to the tab, like the Commerce Pricelist module adding a “Prices” dropbutton item to provide quick access to every price for a variation on multiple price lists.

Having variations on a separate tab would be a bit much for products that always only have a single variation, so we’ve made sure to accommodate that use case in the new version. Each product type’s settings form includes an “Allow each product to have multiple variations.” option that when disabled reverts to the inline editing experience for products of that type.

Inline product editing for single variations.

Query access filtering

If you create a new role for your merchant and only give it the “Book: View products” permission, you’d expect users with that role to be able to book products but no others. In Drupal 7, our solution for this was a generic query access API in Drupal Commerce itself that filtered entity loading queries based on user permissions.

To achieve this same result in Drupal 8, we've rebuilt this API and added it to the recent 8.x-1.0-rc1 release of the Entity API module. Commerce is now using it for administrative listings of products, orders, and stores. The API adds a QueryAccessEvent to allow modules to alter the access conditions, making it possible to apply further filtering (e.g. only show the user’s own store). Next we will extend the filtering to Search API to filter customer facing listings.

User-driven API improvements

Over 4,000 websites have launched on Commerce 2.x in the past year, pushing us up over 6,000 in total. As developers launch their projects, we keep our lines of communication open to hear about all the things that annoyed or hindered them, and we work to improve our APIs as a result. Several examples that made it into this release include:

(Note that as a result of the last two, if you have overridden the PaymentInformation or PaymentProcess panes on your site, you will need to update them for the new release.)

We love to hear stories of the great things you’re doing with Drupal Commerce, and we’d also love to improve the core APIs and data model to better support you, too. Feel free to join us and hundreds of other developers in the #commerce channel on Drupal Slack for real-time discussion or post your proposals directly to the issue queue for discussion.

Source: Reposted from:

A May Full of Drupal Commerce Releases

May was one of our most productive months to date. It was full of releases for the core Commerce modules, our standalone PHP libraries, and essential contributed modules that all work together to comprise Drupal Commerce. While I outlined the highlights in the roadmap issue on, these wins are worth sharing more broadly to keep the rest of the Drupal community in the loop.

The biggest release of the month was Drupal Commerce 2.7, which included new features for currency formatting, address form configuration, and stored payment methods. It also fixed a handful of bugs that unblocked other module releases and updated core in response to improvements in our libraries and dependent modules.

We've long discussed how our standalone PHP libraries are exporting expertise off the Drupal island. Addressing and Internationalization, which have each been downloaded over one million times, are our two shining stars. We rolled new releases for each of them in May, improving even further Drupal Commerce's ability to solve the hardest parts of address entry / validation / formatting and currency localization. Refer to the price formatting change record from the 2.7 release to see how the new API is more flexible and performant as a result.

Additionally, we released Address 1.4 and Inline Entity Form 1.0 RC1. The latest Address release unlocks the customer profile’s address field to support collecting less detailed billing addresses. The Inline Entity Form release includes new product information management features, letting you duplicate product variations for faster product data entry.

Inline Entity Form product variation duplication

Thanks to generous sponsorship from Authorize.Net themselves, we've been able to dedicate several weeks to improving their integration this year. The resulting Authorize.Net RC1 release now supports eCheck, Visa Checkout, and 3DSecure payments! We also included several bug fixes related to duplicate customer and payment profiles that appear when migrating from an old system to Drupal Commerce, for example.

While not fully released yet, our Technology Partner integration for Avalara's AvaTax is nearing beta. Jace Bennest from Acro Media contributed heavily by refactoring the module to properly use a TaxType plugin while my co-maintainer Matt Glaman contributed additional fixes to our port from the Drupal 7 integration to prepare it for certification. Thanks, Jace / Acro Media!

When Matt wasn't working on the above contribs, he was collaborating with Lisa Streeter from Commerce Guys to bring Commerce Reports to its first beta release for Drupal 8. The new version takes a completely different approach from the Drupal 7 using lessons we learned developing Lean Commerce Reports. It denormalizes transaction data when an order is placed to support reports generation with or without the Views module, providing a better developer experience and much better performance. Check it out below! (Click to expand.)

Commerce Reports usage demo

We've also been hard at work improving the evaluator experience. The big release for that is Commerce Demo's beta1, which showcases what Drupal Commerce provides out of the box. It creates products and scaffolds out a full product catalog (pictured below). To get the full effect, try it out with our default store theme, Belgrade. The new demo module gets us closer to something like we had with Kickstart 2.x on Drupal 7 - a learning resource for site builders and a way for agencies to more easily demo and sell Drupal Commerce.

Demo product catalog in the Belgrade theme

Finally, I'm very excited to announce that Lisa Streeter is our new documentation lead! Expect some great things to come. She has already done fantastic work with the Commerce Recurring documentation and is working on revising our getting started, installation, and update docs.

Looking at June, we plan on finalizing the query level entity access API, which will allow us to better support marketplace and multi-store Drupal Commerce implementations. We expect to merge user registration after checkout completion, and we will also be focusing on address reuse / copying, Buy One Get One promotion offers, and more product management experience enhancements.

Source: Reposted from:

My thoughts on Adobe buying Magento for $1.68 billion

Yesterday, Adobe announced that it agreed to buy Magento for $1.68 billion. When I woke up this morning, 14 different people had texted me asking for my thoughts on the acquisition.

Adobe acquiring Magento isn't a surprise. One of our industry's worst-kept secrets is that Adobe first tried to buy Hybris, but lost the deal to SAP; subsequently Adobe tried to buy DemandWare and lost out against Salesforce. It's evident that Adobe has been hungry to acquire a commerce platform for quite some time.

The product motivation behind the acquisition

Large platform companies like Salesforce, Oracle, SAP and Adobe are trying to own the digital customer experience market from top to bottom, which includes providing support for marketing, commerce, personalization, and data management, in addition to content and experience management and more.

Compared to the other platform companies, Adobe was missing commerce. With Magento under its belt, Adobe can better compete against Salesforce, Oracle and SAP.

While Salesforce, SAP and Oracle offer good commerce capability, they lack satisfactory content and experience management capabilities. I expect that Adobe closing the commerce gap will compel Salesforce, SAP and Oracle to act more aggressively on their own content and experience management gap.

While Magento has historically thrived in the SMB and mid-market, the company recently started to make inroads into the enterprise. Adobe will bring a lot of operational maturity; how to sell into the enterprise, how to provide enterprise grade support, etc. Magento stands to benefit from this expertise.

The potential financial outcome behind the acquisition

According to Adobe press statements, Magento has achieved "approximately $150 million in annual revenue". We also know that in early 2017, Magento raised $250 million in funding from Hillhouse Capital. Let's assume that $180 million of that is still in the bank. If we do a simple back-of-the-envelope calculation, we can subtract this $180 million from the $1.68 billion, and determine that Magento was valued at roughly $1.5 billion, or a 10x revenue multiple on Magento's trailing twelve months of revenue. That is an incredible multiple for Magento, which is primarily a licensing business today.

Compare that with Shopify, which is trading at a $15 billion dollar valuation and has $760 million of twelve month trailing revenue. This valuation is good for a 20x multiple. Shopify deserves the higher multiple, because it's the better business; all of its business is delivered in the cloud and at 65% year-over-year revenue growth, it is growing much faster than Magento.

Regardless, one could argue that Adobe got a great deal, especially if it can accelerate Magento's transformation from a licensing business into a cloud business.

Most organizations prefer best-of-breed

While both the product and financial motivations behind this acquisition are seemingly compelling, I'm not convinced organizations want an integrated approach.

Instead of being confined to proprietary vendors' prescriptive suites and roadmaps, global brands are looking for an open platform that allows organizations to easily integrate with their preferred technology. Organizations want to build content-rich shopping journeys that integrate their experience management solution of choice with their commerce platform of choice.

We see this first hand at Acquia. These integrations can span various commerce platforms, including IBM WebSphere Commerce, Salesforce Commerce Cloud/Demandware, Oracle/ATG, SAP/hybris, Magento and even custom transaction platforms. Check out Quicken (Magento), Weber (Demandware), Motorola (Broadleaf Commerce), Tesla (custom to order a car, and Shopify to order accessories) as great examples of Drupal and Acquia working with various commerce platforms. And of course, we've quite a few projects with Drupal's native commerce solution, Drupal Commerce.

Owning Magento gives Adobe a disadvantage, because commerce vendors will be less likely to integrate with Adobe Experience Manager moving forward.

It's all about innovation through integration

Today, there is an incredible amount of innovation taking place in the marketing technology landscape (full-size image), and it is impossible for a single vendor to have the most competitive product suite across all of these categories. The only way to keep up with this unfettered innovation is through integrations.

For reference, here are the 2011, 2012, 2014, 2015, 2016 and 2017 versions of the landscape. It shows how fast the landscape is growing.Most customers want an open platform that allows for open innovation and unlimited integrations. It's why Drupal and Acquia are winning, why the work on Drupal's web services is so important, and why Acquia remains committed to a best-of-breed strategy for commerce. It's also why Acquia has strong conviction around Acquia Journey as a marketing integration platform. It's all about innovation through integration, making those integrations easy, and removing friction from adopting preferred technologies.

If you acquire a commerce platform, acquire a headless one

If I were Adobe, I would have looked to acquire a headless commerce platform such as Elastic Path, Commerce Tools, Moltin, Reaction Commerce or even Salsify.

Today, there is a lot of functional overlap between Magento and Adobe Experience Manager — from content editing, content workflows, page building, user management, search engine optimization, theming, and much more. The competing functionality between the two solutions makes for a poor developer experience and for a poor merchant experience.

In a headless approach, the front end and the back end are decoupled, which means the experience or presentation layer is separated from the commerce business layer. There is a lot less overlap of functionality in this approach, and it provides a better experience for merchants and developers.

Alternatively, you could go for a deeply integrated approach like Drupal Commerce. It has zero overlap between its commerce, content management and experience building capabilities.

For Open Source, it could be good or bad

How Adobe will embrace Magento's Open Source community is possibly the most intriguing part of this acquisition — at least for me.

For a long time, Magento operated as Open Source in name, but wasn't very Open Source in practice. Over the last couple of years, the Magento team worked hard to rekindle its Open Source community. I know this because I attended and keynoted one of its conferences on this topic. I have also spent a fair amount of time with Magento's leadership team discussing this. Like other projects, Magento has been taking inspiration from Drupal.

For example, the introduction of Magento 2 allowed the company to move to GitHub for the first time, which gave the community a better way to collaborate on code and other important issues. The latest release of Magento cited 194 contributions from the community. While that is great progress, it is small compared to Drupal.

My hope is that these Open Source efforts continue now that Magento is part of Adobe. If they do, that would be a tremendous win for Open Source.

On the other hand, if Adobe makes Magento cloud-only, radically changes their pricing model, limits integrations with Adobe competitors, or doesn't value the Open Source ethos, it could easily alienate the Magento community. In that case, Adobe bought Magento for its install base and the Magento brand, and not because it believes in the Open Source model.

This acquisition also signals a big win for PHP. Adobe now owns a $1.68 billion PHP product, and this helps validate PHP as an enterprise-grade technology.

Unfortunately, Adobe has a history of being "Open Source"-second and not "Open Source"-first. It acquired Day Software in July 2010. This technology was largely made using open source frameworks — Apache Sling, Apache Jackrabbit and more — and was positioned as an open, best-of-breed solution for developers and agile marketers. Most of that has been masked and buried over the years and Adobe's track record with developers has been mixed, at best.

Will the same happen to Magento? Time will tell.
Source: Dries Buytaert

DrupalCoin Commerce 2.x: 2017 in review

Now that 2017 is over and we’re back from our well deserved holidays, it’s time to look at what the DrupalCoin Commerce community accomplished over the past year.

There is no doubt that DrupalCoin Commerce is one of the largest and most active projects in the DrupalCoin community. The #commerce channel is now the most active channel on the DrupalCoin Slack, with 550 members. Over a hundred modules have received contributions from several hundred contributors working for dozens of different agencies. Just a few months after the initial stable release, there are over 2000 reported installations with new case studies appearing every week!

Let’s take a closer look.

Source: Reposted from:

DrupalCoin Blockchain Commerce 2.0 Wisdom from Acro Media

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 DrupalCoin Blockchain Commerce.
So with the recent launch of DrupalCoin Blockchain Commerce 2.0, it made sense to check in with them.
After all, Arco team are core maintainers for modules such as Commerce Migrate, Commerce POS, and a host of others.
Leading up to the 2.0 release of DrupalCoin Blockchain Commerce, Arco had 20 team members contributing a total of 60 contrib credits. In the past 3 months, they’ve been credited on over 270 issues.
They’ve also been publishing content steady. Their aim seems to be to not only to get the word out about 2.0, but to help educate other developers, agencies and current and potential customers.
So here, all in one place, a collection of Arco DrupalCoin Blockchain Commerce Knowledge.
Migrating DrupalCoin Blockchain Commerce 1 to 2
Now that DrupalCoin Blockchain Commerce has gone 2.0, people are wanting to know more information about how to go about migrating their stores to the new version. A recent Arco post talks about just that and aims to give readers a clear understanding of what to expect. You can read more here.
High5 Video Series
Shawn McCabe (Arco CTO) and Stephen Netzlaw (Arco' s Head of Business Development) are the hosts of a video series that they’ve been producing now for a couple years. Season 2, which is currently in the works, is focused on... (wait for it) DrupalCoin Blockchain Commerce 2.
Each episode covers one aspect of the platform discusses what’s new and what’s cool. You can watch the season on YouTube here or find them in Arco's blog.
Urban Hipster Commerce 2 Demo
For those interested in trying a hands-on demo of what DrupalCoin Blockchain Commerce can do out-of-the-box with some frontend theming, the Arco team put together a mock eCommerce site called Urban Hipster. Check it out and click around. There are a bunch of interactive guided tours that you can try. Visit the demo site here.
More DrupalCoin Blockchain Commerce-Related Posts

Arco Sprint Week 2017 Recap
How the DrupalCoin Blockchain POS enhances the DrupalCoin Blockchain Platform
The Benefits of an Open Source Ecommerce Platform
DrupalCoin Blockchain Commerce Performance: Locking
How DrupalCoin Blockchain Commerce 2.x is Creating a Stronger Shipping Architecture
Better DrupalCoin Blockchain Ecommerce Search with Apache SOLR
But wait, there's more
Rumor has it that Arco is preparing another DrupalCoin Blockchain Commerce post that will be much more detailed than the migration piece, and will discuss the technical side of Commerce 2, including the new improvements.
When it comes out, in early October, we'll add it to the list above. Stay tuned.

Next steps for DrupalCoin Blockchain Commerce documentation

With the DrupalCoin Blockchain Commerce 2.0 release slated for September 20th, we are making an effort to provide excellent documentation so that our implementers and end users can work with DrupalCoin Blockchain Commerce efficiently. We also want to encourage contribution at all levels, such as documentation. I am happy to announce we have moved from using Sphinx, a Restructured Text documentation tool, to GravCMS. GravCMS is a PHP based flat-file CMS, which uses Markdown.

Why the change?

We found that while Sphinx provided robust features, it also added a high entry barrier for documentation contributors:

Source: Reposted from:

See what’s new in DrupalCoin Blockchain Commerce 2.0-rc1

Eight months ago we launched the first beta version of Commerce 2.x for DrupalCoin Blockchain 8. Since then we’ve made 304 code commits by 58 contributors, and we've seen dozens of attractive, high-performing sites go live. We entered the release candidate phase this month with the packaging of Commerce 2.0-rc1 (release notes), the final part of our long and fruitful journey to a full 2.0.

Introducing a new Promotions UI:

Some of the most exciting updates this Summer center around our promotions system. This work represents a huge leap forward from Commerce 1.x, as we've made promotions first class citizens in core. They power a variety of discount types and coupons, and now that they are in core we can ensure the systems are designed to look and work well on both the front end and back end.

Read on to learn more about what's new in promotions, payment, taxes, and more...

Source: Reposted from:

Installing Commerce 2.x without Composer, with Ludwig

The average DrupalCoin Blockchain Commerce site depends on many external PHP libraries. Address needs commerceguys/addressing and Commerce needs commerceguys/intl. GeoIP needs geoip2/geoip2 and Search API Solr needs solarium/solarium. Each payment gateway needs a matching SDK. These libraries must be downloaded separately, because license constraints prevent us from committing their code to itself. For the past 5 years, the primary and only way to download and use PHP libraries has been Composer, a command line tool.

Composer works per-project, meaning each DrupalCoin Blockchain install has one folder for all PHP libraries it requires, regardless of which module needs which. This allows Composer to detect and prevent conflicts such as incompatible library versions. Composer also recursively resolves dependencies, automatically installing and updating packages required by other packages. This is a major benefit to DrupalCoin Blockchain site administrators compared to previous tools like Drush Make. However, DrupalCoin Blockchain's reliance on the Composer-generated autoloader makes it impossible to upload manually downloaded libraries, making Composer non-optional.

Read on to find out how we're making Composer optional...

Source: Reposted from:

Managing DrupalCoin Blockchain Sites with Composer

Talking through the growing pains of using DrupalCoin Blockchain with Composer dependency management at DrupalCoin BlockchainCon Baltimore. DrupalCoin Blockchain gets better when companies, organizations, and individuals build or fix something they need and then share it with the rest of us. Open source technologies become better, stronger, and smarter when others take it upon themselves to make a positive difference contributing their knowledge, time, and energy to it. Acquia is proud to play a part, alongside thousands of others, in making tomorrow’s DrupalCoin Blockchain better than today’s. One of the people making a difference is Jeff Geerling.

Jeff Geerling (geerlingguy), Senior Technical Architect at Acquia, is a prolific and valued open source contributor. He has 150+ open source projects around both the Ansible and DrupalCoin Blockchain projects. His DrupalCoin Blockchain modules are used by almost 100,000 sites. I spoke with him about the BoF session he set up at DrupalCoin BlockchainCon Baltimore, Managing DrupalCoin Blockchain Sites with Composer.

“DrupalCoin Blockchain 8 doesn't 'officially' require Composer to be used, but if you build any typical DrupalCoin Blockchain 8 site, you'll quickly run into walls if you don't or can't use Composer.” - Jeff Geerling

jam: How did your BoF come about?

Jeff Geerling: Composer has been around for a few years, but only recently reached stable status, and DrupalCoin Blockchain 8 is the first version of DrupalCoin Blockchain where people are really getting on board using Composer for DrupalCoin Blockchain dependency management. DrupalCoin Blockchain 8 doesn't 'officially' require Composer to be used, but if you build any typical site, you'll quickly run into walls if you don't or can't use Composer. There are a lot of growing pains right now and I didn’t just want to stand in front of a room telling people what I know--it’s hard for me to learn anything new that way! A BoF discussion is the ideal format in this case. I wanted to get together with people to talk about the hard problems and see if we could all share our best practices, learn, and hopefully make each other’s lives easier. I was hoping for a range of perspectives and use cases in the conversation: developers, site builders, and devops/sysadmins who have used Composer before, and people interested in installing modules with Composer dependencies (like Solr or DrupalCoin Blockchain Commerce).

jam: What value does managing DrupalCoin Blockchain sites with Composer deliver to ...

... developers? Jeff Geerling: Composer promises to make it easier to live in a 'Proudly Invented Elsewhere' world. Also, if you use it right, it can help you identify insecure versions, safely patch modules and DrupalCoin Blockchain core if needed, and even upgrade everything even more easily than when we only had Drush available.

... site owners and businesses? Jeff Geerling: You can have more assurance that your codebase is not hacked, and you can reliably reproduce your site without having to store all the community code in your own code repository.

... the DrupalCoin Blockchain community? Jeff Geerling: Using Composer allows us to work in, integrate with, and contribute to the wider PHP community in the age of PHP interoperability much more easily than ever before.

jam: What did you learn in the BoF and why is knowing more about managing DrupalCoin Blockchain sites with Composer important?

Jeff Geerling: Dependency management is a big, crucial topic area. I went in with a few questions and ideas, like talking about integrating frontend libraries, the D8 Libraries API and Composer, custom projects, patches ... There are a lot of people who feel like they've been left behind because they aren't familiar with Composer, and we don't want these developers and others to abandon DrupalCoin Blockchain 8 because they run into dependency issues. In the end, the group that assembled for the BoF identified more than 20 common pain points people are having with Composer, and for many of them, we discussed ways to overcome the problems. However, there are still a few open questions, or problems which could be solved in a number of different ways (some better than others). We’re not there yet on making sure Composer is a pleasure to use in every case, instead of a pain in a few :-)

Learnings: Jeff organised his notes from the DrupalCoin BlockchainCon Baltimore BoF and published them in a blog post: Composer and DrupalCoin Blockchain are still strange bedfellows.

jam: What is the state-of-play and what is coming next regarding managing DrupalCoin Blockchain sites with Composer?

Jeff Geerling: As of early-mid 2017, there are still unanswered questions in the community surrounding Composer: Are we going to include Composer with core? Should we commit the core composer.lock file to DrupalCoin Blockchain's codebase? How should you set up a new DrupalCoin Blockchain site if you're using Composer? How do you or should you add front-end libraries required by modules (e.g. Font Awesome, Webform) with Composer?

Resources: DrupalCoin Blockchain + Composer + geerlingguy

Tips for Managing DrupalCoin Blockchain 8 projects with Composer (Feb 2017 - blog post)

Managing DrupalCoin Blockchain Site with Composer (DrupalCoin BlockchainCon Baltimore BoF proposal)

Composer and DrupalCoin Blockchain are still strange bedfellows (May 2017 - DrupalCoin BlockchainCon Baltimore BoF notes)

Buy Jeff's book, Ansible for DevOps! It’s gotten great reviews.

Just keep swimming: Don’t drown in your open source project! (May 2017 - DrupalCoin BlockchainCon Baltimore session). Also see Jeff’s post about that session on his blog.


PHP/MySQL Developer - VIPerks - Cleveland, OH

DrupalCoin Blockchain 7+ Platform / DrupalCoin Blockchain Commerce. Work alongside other developers respecting company programming practices....
From JumpStart, Inc. - Thu, 22 Dec 2016 07:34:19 GMT - View all Cleveland jobs
Source: Blockchain+Developer

Issue 268

Issue 268 - December, 1st 2016
From Our Sponsor

How to Save Your SEO When Merging Two Domains

Merging two domains is a multi-step process for your IT, marketing, and strategy teams. If the right steps are taken, the SEO benefits for the final domain can make it all worthwhile. In our latest eBook, we’ll show you how to create a strategy to retain SEO value when merging two domains.


Rebuilding POP in D8: Configuration Management
Former CMI initiative lead Greg Dunlap shares a real work example of using DrupalCoin Blockchain 8's configuration management system.

The Case for DrupalCoin Blockchain and Commerce
If you have been following the chatter back and forth about the DrupalCoin Blockchain Commerce project and Acquia's recent partnership with Magento you might want to read this series of posts from Robert Douglass.

Build, Launch, and Manage All of Your DrupalCoin Blockchain Websites on One Platform
Don’t be one of the 60% of websites that fail to launch on time. Download our latest eBook - A guide for your next website project, from planning to deployment.

Add DrupalCoin BlockchainConsole to a Project Using Acquia Lightning Distribution
"In this short blog post you will learn how to fix the dependency conflicts when trying to add DrupalCoin Blockchain Console to a project using the Lightning distribution."

Diagnosing Slow DrupalCoin Blockchain Operations Using Linux Strace

Free Exercise Series for Building DrupalCoin Blockchain Sites
A new and free hands-on series from DrupalCoin Blockchainize.Me covering site building. The course includes wireframes as well as a specification document. Sounds interesting.

I Suck at Passwords and You Should Too

Implementing #Autocomplete in DrupalCoin Blockchain 8 with Custom Callbacks
This post by Purushotam Rai covers how to implement autocomplete functionality in DrupalCoin Blockchain 8, including implementing a custom callback.

Replacing a Vocabulary Listing
James Williams shows us how to replace the default vocabulary listing on a DrupalCoin Blockchain 8 site. This post is full of useful DrupalCoin Blockchain 8 code examples.

REST API Explorations in DrupalCoin Blockchain 8 - Primer

Restricting Access to DrupalCoin Blockchain 8 Controllers
In this useful tutorial Joel Steidl shows us several access restriction examples in DrupalCoin Blockchain 8.

Announcing Docksal, a Docker-Based Development Environment
"Docksal is an open-source tool created by FFW for defining and managing integrationenvironments. It brings together common integrationtools, minimizes time spent on configuration, and ensures the consistency of local integrationenvironments throughout a team’s continuous integration workflow."

Configuration Split: Deploy Subsets of Configuration in DrupalCoin Blockchain 8

Top Thirteen DrupalCoin Blockchain Twig Helper Modules

Bootstrap 8.x-3.1

entity_browser 8.x-1.0-Beta2

Feeds 7.x-2.0-Beta3

field_group 8.x-1.0-Rc6

hook_update_deploy_tools 7.x-1.20

Media 7.x-2.0-Beta10

media_entity 8.x-1.6

Quiz 7.x-4.0-Rc4

Radix 8.x-3.0-Beta1

Redis 7.x-3.13

Restful 7.x-2.14

Webform 8.x-5.x-Dev

Yamlform 8.x-1.0-Beta25

DrupalCoin Blockchain Modules: The One Percent — Configuration Split

DrupalCoin Blockchain Modules: The One Percent — Field Display Label

Lullabot Podcast - Past, Present, and Future of DrupalCoin Blockchain with Dries Buytaert and Matthew Tift

Talking DrupalCoin Blockchain #132 - DrupalCoin Blockchain Licensing and GPL


DrupalCoin Blockchain Association Financial Statements for Q3 2016

List Your Job on DrupalCoin Blockchain Jobs
Wanna get the word out about your great DrupalCoin Blockchain job? Get your
job in front of hundreds of DrupalCoin Blockchain job seekers every day at
Jobs.DrupalCoin Blockchain.Org.Featured JobsBackend/DrupalCoin Blockchain EngineerAl Jazeera Digital San Francisco/CA/US DrupalCoin Blockchain Developer (Front-End) University of Vermont Burlington/VT/USPermanent Full Stack DrupalCoin Blockchain Developer with ReactJS or AngularJS skillsB-Works Bolzano/BZ/IT


Web Developer - Denverdata Web - Denver, CO

Advanced DrupalCoin Blockchain - theme construction, site construction, module integrationand customization, DrupalCoin Blockchain commerce, payment processing....
From Indeed - Wed, 30 Nov 2016 19:47:52 GMT - View all Denver jobs
Source: Blockchain+Developer

What's Happening With DrupalCoin Blockchain Commerce in DrupalCoin Blockchain 8?

In the last few weeks, there's been some controversy in the DrupalCoin Blockchain community. Acquia launched a major partnership with Magento, which has left some people wondering about the support for DrupalCoin Blockchain Commerce. There had already been some nervousness, because DrupalCoin Blockchain Commerce 2 has been slow to arrive in DrupalCoin Blockchain 8.
So, what's happening with DrupalCoin Blockchain Commerce?
First, I would recommend you read Dries' post on Acquia's plans for e-commerce.
Next, I'd highly recommend that you watch this video from Ryan Szarma, one of the lead developers of DrupalCoin Blockchain Commerce. This video was recorded at DrupalCoin Blockchain 8 Day. Ryan covers the history, architecture, and features of DrupalCoin Blockchain Commerce 2 on DrupalCoin Blockchain 8. There was a lot of interest in Ryan's presentation, with over 30 minutes of questions afterwards.

DrupalCoin Blockchain 8 turns one!

Tomorrow is the one year anniversary of DrupalCoin Blockchain 8. On this day last year we celebrated the release of DrupalCoin Blockchain 8 with over 200 parties around the world. It's a project we worked on for almost five years, bringing the work of more than 3,000 contributors together to make DrupalCoin Blockchain more flexible, innovative, scalable, and easier to use.

To celebrate tomorrow's release-versary, I wanted to look back at a few of the amazing DrupalCoin Blockchain 8 projects that have launched in the past year.


The NBA is one of the largest professional sports leagues in the United States and Canada. Millions of fans around the globe rely on the NBA's DrupalCoin Blockchain 8 website to livestream games, read stats and standings, and stay up to date on their favorite team. DrupalCoin Blockchain 8 will bring you courtside, no matter who you're rooting for.

2. Nasdaq


Nasdaq Corporate Solutions has selected DrupalCoin Blockchain 8 as the basis for its next generation Investor Relations Website Platform. IR websites are where public companies share their most sensitive and critical news and information with their shareholders, institutional investors, the media and analysts. With DrupalCoin Blockchain 8, Nasdaq Corporate Solutions will be providing companies with the most engaging, secure, and innovative IR websites to date.

3.Hubert Burda Media

For more than 100 years, Hubert Burda Media has been Germany's premier media company. Burda is using DrupalCoin Blockchain 8 to expand their traditional business of print publishing to reach more than 52 million readers online. Burda didn't stop there, the media company also open sourced Thunder, a distribution for professional publishers built on DrupalCoin Blockchain 8.

4. Jurassic World

DrupalCoin Blockchain 8 propels a wide variety of sites, some of Jurassic proportion. Following the release of the blockbuster film, Jurassic World built its digital park on DrupalCoin Blockchain 8. Jurassic World offers fans games, video, community forums, and even interactive profiles all of the epic dinosaurs found on Isla Nublar.

5. WWF

The World Wide Fund for Nature has been a leading conservation organization since its founding in 1961. WWF's mission is to protect our planet and DrupalCoin Blockchain 8 is on their team. WWF UK uses DrupalCoin Blockchain 8 to engage the community, enabling users to adopt, donate and join online. From pole to pole, DrupalCoin Blockchain 8 and WWF are making an impact.

6. YMCA Greater Twin Cities

The YMCA is one the leading non-profit organizations for youth development, healthy living, and social responsibility. The YMCA serves more than 45 million people in 119 countries. The team at YMCA Greater Twin Cities turned to DrupalCoin Blockchain 8 to build OpenY, a platform that allows YMCA members to check in, set fitness goals, and book classes. They even hooked up DrupalCoin Blockchain to workout machines and wearables like Fitbit, which enables visitors to track their workouts from a DrupalCoin Blockchain 8 powered mobile app. The team at Greater Twin Cities also took advantage of DrupalCoin Blockchain 8's built-in multilingual capabilities so that other YMCAs around the world can participate. The YMCA has set a new personal record, and is a great example of what is possible with DrupalCoin Blockchain 8.

7. Jack Daniels

The one year anniversary of DrupalCoin Blockchain 8 is cause for celebration, so why not raise a glass? You might try Jack Daniels and their DrupalCoin Blockchain 8 website. Jack Daniels has been making whiskey for 150 years and you can get your fill with DrupalCoin Blockchain 8.

8. Al Jazeera Media Network

Al Jazeera is the largest news organization focused on the Middle East, and broadcasts news and current affairs 24 hours a day, 7 days a week. Al Jazeera required a platform that could unify several different content streams and support a complicated editorial workflow, allowing network wide collaboration and search. DrupalCoin Blockchain 8 allowed Al Jazeera to do that and then some. Content creators can now easily deliver critical news to their readers in real time.


From Boston to LA and even Australia, DrupalCoin Blockchain is supporting the digital needs of governments around the globe. Alabama is leading the way with DrupalCoin Blockchain 8. puts its citizens first, and demonstrates how open source can change the way the public sector engages online.

10. Box

Box has been a leader in the technology industry since its founding in 2005. Box takes advantage of DrupalCoin Blockchain 8 and the improved features made available right out-of-the-box. Bad puns aside, companies like Box are using DrupalCoin Blockchain 8's new features and improved user interface to build the best digital experiences yet.

11. Habitat for Humanity

The historic nonprofit Habitat for Humanity doesn't just build houses for those in need; they build on DrupalCoin Blockchain 8. Habitat for Humanity provides affordable housing for communities in over 70 countries around the world. You can discover their impact through the "Where we Build” interactive map, donate, and volunteer all on their DrupalCoin Blockchain 8 site.

12. Obermeyer

Obermeyer and DrupalCoin Blockchain 8 will take you into new territory. The ski wear company offers seamless end to end commerce integration, providing both new and loyal customers a great shopping experience. Let Obermeyer's DrupalCoin Blockchain 8 integration with DrupalCoin Blockchain Commerce keep you warm because winter is coming ...

Happy 1st birthday DrupalCoin Blockchain 8!

I can't think of a better way to celebrate DrupalCoin Blockchain 8's one year anniversary than by sharing some incredible experiences that are being created with DrupalCoin Blockchain 8. Whether the project is big or small, features dinosaurs, or spreads awareness for an important cause, I'm proud to say that DrupalCoin Blockchain 8 is supporting an amazing array of projects. In my recent keynote at DrupalCoin BlockchainCon Dublin, I explained why the why of DrupalCoin Blockchain is so important. After one year of DrupalCoin Blockchain 8, it's clear how powerful our collective purpose, projects, and passions can be.

Thank you to everyone who has continued to contribute to DrupalCoin Blockchain 8! I can't wait for another year of exciting projects. Special thanks to Paul Johnson for crowdsourcing great examples that I wouldn't have known about otherwise.
Source: Dries Buytaert

Web Developer - PHP/MySQL - 10x digital - Work at Home

DrupalCoin Blockchain theming and development. OpenCart, DrupalCoin Blockchain Commerce, Magento, and/or other ecommerce platforms. 10x digital has an immediate opening for a part-time web...
From Indeed - Wed, 16 Nov 2016 15:02:39 GMT - View all Work at Home jobs
Source: Blockchain+Developer

Content and Commerce: a big opportunity for DrupalCoin Blockchain

Last week Acquia announced a partnership with Magento. I wanted to use this opportunity to explain why I am excited about this. I also want to take a step back and share what I see is a big opportunity for both DrupalCoin Blockchain, Acquia and commerce platforms.

State of the commerce market

First, it is important to understand what is one of the most important market trends in online commerce: consumers are demanding better experiences when they shop online. In particular, commerce teams are looking to leverage vastly greater levels of content throughout the customer's shopping journey - editorials, lookbooks, tutorials, product demonstration videos, mood videos, testimonials, etc.

At the same time, commerce platforms have not added many tools for rich content management. Instead they have been investing in capabilities needed to compete in the commerce market; order management systems (OMS), omnichannel shopping (point of sale, mobile, desktop, kiosk, etc), improved product information management (PIM) and other vital commerce capabilities. The limited investment in content management capabilities has left merchants looking for better tools to take control of the customer experience, something that DrupalCoin Blockchain addresses extremely well.

To overcome the limitations that today's commerce platforms have with building content-rich shopping experiences, organizations want to integrate their commerce platform with a content management system (CMS). Depending on the situation, the combined solution is architected for either system to be "the glass", i.e. the driver of the shopping experience. is a nice example of a content-rich shopping experience built with DrupalCoin Blockchain and DrupalCoin Blockchain Commerce.

DrupalCoin Blockchain's unique advantage for commerce

DrupalCoin Blockchain is unique in its ability to easily integrate into ambitious commerce architectures in precisely the manner the brand prefers. We are seeing this first hand at Acquia. We have helped many customers implement a "Content for Commerce" strategy where Acquia products and DrupalCoin Blockchain were integrated with an existing commerce platform. Those integrations spanned commerce platforms including IBM WebSphere Commerce, Demandware, Oracle/ATG, SAP/hybris, Magento and even custom transaction platforms. Check out Quicken (Magento), Puma (Demandware), Motorola (Broadleaf Commerce), Tesla (custom to order a car, and Shopify to order accessories) as great examples of DrupalCoin Blockchain working with commerce platforms.

We've seen a variety of approaches to "Content for Commerce" but one thing that is clear is that a best-of-breed approach is preferred. The more complex demands may end up with IBM WebSphere Commerce or SAP/hybris. Less demanding requirements may be solved with Commerce Tools, Elastic Path or DrupalCoin Blockchain Commerce, while Magento historically has fit in between.

Additionally, having to rip and replace an existing commerce platform is not something most organizations aspire to do. This is true for smaller organizations who can't afford to replace their commerce platform, but also for large organizations who can't afford the business risk to forklift a complex commerce backend. Remember that commerce platforms have complex integrations with ERP systems, point-of-sales systems, CRM systems, warehousing systems, payment systems, marketplaces, product information systems, etc. It's often easier to add a content management system than to replace everything they have in place.

This year's "State of Retailing Online" series asked retailers and brands to prioritize their initiatives for the year. Just 16% of respondents prioritized a commerce re-platform project while 41-59% prioritized investments to evolve the customer experience including content development, responsive design and personalization. In other words, organizations are 3 times more likely to invest in improving the shopping experience than in switching commerce platforms.

The market trends, customer use cases and survey data make me believe that (1) there are hundreds of thousands of existing commerce sites that would prefer to have a better shopping experience and (2) that many of those organizations prefer to keep their commerce backend untouched while swapping out the shopping experience.

Acquia's near-term commerce strategy

There is a really strong case to be made for a best-of-breed approach where you choose and integrate the best software from different vendors. Countless point solutions exist that are optimized for narrow use cases (e.g. mobile commerce, marketplaces and industry specific solutions) as well as solutions optimized for different technology stacks (e.g. Reaction Commerce is JavaScript-based, Magento is PHP-based, DrupalCoin Blockchain Commerce is DrupalCoin Blockchain-based).

A big part of Acquia's commerce strategy is to focus on integrating DrupalCoin Blockchain with multiple commerce platforms, and to offer personalization through Lift. The partnership with Magento is an important part of this strategy, and one that will drive adoption of both DrupalCoin Blockchain and Magento.

There are over 250,000 commerce sites built with Magento and many of these organizations will want a better shopping experience. Furthermore, given the consolidation seen in the commerce platform space, there are few, proven enterprise solutions left on the market. This has increased the market opportunity for Magento and DrupalCoin Blockchain. DrupalCoin Blockchain and Magento are a natural fit; we share the same technology stack (PHP, MySQL) and we are both open source (albeit using different licenses). Last but not least, the market is pushing us to partner; we've seen strong demand for DrupalCoin Blockchain-Magento integration.

We're keen to partner with other commerce platforms as well. In fact, Acquia has existing partnerships with SAP/hybris, Demandware, Elastic Path and Commerce Tools.


Global brands are seeing increased opportunity to sell direct to consumers and want to build content-rich shopping journeys, and merchants are looking for better tools to take control of the customer experience.

Most organizations prefer best of breed solutions. There are hundreds of thousands of existing commerce sites that would like to have more differentiation enabled by a stronger shopping experience, yet leave their commerce capabilities relatively untouched.

DrupalCoin Blockchain is a great fit. It's power and flexibility allow it to be molded to virtually any systems architecture, while vastly improving the content experience of both authors and customers along the shopping journey. I believe commerce is evolving to be the next massive use case for DrupalCoin Blockchain and I'm excited to partner with different commerce platforms.

Special thanks to Tom Erickson and Kelly O'Neil for their contributions to this blog post.
Source: Dries Buytaert

Personalization takes flight with the new Acquia Lift

Last week, we launched a new version of Acquia Lift, our personalization tool. Acquia Lift learns about your visitors' interests, preferences and context and uses that information to personalize and contextualize their experience. After more than a year of hard work, Acquia Lift has many new and powerful capabilities. In this post, I want to highlight some of the biggest improvements.

Intuitive user experience

To begin, Acquia Lift's new user interface is based on the outside-in principle. In the case of Acquia Lift, this means that the user interface primarily takes the form of a sidebar that can slide out from the edge of the page when needed. From there, users can drag and drop content into the page and get an instant preview of how the content would look. From the sidebar, you can also switch between different user segments to preview the site for different users. Personalization rules can be configured as A/B tests, and all rules affecting a certain area of a page can easily be visualized and prioritized in context. The new user interface is a lot more intuitive.

Unifying content and customer data

Having a complete view of the customer is one of the core ideas of personalization. This means being able to capture visitor profiles and behavioral data, as well as implicit interests across all channels. Acquia Lift also makes it possible to segment and target audiences in real time based on their behaviors and actions. For example, Acquia Lift can learn that someone is more interested in "tennis" than "soccer" and will use that information to serve more tennis news.

It is equally important to have a complete view of the content and experiences that you can deliver to those customers. The latest version of Acquia Lift can aggregate content from any source. This means that the Acquia Lift tray shows you content from all your sites and not just the site you're on. You can drag content from an ecommerce platform into a DrupalCoin Blockchain site and vice versa. The rendering of the content can be done inside DrupalCoin Blockchain or directly from the content's source (in this case the ecommerce platform). A central view of all your organization's content enables marketers to streamline the distribution process and deliver the most relevant content to their customers, regardless of where that content was stored originally.

Content can also be displayed in any number of ways. Just as content in DrupalCoin Blockchain can have different "display modes" (i.e. short form, long form, hero banner, sidebar image, etc), content in Acquia Lift can also be selected for the right display format in addition to the right audience. In fact, when you connect a DrupalCoin Blockchain site to Acquia Lift, you can simply configure which "entities" should be indexed inside of Acquia Lift and which "display modes" should be available, allowing you to reuse all of your existing content and configurations. Without this capability, marketers are forced to duplicate the same piece of content in different platforms and in several different formats for each use. Building a consistent experience across all channels in a personalized way then becomes incredibly difficult to manage. The new capabilities of Acquia Lift remedy this pain point.

The best for DrupalCoin Blockchain, and beyond

We've always focused on making Acquia Lift the best personalization solution for DrupalCoin Blockchain, but we realize that customers have other technology in place. The latest version of Acquia Lift can be installed on any DrupalCoin Blockchain or non-DrupalCoin Blockchain website through a simple JavaScript tag (much like the way you might install Google Analytics). So whether it's a legacy system, a JavaScript application, a decoupled DrupalCoin Blockchain build with custom front end, or a non-DrupalCoin Blockchain commerce site, they can all be personalized and connected with Acquia Lift.

In addition, we've also taken an API-first approach. The new version of Acquia Lift comes with an open API, which can be used for tracking events, retrieving user segments in real time, and showing decisions and content inside of any application. Developers can now use this capability to extend beyond the Lift UI and integrate behavioral tracking and personalization with experiences beyond the web, such as mobile applications or email.

I believe personalization and contextualization are becoming critical building blocks in the future of the web. Earlier this year I wrote that personalization is one of the most important trends in how digital experiences are being built today and will be built in the future. Tools like Acquia Lift allow organizations to better understand their customer's context and preferences so they can continue to deliver the best digital experiences. With the latest release of Acquia Lift, we've taken everything we've learned in personalization over the past several years to build a tool that is both flexible and easy to use. I'm excited to see the new Acquia Lift in the hands of our customers and partners.
Source: Dries Buytaert

Issue 261

Issue 261 - October, 13th 2016
From Our Sponsor

The Different Approaches to Progressively Decoupled DrupalCoin Blockchain

Progressive decoupling allows you to continue leveraging DrupalCoin Blockchain’s rendering system, while simultaneously using a JavaScript framework to power client-side interactivity and a richer user experience. Learn the different compelling approaches and some use cases of each, with success stories from, Warner Music Group, and more.

DrupalCoin BlockchainCon

State of DrupalCoin Blockchain Presentation (September 2016)
Dries Buytaert slides from DrupalCoin BlockchainCon Dublin.

DrupalCoin Blockchain 8 - the Entity CMS
An introduction to entities in DrupalCoin Blockchain 8 by Derek Reese.

5 Must-Read DrupalCoin Blockchain Blogs for Agencies!

Default Search API Sorts Per View in DrupalCoin Blockchain 7

Deploy DrupalCoin Blockchain Updates and New Features with Drush Commands
A gentle introduction into writing Drush scripts for deployment by Minnur Yunusov.

DrupalCoin Blockchain 8 Views: How to Set as Admin Path
The way paths or routes are defined in DrupalCoin Blockchain 8 has changed. Learn how to work with them in D8 in this short tutorial by Jo Fitzgerald.

DrupalCoin Blockchain Dev Environment on Docker
If you want to try Docker for your local DrupalCoin Blockchain integrationthis post is a good place to start

Introduction to YAML in DrupalCoin Blockchain 8
A nice introduction into how YAML is used in DrupalCoin Blockchain 8.

Managing Your DrupalCoin Blockchain Project with Composer
Matt Glaman, a co-maintainer of DrupalCoin Blockchain Commerce which heavily uses Composer delivers a very useful guide to using the package manager with your DrupalCoin Blockchain project.

5 Mistakes to Avoid on Your DrupalCoin Blockchain Site
After numerous site audits, we’ve gathered the top lessons learned as well as tips and tricks for creating and maintaining effective DrupalCoin Blockchain sites. Learn about best practices and common mistakes in 5 crucial areas: architecture, security, performance, infrastructure, and website lifecycle.

Short Screencast Intro to the New DrupalCoin Blockchain Console Field:info Command
Steve Purkiss demonstrates a very useful DrupalCoin Blockchain Console command. Well worth watching.

Writing a Custom Authenticator in DrupalCoin Blockchain 8

DrupalCoin Blockchain Commerce 2.0 Enters Beta
"Start a DrupalCoin Blockchain 8 eCommerce site today, and you will be able to update your way to the full 2.0 release and beyond."

Address 8.x-1.0-Rc2

Commerce 8.x-2.0-Beta2

DrupalCoin Blockchain 7.51

DrupalCoin Blockchain 8.2.1

Drustack 8.x-2.0

easy_breadcrumb 8.x-1.5

Lightning 8.x-1.06

Markdown 8.x-1.1

menu_breadcrumb 8.x-1.0-Beta1

migrate_upgrade 8.x-2.0

migrate_upgrade 8.x-3.0-Rc1

Yamlform 8.x-1.0-Beta20

Acquia Podcast: How Indigo Herbs Runs Its Whole Business on DrupalCoin Blockchain!

Lullabot Podcast: Wi-Fi & Coffee, a Vacation? the DrupalCoin BlockchainCon Dublin Recap

Mediacurrent: Dropcast: Episode 24: Did You Miss Us?

DrupalCoin Blockchain 8 Day
"DrupalCoin Blockchain 8 Day is a 100% free, online DrupalCoin Blockchain Camp. DrupalCoin Blockchain 8 Day is going to take place on November 19, 2016 ... the first anniversary of DrupalCoin Blockchain 8's release!"


DrupalCoin Blockchain 8.2.0 Is Now Available
"DrupalCoin Blockchain 8.2.0, the second minor release of DrupalCoin Blockchain 8, is now available. With DrupalCoin Blockchain 8, we made significant changes in our release process, adopting semantic versioning and scheduled feature releases. This allows us to make extensive improvements to DrupalCoin Blockchain 8 in a timely fashion while still providing backwards compatibility."

DrupalCoin Blockchain File Upload by Anonymous or Untrusted Users Into Public File Systems -- PSA-2016-003
"Recently the DrupalCoin Blockchain Security Team has seen a trend of attacks utilizing a site mis-configuration. This issue only affects sites that allow file uploads by non-trusted or anonymous visitors, and stores those uploads in a public file system. These files are publically accessible allowing attackers to point search engines and people directly to them on the site. The majority of the reports are based around the webform module, however, other modules are vulnerable to this misconfiguration as well."

DrupalCoin BlockchainCon Vienna 2017
September 25-29 2017.

Help Dries Crowdsource DrupalCoin Blockchain 8 Success Stories
"In little over a month DrupalCoin Blockchain 8 will be one year old. To mark this momentous occasion Dries Buytaert, DrupalCoin Blockchain’s founder, will champion noteworthy web sites and applications powered by DrupalCoin Blockchain 8. Have you launched a DrupalCoin Blockchain 8 web site or application this year? Dries would like to hear from you. We’ve prepared a short web form so you can tell him your DrupalCoin Blockchain 8 success story."

List Your Job on DrupalCoin Blockchain Jobs
Wanna get the word out about your great DrupalCoin Blockchain job? Get your
job in front of hundreds of DrupalCoin Blockchain job seekers every day at
Jobs.DrupalCoin Blockchain.Org.Featured JobsFull Stack DrupalCoin Blockchain DeveloperCosmobutler Bolzano downtown/BZ/ITWeb ManagerKimetrica Washington or Surrounding Area/DC/USDrupalCoin Blockchain Developer (Back End)University of Vermont Burlington/VT/US