marketing-pages

Name: marketing-pages
Availability: InStock
Author: Resend

Create marketing pages using PublicPage structure and website primitives.

39|3|Updated Jan 29, 2026

Search Tags:#marketing #design-system #marketing-pages #public-page #website-primitives

Ready to run

npx skills add https://github.com/resend/design-skills --skill marketing-pages

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: marketing-pages
Source: https://github.com/resend/design-skills/tree/main/marketing-pages
Command: npx skills add https://github.com/resend/design-skills --skill marketing-pages

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Marketing pages in the Resend codebase often lack a unified structure, leading to inconsistent layouts and copy across pages. This skill provides a standardized framework for creating, updating, and deleting marketing/public pages using shared design system rules and public primitives.

Core Features & Use Cases

Enforces a single marketing-page structure that aligns with PublicPage components and website primitives.
Guides reuse of public primitives and components to avoid duplication and ensure consistent UX.
Use Case: Create a new marketing page under src/app/(website)/your-page with PublicPage.Root, Header, Hero, Container, and Footer, sourcing content from src/components/website/ and src/components/public-page.tsx.

Quick Start

Create or update marketing pages using the standard PublicPage structure and reusable primitives.

Frequently Asked Questions about marketing-pages

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

FAQPage Schema

How do I standardize marketing page layouts and prevent inconsistent designs?▼

Standardizing marketing page layouts requires a centralized structure using reusable public primitives like PublicPage.Root, Header, Hero, Container, and Footer to enforce consistent UX and avoid duplication across pages.

What is the correct directory structure for publishing public website pages?▼

The correct directory structure places marketing pages under src/app/(website)/your-page, with corresponding content and components sourced from src/components/website/ and src/components/public-page.tsx.

How do I separate website public primitives from product UI components?▼

Separating website public primitives from product UI components requires enforcing distinct directory paths, routing public pages through src/app/(website)/ while isolating shared layouts in src/components/public-page.tsx.

Can I compose a new marketing page using reusable website primitives?▼

Yes, composing a new marketing page uses reusable website primitives by applying a standard PublicPage structure that references shared layout and metadata components to ensure consistent design system rules.

What are the limitations of using a centralized structure for public pages?▼

A limitation of using a centralized structure for public pages is the strict separation between website primitives and product UI, requiring all marketing pages to conform to the src/app/(website)/ routing and component sourcing rules.

How do I handle SEO metadata when creating a new marketing page?▼

Handling SEO metadata when creating a marketing page is guided by the centralized framework, which provides a reference for page layout and metadata alongside the standard public page components to ensure correct configuration.