Digital Strategy, Design, Video Production, and Development Agency - Drupal PlanetPosts categorized as 'drupal planet'http://activelamp.comDrupal 8 Development in Docker - ReduxBack in December, Tom Friedhof <a href="">shared how we set up our Drupal 8 development and build process utilizing Docker</a>. It has been working well in the several months we have used it and worked within its framework. Within the time-span however, we experienced a few issues here and there which led me to come up with an alternative process which keeps the good things we like and getting rid of/resolving the issues we encountered.Thu, 14 Jul 2016 02:00:00 +0000 Things Every Jr. Drupal Web Developer Needs to KnowJonathan provides a list of 10 things that he feels every Jr. Drupal Web Developer needs to knowWed, 15 Jun 2016 02:00:00 +0000 custom fields in Drupal 8 - Part 2Continuing from Evan's blog post on building pages with Paragraphs and writing custom blocks of content as fields, I will walk you through how to create a custom field-formatter in Drupal 8 by example.Tue, 07 Jun 2016 02:00:00 +0000 custom fields in Drupal 8 - Part 1Creating custom fields for Drupal 8 are easy to create and can get great results paired with the paragraphs module.Fri, 03 Jun 2016 02:00:00 +0000 back to Drupal, it's fun again!Actually, we never left. We didn't stop building Drupal sites, even through the long release cycle. However, we did move our company website, [](, off of Drupal about 18 months ago. Our company site had been built on Drupal since the _Drupal 4.7_ days. That was back when it started to become uncool to write and maintain your own home-grown CMS. I eventually found Drupal, ditched my custom CMS, and never looked back.<br /><br />Our site started on _Drupal 4.7_, upgraded onto _Drupal 5_, then _Drupal 6_, and also _Drupal 7_ all at the beginning of the release cycles of Drupal. About 18 months ago, when our site was in dire need of an update, we evaluated _Drupal 8_ but realized with no release date in sight, and the fact that we did not want to chase HEAD and develop on unstable API's, we decided to go a different route and build our updated site on [Jekyll](, a popular static generator. **It's more fun to tinker with new technology when working on non-billable stuff**, which is what we did. We brushed up on our Ruby skills and built out a _Jekyll_ site (which is this site you're looking at if you're reading this blog post before Q3 of 2016).<br /><br />We're getting ready for another update to our company website and moving back to _Drupal_ to do it. _Jekyll_ was great, but it came with its disadvantages over something like _Drupal_. This post will highlight some of the advantages and disadvantages of working with _Jekyll_ the past 18 months, as well as highlight why we're excited to put on _Drupal 8_ in Q3 of this year.Tue, 17 May 2016 02:00:00 +0000 CKEditor plugins to Drupal 8Drupal 8 has greatly improved editor experience out-of-the-box. It comes shipped with CKEditor for WYSIWYG editing. Although, D8 ships with a custom build of CKEditor and it may not have the plugins that you would like to have or that your client wants to have. I will show you how to add new plugins into the CKEditor that comes with Drupal 8.Sat, 07 May 2016 02:00:00 +0000 2016 RecapThe San Diego Drupal Camp was great! You can't beat the weather in San Diego, and as usual, these regional events are great for catching up with old friends that are still plugging away with the Drupal content management system. Checkout our highlight video&#58; <a href="">![Sandcamp Highlight Video](/images/posts/sandcamp-video.jpg)</a> This year I had the pleasure of giving 3 sessions at the camp, and as promised, I want to share the slides and code for everything that I presented. Each deck is iframed in on this article, feel free to checkout <a href="">my github page</a< if you want the speaker notes too.Tue, 15 Mar 2016 02:00:00 +0000 Drupal: all about the service containerThe biggest thing that got me excited with Drupal 8 is the first-class use of services & dependency-injection throughout the entire system. From aspects like routing, templating, managing configuration, querying and persisting data, you name it -- everything is done with services. This is a *great* thing, because it grants developers a level of flexibility in extending Drupal that is far greater than what Drupal 7 was able to. I'll walk you through a few strategies of extending existing functionality, leveraging the power of Symfony's `DependencyInjection` component.Tue, 01 Mar 2016 02:00:00 +0000 a deployable Docker image with Jenkins - Part 4My previous posts talked about getting your local environment setup using the [Drupal Docker image]( with [Vagrant]( It's now time to bake a Docker image with our custom application code within the container, so that we can deploy containers implementing the [immutable server pattern]( One of the main reasons we starting venturing down the Docker path was to achieve deployable fully baked containers that are ready to run in whatever environment you put them in, similar to what we've done in the past with [Packer](, as I've mentioned in a previous post.Wed, 20 Jan 2016 14:30:00 +0000 build process using Drupal 8Now that the [release of Drupal 8]( is finally here, it is time to adapt our Drupal 7 build process to Drupal 8, while utilizing [Docker]( This post will take you through how **we** construct sites on Drupal 8 using dependency managers on top of [Docker with Vagrant]( <h3>Keep a clean upstream repo</h3> Over the past 3 or 4 years developing websites has changed dramatically with the increasing popularity of dependency management such as [Composer](, [Bundler](, [npm](, [Bower](, etc... amongst other tools. Drupal even has it's own system that can handle dependencies called [Drush](, albiet it is more than just a dependency manager for Drupal. With all of these tools at our disposal, it makes it very easy to include code from other projects in our application while not storing any of that code in the application code repository. This concept dramatically changes how you would typically maintain a Drupal site, since the typical way to manage a Drupal codebase is to have the entire Drupal Docroot, including all dependencies, in the application code repository. Having everything in the docroot is fine, but you gain so much more power using dependency managers. You also lighten up the actual application codebase when you utilize dependency managers, because your repo only contains code that you wrote. There are tons of advantages to building applications this way, but I have digressed, this post is about how we utilize these tools to build Drupal sites, not an exhaustive list of why this is a good idea. Leave a comment if you want to discuss the advantages / disadvantages of this approach.Wed, 02 Dec 2015 02:30:00 +0000