Web services and APIs (application programming interfaces) are hot topics among Web developers -- for two good reasons.
- Many developers now want to expose content and features on their site via Web services or APIs.
- It's getting easier to take advantage of these services. Drupal 8, for example, now has this capability in core. And some contributed modules are attempting to make it even better.
This is why Acquia and Palantir.net, the Chicago-based Web strategy, development, and design firm, have been working together on a Web services series.
Recently I had a customer ask me how to tell Drupal 8 to display certain blocks conditionally, based on whether or not the node page being viewed referenced certain taxonomy terms. In Drupal 7 I would have recommended the Context module for this, but as it’s not yet ready for Drupal 8 I had to go looking for other options.
My search led me fairly quickly to the brand-new Block Visibility Groups module, which aims to provide the same sort of conditional block visibility functionality that Context provides, but in a manner that integrates more closely with the core Block UI. It works well, but doesn’t natively provide support for basing visibility off of node field data (such as taxonomy term references). However, since Block Visibility Groups uses the core D8 Condition plugin type to define its conditions, all that’s needed is to implement a custom plugin to get the desired behavior. Here’s how it works, from start to finish:
This is Part 2 of an interview with Will Eisner, Senior Director, Product at Acquia. Will’s primary focus is on Acquia Cloud Site Factory, which helps organizations create and manage many sites, from a dozen to thousands.
In Part 1, Will discussed how companies often discover, to their dismay, that they are running hundreds of Web sites, on many different platforms. In this section of the interview, Will describes how Site Factory addresses that problem.
The interview was conducted by DC Denison, Senior Editor, Technology, at Acquia, who is represented by the letter “Q.”
As the organizer of the Washington, DC Drupal meetup for three years, I've had the benefit of finding out what works and what doesn’t when setting up a meetup. Although I recently had to step away from my organizing duties due to other commitments, I'd like to provide a retrospective on what I've learned from organizing meetups. My goal is to help those who want to set up a meetup in their area for the first time, and to help provide ideas for those who are already running a meetup.
Each day, more Drupal 7 modules are being migrated to Drupal 8 and new ones are being created for the Drupal community’s latest major release. In this series, the Acquia Developer Center is profiling some of the most prominent, useful modules, projects, and tools available for Drupal 8. This week, a handy-dandy usability module called Linkit.
We've been talking to our clients about Drupal upgrades a lot lately. This is not surprising, of course, given the recent release of Drupal 8, which signaled the end of life for Drupal 6.
The Drupal community is excited about all that Drupal 8 has to offer. If you’re on Drupal 6, however, that excitement may be muted by the feeling that you're between platforms. You want to be thoughtful about your next steps. You want to anticipate all the possible consequences. The stakes are high.
Here at Advomatic we've been involved in many, many Drupal upgrade decisions in the last few months. We've gotten good at helping customers navigate the options.
So what are we now telling our current customers, and prospective customers? Read on.
It's a good time to press your advantage as a Drupal developer.
Drupal 8 has launched, and it's much easier now for Drupal developers to expose content and features on their sites via an API. The capability is built right into Drupal 8 Core. Some contrib modules are attempting to make such capabilities even better.
Each day, more Drupal modules are being migrated from Drupal 7 to Drupal 8 and new ones are being created for the Drupal community’s latest major release. In this series, the Acquia Developer Center is profiling some of the most prominent, useful modules available for Drupal 8. This week: Paragraphs.
In this 3-part Drupal How-To series, I'm going to show you various options for configuring images on your site.
In Part 1, we looked at how to tweak the default image options. Here, in Part 2, we'll see ways to allow inline images. In Part 3, we'll see the latest options for responsive images.
This post may be of interest to project managers and sitebuilders looking to migrate from Drupal 6 to Drupal 8 during the early months after the launch of GA D8.
On the Acquia Support Team we often find ourselves using Acquia’s public-facing documentation and article library as an effective tool for explaining product-related tasks, technical how-tos, and a variety of other topics. These resources are useful when communicating via our Support Help Center. Unfortunately, the underlying infrastructure for this site was Drupal 6.37.
There are some excellent improvements to modeling data in Drupal 8, including a number of new fields. This is going to make it easier to model content in Drupal. Let’s look at the image handling in Drupal 8 and what changes are in store.
Larry "Crell" Garfield led the Drupal 8 Web services Initiative.
The mandate: to make Web services better in Drupal. Or, as the group phrased it in their mission statement, "Drupal needs to evolve from a first-class CMS to a first-class REST server with a first-class CMS on top of it."
Some time ago we were contacted by a client to execute a migration: from a soon-to-be decommissioned site into Drupal.
Just when we thought that it would be a simple process, the requirements came in: “Migrate the data from Site A into Drupal, but also join data from Spreadsheet X, and some data already inside the Drupal website.”
To handle such complicated task, with so much different data, we chose the Migrate module to make our lives easier.