We've made a number of updates to both tutorials and topic pages this past quarter. The updates we made related to Drupal's 8.8.x minor release update (which introduced some big changes) and to our content archiving project, which we wrote about previously.

We're excited to announce that sandbox environments powered by Tugboat are now live and ready for Drupalize.Me members to use while following our Drupal Views tutorials!

You might have noticed some changes on Drupalize.Me lately. We've just wrapped up a huge content archiving project and I'd like to share what we did and how this will help us move forward with a library of tutorials for Drupal learners that we're committed to keeping up-to-date.

The beginning of a new year always seems like a good time to take some time for reflection. While we started to do that the past couple of weeks, in an effort to wrap up some end of the year goals and finalize plans for how we wanted to start 2020, we realized that it's been quite a while since we've written about projects we're working on for the site. With Drupal 9's release planned for June of 2020 now is a great time to do this reflecting and planning work.

We're excited to publish a new set of tutorials on Drupal's Views module. This set of tutorials includes a database starting point and instructions for setting up a local development environment with DDEV so that you can follow along. The database includes an extensive set of baseball stats data so that we could demonstrate the power of Views to filter, sort, display, theme, and build customized lists in blocks, pages, API endpoints, and more.

We're excited to launch a new series of tutorials for Drupal 8: Content Moderation and Workflows! The Workflows and Content Moderation modules allow an editorial team to put any type of content administered in Drupal through a customized editorial workflow and moderation process. Workflow states, such as draft, ready for review, or approved are defined using the Workflows module. The ability to attach moderation states to entity bundles -- such as content types -- is configurable by the Content Moderation module.

In this series, you'...

We recently started using Vale to help automate the tedious task of enforcing our style guide. Doing so has helped make reviews faster, and reduced any hard feelings between us. Emotions can run high when you feel someone is being overly scrupulous in their review of something you've worked really hard to create.

We're sad to miss DrupalCon Europe in Amsterdam next week (October 28-31, 2019). But which talks would we attend if we were going? Amber and Joe combed through the program and created a list of what looks intriguing to us at the next DrupalCon. Will you be there? You might want to check out our picks.

I began my DrupalEasy journey with the greatest of intentions. Jumping in head first, I upgraded to Windows 10 Pro, set up a new local development environment — I highly recommend DDEV for its power and flexibility, and because it allows development teams to use Docker in their workflow — and reacquainted myself to Composer and the command line. If there was a roll, I was on it. Then week 2 happened.

In a recent support question, one of our members asked about consuming REST APIs with Drupal 8. Joe Shindelar took on the question and found in trying to answer the question he first needed to know more about what they are trying to accomplish. Like with most things Drupal, there's more than one right way to accomplish a task. Choosing a solution requires understanding what options are available and the pros and cons of each. This got Joe thinking about the various different ways one could consume data from an API and display it using...

“What is Drupal?” describes where I was when I joined the Osio Labs team last summer as People Support. Beginning August 26, I’m taking DrupalEasy’s Drupal Career Online program and I’m thrilled to be taking this next step in my Drupal journey. I'll be blogging about it here so if you’re a beginner like me, hopefully there’ll be something to aid you in your learning process, to encourage you when you’re feeling stuck, or to support you on your own road to Drupal proficiency.

Hey Node didn’t arise just from me or any single member of my team. At our 2017 company retreat, we had a long conversation about our personal and business goals for the next five years. We decided we wanted to grow the company -- but in a deliberate and meaningful way. We also wanted to be mindful about taking our most formative lessons from Drupalize.Me, and applying them to our next project. It took us another year of research to decide to work with the Node community and build Hey Node.