Phase 7: Content & CMS Integration

Date: January 6, 2026
Phase: Phase 7 - Content & CMS Integration
Status: Ready for Manual Completion

Note: This post is written from Joel's perspective (first person "I" = Joel). Technical details sections are clearly marked as written by the AI agent (Cursor - Claude Code).

Phase 7 is about populating the CMS with content and creating the actual pages. Most of this work needs to be done manually in Agility CMS, but the agent has prepared everything needed.

What's Ready

All the components, models, and infrastructure are in place:

• BlogPost model exists
• CareerEntry model exists
• Category and Tag models exist
• All component models are created
• Containers are set up
• Pages can be created using the "Main" page model

What Needs to Be Done

I'll need to:

1. Create the UsesItem content model (if not already created)
2. Populate content in the CMS:
   • Blog posts
   • Career entries
   • Uses items
   • Categories and tags
3. Create pages in Agility CMS:
   • Homepage (already has BlogListing)
   • /about page
   • /career page
   • /uses page
   • Individual blog post pages (dynamic)
4. Configure webhooks for revalidation
5. Test content updates and revalidation

Visual Reference: Page Structure in Agility CMS

This screenshot shows the homepage page editor in Agility CMS, displaying the "MainContent" zone with the BlogListing component.

Joel's Thoughts / Reflections

The biggest challenge in general with AI agents when working with Agility CMS is understanding the routing model with sitemaps, pages and components being pulled as JSON from the CMS. Other headless options just have content lists and items, so by default the agent tries to create shared content lists for stuff. I’m going to focus on making the AI content creation experience seamless - both through prompting and in the MCP server itself.