Blog

This week we get hands-on with Domain Access as we continue the Introduction to Domain Access for Drupal 7 series. We'll walk through configuring our Apache virtual host (vhost) so all three of our domain names are pointing to the same Drupal site. With that configured properly we can get the Drupal site installed and then install Domain Access. There is a little extra installation step required for Domain Access to do its magic. After we have it up and running we spend some time looking at and understanding the main Domain Access settings, get our other domain names added to the site, and dive into working with content. We're going to learn how to share content across all three domains, as well as be able to restrict some content to only certain domains.

We've recently been using Trello to help us track our content publication workflow. Here's a little bit about why and how we use it.

We're kicking off a campaign to help the Drupal 8 Accelerate Fund. If you donate $50 or more to the community fund, you have a chance to win a free annual membership and if you donate $100, you can choose a new video for us to create.

Our entire team will be at DrupalCon Los Angeles in just a few weeks. We'd love to chat with you, so here is where you'll be able to find us.

This week we're pleased to add another series that addresses multiple sites in a different way from the core multisite feature, with the Introduction to Domain Access for Drupal 7 series. This series covers the basics of working with Domain Access to manage multiple domain names all on one Drupal instance—only one code base and one database.

Let’s take a brief look at how translation contributions work in Drupal. This written tutorial is based on the free video, Translation in Drupal.

Design work is a lot of show-and-tell. It can be challenging to effectively communicate and collaborate on a distributed team. Join hostess Amber Matz, Lullabot Creative Director Jared Ponchot, Lullabot UX Designer Jen Witkowski, and Justin Harrell, Interactive Designer for Drupalize.Me, as they talk about the unique challenges, processes, and tools they use as part of a distributed team.

This week, we're wrapping up our series, Introduction to Object-oriented PHP, in partnership with KnpUniversity, with tutorials on access control for properties, type hinting, and constructors in PHP.

Here's an example of an assumption; The sun will rise tomorrow. An assumption is something that is accepted as true or as certain to happen, without proof. This kind of thinking, while convenient, is prone to concealing facts, and troublesome when debugging code. This article defines what an assumption is, and provides some techniques for helping to eliminate them during debugging.

This week, we continue our Introduction to Object-oriented PHP series, in partnership with KnpUniversity (now SymfonyCasts), with tutorials that mostly focus on working with objects in PHP. You'll also learn how to add a specially formatted comment to your code that will enable code autocomplete functionality in your IDE.

While a lot of our days are focused on Drupal, as web developers there are other pieces of tech that we need to understand and use on a regular basis. One example is Apache web server. This is the most popular web server on the web and likely the one your site uses. While you don't need to be a system administrator to use Drupal, you do need to understand some basics of Apache when working with domain names, especially if you're managing multiple domain names on one web server.

At the beginning of this month, we introduced a new feature on the site: self-serve group memberships! In the olden days, when a group wanted to purchase a membership, we asked that they email us. We then generated an invoice and emailed it back. No longer! Now, groups can purchase 5-seat memberships directly from our site—no emailing or invoicing required. Not only is the signup process now very straightforward, but you can purchase a group membership on a monthly basis in addition to the annual option.