page▌

Guides solutions pages focused on business outcomes. Industry-first is the B2B norm (Salesforce, HubSpot). Answer "what outcome do I get for my industry/team/size?" rather than "what does it do?" Distinct from features (capabilities) and use cases (scenarios); solutions emphasize measurable value by segment.

Guides integrations, plugins, and extensions pages. Shows how the product connects with Canva, Slack, Zapier, and other platforms. Common for SaaS, tools, and developer products.

Guides documentation site structure, navigation, and content organization. Typically hosted on docs.* or help.* subdomain. Includes Getting Started, guides, tutorials, API Reference (endpoint docs), and troubleshooting. Distinct from API introduction page (api-page-generator).

Guides resources page and content hub structure for discovery and SEO.

Guides feedback and roadmap pages that collect user input and communicate product direction. Often integrates with Canny, FeatureBase, UserVoice, or similar. Supports product-led growth and community engagement.

Guides changelog and release notes pages. Typically at changelog.* subdomain or /changelog. Builds trust, reduces support, increases feature adoption.

Guides status page design for communicating service health, uptime, and incidents. Typically at status.* subdomain. Reduces support during outages, builds trust.

Guides alternatives and comparison content that target "X alternatives" and "X vs Y" search intent. Purpose: Intercept competitor brand traffic—organic (SEO) and paid (brand keyword ads). High-intent, bottom-of-funnel; users searching alternatives are ready to switch. Content format: Standalone page (/alternatives, /alternatives-to-notion) or blog article (/blog/notion-alternatives). Same structure; blog builds topical authority.

Guides glossary page structure, content, and internal linking for SEO.

Guides careers page content, structure, and employer branding for recruitment.