Series: Building This Site

Testing Content Requirements

Workcodingai

To properly test the site, we need actual content in Agility CMS. I've specified what content we need to create so we can test all the features properly.

Testing Content Requirements

Date: January 6, 2026
Phase: Phase 7 & 9 - Content & Testing
Status: In Progress

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).

To properly test the site, we need actual content in Agility CMS. I've specified what content we need to create so we can test all the features properly.

Content Requirements

Blog Categories (3 required)

I want to write about three main topics:

  1. "3rd spaces" - Places that are neither home nor work, but serve as important community gathering spots
  2. "football" - The beautiful game, tactics, analysis, and fandom
  3. "work" - Work, career, professional development, and workplace thoughts

Blog Tags (5 required)

I specified 5 tags but only listed 4, so we'll need to figure out the 5th one:

  1. "sports" - Sports-related content
  2. "theatre" - Theatre-related content
  3. "coding" - Coding and development
  4. "leadership" - Leadership and management
  5. (TBD - need to decide on 5th tag)

Sample Blog Posts

We need at least 3-5 sample blog posts to test:

  • Blog listing page displays correctly
  • Blog detail pages work
  • Category filtering
  • Tag filtering
  • RSS feed generation
  • Markdown processing
  • Gallery functionality

What's Been Created

The agent created the categories and tags in Agility CMS using the MCP server. Now we have:

  • ✅ 3 categories created
  • ✅ 4 tags created (5th TBD)

Next steps are to create sample blog posts, career entries, and uses items so we can properly test everything.

Joel's Thoughts / Reflections

After automatic content and component model creation, sample content creation in the CMS is the next best feature for MCP servers. Having a bunch of default content to test the site on without having to switch context from the IDE is a huge benefit. For this project, almost all of the non-page content was created by the agent, and it did a great job. Next iteration with Claude will, I hope, be able to create the page and component content automatically.