Content Before Code - A D8 Case Study
summary
Project integrates GatherContent API with Drupal 8 using a custom migration source plugin (YAML + migrate module) so content authors produce structured pages, profiles and events before development. Client restructures old content, runs Treejack usability each sprint, and the site moves from code-complete to live in a two-week launch window. Team limits fields (title, lead, body), automates pulls at demos, and repeats migrations for menus, taxonomies and profiles; it works.
AI-written summary · about
chapters (21)
- 0:00Content Before Code A D8 Case Study
- 3:32Development Operations Manager
- 6:07Code doesn't become a website until there is navigation and content. Very few of the sites we build have no editorial content.
- 7:07AcademyHealth: ion Outcomes
- 8:50Client evaluated how their content and menu structure functioned within the site at the end of each sprint during development.
- 10:06Client had quick turnaround time between the end of development and the site launch.
- 10:58Client validated information architecture and design through collaborative in person and virtual user testing.
- 12:40Included content planning as part of the overall development planning.
- 13:08Created a schedule with deadlines for both new content and migration source data to set up our entire team for success.
- 13:52When we don't know where content is coming from, we can't plan functionality (let alone start development).
- 17:15Guide clients away from unstructured content found in .ppt or .doc formats as it cannot be easily migrated.
- 21:04We used existing content as the foundation of our design and to inform the hierarchy and selection of design components.
- 24:45With guardrails in place, we can migrate content automatically.
- 29:07Advantages: Familiar structured content. Limitations: Too easy to change fields, difficult to read.
- 31:11Content Development Tools: Updates in existing Content
- 32:56Content Development Tools: GatherContent
- 35:09Advantage 2: Fast turn around time between development phase and site launch.
- 35:43Limitation 1: Client may lack familiarity with tool. Limitation 2: Cost.
- 36:21Rationale: Preferred communication method/editorial review process for some clients.
- 37:27Limitations: Lack of hierarchy, can't import automatically, no version control.
- 38:13Find a tool the content development folks will use, and that
related talks
50mContent as code, technical writers as developers
17mA case study: Ditching the paper for Drupal
47mEngineering Documentation
59mTransforming your Documentation Process
19mA JCR View of the World: Everything is Content
46mContent Design Saves Your Forms
21mDrop your Excel Sheets: Drupal native editorial planning
26mWhat you get when you invest Non-Docs time in Docs tools