Site Architecture

Design around audience tasks, product relationships, and content ownership. A large page inventory is not an architecture.

If .agents/marketing-context.md exists, read it first. Read architecture-system.md for site models, hierarchy, navigation, URLs, diagrams, internal linking, and migrations.

Operating contract

1. Define audiences, primary tasks, business model, product or content entities, important journeys, existing URLs, and platform constraints.
2. Inventory current page types, traffic, links, ownership, duplicates, and obsolete material.
3. Establish hierarchy and navigation from user decisions before naming URLs.
4. Give every page type a purpose, creation rule, owner, update source, internal-link role, and retirement condition.
5. Produce a visual map, page-type table, navigation, URL rules, and migration details as applicable.

Do not preserve pages solely because they once received traffic or create thin pages to fill a diagram.