I've been continually defining and redefining the goals of the Schema.org Blueprints module for Drupal. Initially, I started with the simple goal of taking a Schema.org-first approach to building standardized content models in Drupal with JSON:API and JSON-LD to provide great APIs and fantastic SEO. The reality is that for myself and my organization, I am also working on building a best-in-class content management and authoring experience. Ultimately, this secondary goal has led me to reimagine how to build and maintain an instance of Drupal.

In short, there is so much going on with the Schema.org Blueprints modules that my presentation proposal for DrupalCon Portland is a live demo showing how to go from 0-60 with the Schema.org Blueprints module. I am confident that attendees will learn something valuable from my demo of leveraging Schema.org to build an ideal content authoring experience in Drupal. Still, I needed something direct and straightforward to define the overarching goal of the module and presentation, and I decided to prefix my session's title with "Love thy CMS!"

"Loving your CMS" has been floating around for a few years. For example, Greg Dunlap's presentation at DrupalCon Pittsburg and related blog post about Designing Content Authoring Experiences opens with the statement that "Most people don't love their content management system." A List Apart moderated a conversation between Eileen Webb, Karen McGrane, Jeff Eaton, and Ryan Irelan titled "Love Your CMS."

Drupal - the software and the community - makes it possible for people to love their CMS. Being able to build and alter every aspect of the CMS to cater to an organization's business requirements makes it feasible to construct the ideal content-authoring experience. The collaborative nature of the Drupal community enables us to improve and expand our tools and technology collectively. Whether Drupal is the best CMS or DXP could be debatable. I would argue that Drupal has the most potential to be loved.

The statement "Love thy CMS" appeared in an internal Zoom chat about the modernization of my organization's CMS. My co-worker and I were explaining the overarching technical goals for rethinking and modernizing the organization's Drupal implementation. On the call were stakeholders, an SEO specialist, site builders, and content authors. While presenting goals and features, I finally summed it up as "We want you to love your CMS." In the chat, someone simplified that statement into "Love thy CMS!" and the "thy" adds the tongue-in-cheek aspect, being it is hard to imagine loving a piece of software. Yet, Drupal has the potential to be loved, and this concept could become part of Drupal's marketing efforts.

The most recent Driesnote from DrupalCon Lille ends with a promise to "Amplify our marketing efforts to highlight the outstanding work happening in Drupal, and to expand Drupal's reach and influence in the market." Of course, marketing Drupal can't be boiled down to simply a three-word statement. Still, it helps to use "Love thy CMS!" to invite someone to learn more about Drupal and discover why and how they could love their CMS.

To end, I invite you to learn to "Love thy CMS" using the Schema.org Blueprint module at an upcoming Drupal event, including NEDCamp, hopefully at DrupalCon Portland in 2024. Please follow my blog to catch a recording of my session.