Better decision making for content types and views

Drupal offers seemingly unlimited customization and flexibility when configuring content types and views. Too often, a high-level list of content types gets handed off to a developer, who is left to make guesses about the best way to set them up. No context for what content will end up in those containers or the needs of people entering the content. When it’s time to enter content, the build may not match the actual content. You end up with extra work, unhappy stakeholders, and probably late delivery of the website.

Working content modeling into the build planning saves time and money. Defining content types involves nuanced decision making and shouldn’t be left to one person to determine. It needs to be a team sport. Content, design, and development all need to work together to define content types and views. When you define this all together and ahead of time, the design, content, CMS build, and any other functionality can all be built at the same time. The result? Smoother implementation, more on-time and on-budget deliveries, and happier stakeholders and clients.  

In this session, we will

• Discover a process of using domain models to inform the Drupal content types
• See how content strategists and developers can support each other
• Discuss ways to involve stakeholders early to avoid surprises later
• Make sure Drupal user needs are supported so no one hates their CMS

Whether you’re new to Drupal or have been working in it for years, you’ll go away with a new way to think about how to create, manage, and connect content.