Part 1 of 2 - I had the great pleasure of speaking with Lukas Smith at SymfonyCon Warsaw in December, 2013. Lukas is a major contributor to open source, touching a range of projects, including the Symfony framework, Drupal, and much more. He is one of the 50 most active contributors on GitHub. Thank you, Lukas!
In previous articles in this series, we’ve covered the areas of architecture, security and performance. All of these aspects are affected by your infrastructure from the time of development to deployment.
This blog post is a textual representation of the video shared yesterday. If you are visual learner, watch it. If you are in a hurry, read this blog :). Peter's video also shows how configuration_log module can be used to materialize all config changes in Prod so they may be easily integrated back into the codebase. That is not covered here.
Two weeks ago I had a great opportunity to spend a few days working with Moshe Weitzman (moshe weitzman), Justin Randell (beejeebus), Alex Bronstein (effulgentsia), and Stéphane Corlosquet (scor) to look at the challenges and best practices for using the new Drupal 8 configuration system (a.k.a. CMI) to move changes between a local development environment and one or more server environments.
Ryan Weaver is the single biggest contributor to the Symfony2 framework's documentation (which is excellent, check it out!), a self-described Symfony evangelist, and lead at KnpUniversity.com, makers of fantastic PHP tutorial screencasts like this one on using Composer to include PHP libraries in Drupal 7.
Performance is crucial for providing a great user experience. If the site is slow or balky, even great functionality won’t keep the site visitor engaged.
Whether you are just moving to Drupal or upgrading to a new version of Drupal, if you are starting with an existing website, you are facing the same problem: Your migration timeline. It will take you significant effort to move everything you have to the new system and you cannot play catch-up all the time. That’s why many people are opting for continuous migration. What does that mean? Run the migration project in parallel to your existing website effort and migrate gradually, page by page and URL by URL.
So you're contributing a module or theme to the greater Drupal community. Awesome! We're thrilled that you're sharing your work.
Naming your project may be one of the last things on your mind, but a poor naming choice could cause you issues down the road. Your project name ends up in a lot of places, including: Google Search Results, Drupal.org related project listings, the URL to the project, the title of your project page, Drush commands, the filenames of your project files, hook invocations in your project, and CSS classes, to name a few. A name that's used inconsistently can be confusing for users and cause integration issues.
There are several principles to consider and some are more important than others, so I've broken them into three categories: The Essentials, Strong Recommendations, and Further Suggestions.
Good security practices protect your site from hacker attacks. In this article we'll look at some methods for reducing security risks on your site.
This week's podcast is parts of a fun conversation I had with Ruben Teijeiro at Drupal Camp Vienna in December 2013. I "borrowed" him from mentoring Manuela Hutter at the code sprint to talk with me, but in the end, they both still managed to get a lot done that weekend. Thanks for your contributions, folks!
Drupal is one of the most flexible content management systems in existence. In this blog series, I'll go over five mistakes to avoid on your Drupal website which include: architecture, security, performance, infrastructure, and website lifecycle management.
Hat tip to my colleague Ryan MacInnis for prompting me to write this up!
From an architecture standpoint, these are the most vital decisions you'll make to ensure the success and performance of your Drupal website.
I spoke with Slovenian Drupalist-extraordinary Janez Urevc at Drupal Camp Vienna 2013. Alongside being a Drupal developer at examiner.com, he is also a major force in everything media+Drupal. Janez is slashrsm on Drupal.org, Twitter and "all the other online services you can imagine." He's on the team planning Drupal Camp Alpe-Adria 2014, which will be in the beautiful Slovenian resort town of Portoroz in May. Knowing the wonderful Drupal community in Slovenia (and the region around it) and the fantastic location, I highly recommend this camp!
2012 Greatest Hits - Drupal Camp Sofia, Bulgaria - A quick blast from the past this week from the first Drupal community event at which I was recording material for a podcast. This gives this particular event an extra sparkle in my memory. True to form for the Drupal community around the world, many of the people I met at this camp have become friends with whom I stay in touch with or even get to see now and then at a DrupalCon or Drupal Camp somewhere. Community ftw!
Drupal 8 Wins: Avoiding the Dead Hook Blues, Part 3 - Today we wrap up this mini series with Larry Garfield, Kris Vanderwater, and me answering the question "Do I need to learn Symfony to develop for Drupal 8?", getting the lowdown on plugins, and doing a wrap-up on the important points from our whole, 3-part conversation.
In our structured Drupal training program, we teach the "right way" to do things. We listen to our support team of client advisors who see all the permutations of "you're doing it wrong" in Drupal, and make sure we're leading learners in the right direction. When there's something particularly essential we use words like "Important" and set off warnings with a little exclamation mark icon.
Drupal 8 Wins: Avoiding the Dead Hook Blues, Part 2 - In today's conversation, Larry Garfield, Kris Vanderwater, and I go over the Go PHP 5 project as the first seeds of cooperation between different PHP projects, how the Symfony2 framework became part of Drupal 8, why we aren't building Drupal 8 on Symfony full-stack, CMI, abstraction in Drupal, and the future of Features in Drupal 8.
There are many great positions available for people who build Drupal sites. For anyone who knows PHP, Drupal is a great extension to your tool chain. Drupal’s unique site building model also allows for non-coding web development. Right now, the job market in Drupal is tipped in the favor of the job seeker. If you need help finding Drupal jobs, you’re in the right place.
Drupal 8 Wins: Avoiding the Dead Hook Blues, Part 1 - In August 2013, I spoke with Larry Garfield and Kris Vanderwater in a 90+ minute live Hangout on Air about the origins, details, and implications of the big architectural changes coming in Drupal 8. Today's video and audio podcasts are the first set of "curated" excerpts from that long conversation. We cover Larry and Kris's Drupal backgrounds, early Drupal memories, compare Drupal 4 to Drupal 7 and 8, some pragmatic reasons to choose Drupal, and how to get your head around the Symfony2 framework.
I met Anthony, aka @ircmaxell, for the first time at the PHP BeNeLux conference in early 2013. He was among the first people I spoke with on mic about PHP. Our conversation about PHP being secure was one of the seeds that grew into the "Power of PHP" series on Acquia.com, though you'll notice we were still calling it "PHP Myths" at the time. The series will be continuing in 2014, stay tuned to the Acquia podcast and the Acquia blog for more!