We share knowledge, ideas and ambitions openly,
constantly improving and critiquing our ideas in the larger community.
On a recent project we had to create a section that is basically a Twitter search for a hashtag. It needed to be usuable in different sections of the layout and work the same. Continue reading →
Meetings are an inevitable part of creating an awesome product. The Scrum methodology has a set of meetings that were designed to help a team be productive, working on the most relevant, prioritized requests and features first. Continue reading →
Actually, we never left. We didn’t stop building Drupal sites, even through the long release cycle. However, we did move our company website, activelamp.com, 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.
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).
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 activelamp.com on Drupal 8 in Q3 of this year. Continue reading →
Drupal 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. Continue reading →
When you hear the terms strategy and tactics, what do you think of? It is extremely common for people to confuse the two ideas. In fact, many people believe that strategy and tactics mean the exact same thing. There is a clear difference between the two, and having a proper understanding of each is extremely important. Continue reading →
Recently, I have been tasked to create an automated content creator for end to end testing. This project should be able to create a drupal content type AND show the steps on how it is done properly. We could say that our team wanted to replicate a user workflow, automatically. Continue reading →
The 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:
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 my github page if you want the speaker notes too. Continue reading →
The 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