Contentful Modeling and Migration

/ CLIENT

Children’s Health

/ PROJECT TYPE

Discovery

/ DURATION

2 months

/ DELIVERABLES

Design System Inventory

Content Inventory

Content Model

/ BACKGROUND

Children’s Health approached FFW for assistance with migrating portions of the website to Contentful. During our Discovery, we focused on the in-scope areas of the site, but also unearthed a treasure trove of insights that will guide both our teams in the ongoing migration to Contentful. 

/ APPROACH

To get the insight required to make recommendations, we needed:

1. Intake and workshops: Our team needed to understand what’s already been completed and documented. Workshops allow us to work through your goals for the site, platform requirements, UX vision, audiences, and features to inform and prioritize areas of focus.

2. Activities and deliverables: Reviewing the current website and tools allowed us to prepare a variety of deliverables created to guide the upcoming design and development of the updated website. 

Findings

Through a variety of workshops and discussions, we explored Children’s Health’s current web ecosystem,  integrations, and goals for the site migration to Contentful. Stakeholder participation was important in helping the FFW team understand Children’s Health’s requirements, constraints, and opportunities for growth.

Integration is key
With a number of systems integrated into the current site, including custom databases created by Children’s Health, proper integration and data flow will be key for success in future phases.

The website is very connected
While we only focused on three sections of the website, we found that much of the content across the site is intertwined with multiple sections.

Different teams & responsibilities
As with most large healthcare organizations, there are a number of different teams working on Childrens.com with specific responsibilities related to content and management.

Content is modular
Since content in WCM is already highly structured it is in a great place to migrate to a headless system; we’re going to continue to evolve this approach in our new system with an eye on reuse.

Hosting in Bynder
There’s an ongoing sentiment to bring different content into Bynder and to have it integrated effectively into the updated system.

Stakeholders
Next steps that go beyond Phase 1 will involve additional stakeholders and approval time. Timelines should be adjusted appropriately.

/ ARTIFACTS + DELIVERABLES

Design System Inventory

Content Inventory

Content & Design Inventory

We reviewed and mapped content that will be moved to Contentful from the in-scope pages.

Key findings include:

• Different content was visually represented with similar content patterns; we heard that pages felt static/flat and there is interest in making them more dynamic or visually interesting.

• Authoring templates for Conditions, Treatments, and the Health & Wellness library are very fixed.

• Flexible components were not available to build new content requiring authors to manually code visual elements and interactions.

• Content from out-of-scope areas of the site was both dynamically and manually added to in-scope areas of the site.

Content Modeling Workshop

Content Model

Visual Content Model

Content Model

A content model was created based on both the Design System inventory and existing Content Model/templates. This document contains the recommended structure for content types and components in the new system.

Key findings include:

• There’s content whose structure and authoring process lives outside of the CMS, this makes the migration and synchronization process more complex.

• There’s an opportunity to reuse existing content types to ease the process of creating new content and have a more robust model to contain the data that gives life to the website and different channels.

• New content model was designed considering future phases as well as supporting some of the main entities living outside of contentful.

• Contentful offers a mature set of apps/integrations that will unify in a single place processes that currently run independently.

UI Mapping + User Guide

/ OUTCOMES

coming soon