Teamwork is the lifeblood of project management at Chapter Three. Every project manager uses Teamwork a little bit differently and we each customize the experi...
It is time for the Drupal community to catch up the rest of the open source world and drop the module review process from Drupal.org.
I woke up this morning to see this series of tweets f...
As a Project Manager at a digital agency, I live and die by my inbox. It's where every PM tool I use converges into a hub of notifications, important documents, questions and change requests. Time is money. Spending time manicuring your inbox improves communication, reduces overhead and reduces oversights.
I often want to print the output of an Entity Reference field somewhere - a page template, a complicated node template, or in a custom module that is organizing data. In Drupal 7, you could do this...
I started an internal discussion with the team about the possibility of contributing an administrative theme to the community. Many were eager to help. A new Slack channel was born, and a impassioned flurry of ideas and concepts came pouring out.
When starting a new project we often outline our development process with our clients. The explanation helps our clients understand how important each aspect is to the immediate- and long-term success of their projects. This also illustrates the environment scheme needed.
Lately there has been much chatter about Drupal including a front-end framework in Drupal core. Dries has written a few times about the concept and has established that he’s interested in a future where Drupal is “progressively decoupled” from its front-end, leaving the front-end rendering to be handled piecemeal by a JavaScript framework like Angular or React. Progressive decoupling, far from being an industry standard, is a concept that has been coined in the last several months. Without a sucessful model to look at, we are staking our future on a reality that only exists in blog posts. The momentum of front end frameworks distracts from addressing more important issues, and has created a miasma of anxiety that Drupal is going to be “left-behind”, again.