site-architecture

Plan and document website information architecture with page hierarchy, navigation, and URL structure.

787|36|Updated Apr 26, 2020
One-click install
npx skills add https://github.com/AvdLee/RocketSimApp --skill site-architecture-avdlee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: site-architecture
Source: https://github.com/AvdLee/RocketSimApp/tree/main/docs/.agents/skills/site-architecture
Command: npx skills add https://github.com/AvdLee/RocketSimApp --skill site-architecture-avdlee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and document website information architecture by outlining page hierarchy, navigation, and URL structure.

Core Features & Use Cases

  • Plan and map page hierarchies (L0-L3) to ensure intuitive navigation
  • Define consistent URL patterns, breadcrumbs, and internal linking strategies
  • Use cases include marketing sites, product docs, blogs, and resource portals

Quick Start

Provide a starter site inventory and draft a sitemap to begin planning.

Frequently Asked Questions about site-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is website information architecture and when do I need to plan it?

Website information architecture involves outlining page hierarchy, navigation, and URL structure to ensure intuitive user experiences. You need to plan it when building or restructuring SaaS marketing sites, content portals, documentation hubs, or hybrid platforms to guide scalable site organization.

How do I map page hierarchies and URL structure for a new website?

To map page hierarchies and URL structures, outline your site's L0-L3 page levels, define consistent URL patterns, and establish breadcrumb and internal linking strategies. You can visualize the structure using ASCII or mermaid diagrams with YAML frontmatter for metadata documentation.

Can I use this site architecture approach for both marketing sites and documentation hubs?

Yes, this information architecture planning approach supports SaaS marketing sites, product documentation, blogs, and resource portals. It adapts to different platform types by defining consistent navigation patterns, URL conventions, and internal linking strategies tailored to each specific use case.

What's the best way to document internal linking and navigation design?

Document internal linking and navigation design by outlining page hierarchies and aligning them with established navigation patterns and URL conventions. Use YAML frontmatter for metadata and ASCII or mermaid diagrams to visualize the structure, ensuring clear documentation for planning or restructuring tasks.

How do I start planning a sitemap for a site restructuring project?

Start planning a sitemap by providing a starter site inventory and drafting the initial sitemap structure. From there, define the page hierarchy, map out navigation patterns, and establish URL conventions to guide the restructuring process for your specific platform type.