2 min readAn original planning guide. Use the linked primary documentation for platform details and the supported procedure for your environment.
Name the audience and task
Describe who the site serves, what visitors need to do, and what information helps them decide. Keep assumptions separate from established facts.
Define content and functions
List required pages, forms, accounts, integrations, and content sources. Identify who supplies and approves each part.
Record constraints
Include brand assets, accessibility needs, maintenance capacity, platform requirements, and any launch dependencies. Avoid assuming a feature is included because it appears in a mockup.
Write acceptance criteria
Turn each important task into an observable check and assign review ownership. Use the brief to resolve scope questions during implementation.
Worked scenario
See the plan in practice.
A service business needs qualified contact requests, not just an attractive homepage. The brief describes required form fields, routing, and confirmation behavior.
Review your result
Your acceptance checklist
Audience named- Scope explicit
- Acceptance defined
Use these checks to identify gaps in your website project brief. Assign an owner to any unresolved item before the next dependent step.
The terms behind the task
- Content management systemSoftware for organizing, editing, and publishing content through an application interface.
- Website navigationThe controls and links that help people understand a site's organization and move between content or tasks.
- AccessibilityThe practice of making products usable by people with a broad range of abilities and assistive technologies.
Primary references
For the underlying concepts and current platform details:
