Understanding Drupal: A Complete Guide to Caching Layers

It is that time of year, again! It is DrupalCon time! Woooooo. Last year DrupalCon Baltimore saw 3,271 attendees, and I'm thinking Nashville will bring in more (because, Nashville.) When this publishes and hits various feeds, I will be on the road and (hopefully) an hour into the eight-hour drive to Nashville with my family.

In prep for DrupalCon Nashville, I was working on our Drupal Commerce demo sites that we'll be showing off.

Back in February, I automated some of my content workflows. I use the Scheduler module to publish posts and have them automatically pushed into Buffer to be shared across my social networks. I'm attempting a new experiment once this node publishes. This should show up at my Medium account, https://medium.com/@mglaman.

At the end of October 2017, I wrote about the new and upcoming changes to ContribKanban.com. I decided to migrate off of a MEAN stack and go to a more familiar (aka manageable) stack. I decided upon Drupal 8 to manage my backend. Drupal is what I do, and Drupal is amazing at modeling data. People can moan and whine - it handles data models like a boss. I decided to treat it as a "progressively" decoupled web application.

Every software release needs to have release notes. End users need to be able to understand what it is that they are upgrading to and any associated risks, or risks mitigated by upgrading and receiving bug fixes. Across the board proprietary and open source software projects either hit or miss on delivering decent release notes. During MidCamp I decided to help fix that problem for Drupal.org projects.

 MidCamp 2018 has come and gone. This was the regional Drupal camp's fifth year, and my fourth time attending (missed year one ?). The amazing group of organizers behind the conference makes it one of my favorites. MidCamp is a human first event -- everything is about accessibility.

At DrupalCon Dublin I caught Fabianx’s presentation on streaming and other awesome performance techniques. His presentation explained how BigPipe worked to me, finally. It also made me aware of the fact that, in Drupal, we have mechanisms to do expensive procedures after output has been flushed to the browser.

At Florida DrupalCamp, I got to talk to the DRUD team. They were demoing their DDEV tool, which is an open source local development stack. For a while I have been using my own platform-docker tool, which is a PHP based tooling command I used for scaffolding Docker, running Behat, and more. Instead of maintaining my already unmaintained tool, I decided to give DDEV a try and contribute back some things which I considered experience fixes.

A few days ago Dries posted To PESOS or to POSSE. I have been working on trying to blog more. And so far I have been successful. I have read his plans to implement POSSE. My goal is to follow some of the same patterns. In fact, that's the purpose of the trial-run post!

DrupalCamp London is coming around the corner! If you have the chance to go, I highly recommend it. The organizers put on a top-notch event. Last year I had the privilege of giving my first keynote at the conference.