template
Landing-page project brief
Define the landing page's owner, visitor, job, public source material, boundaries, and observable finish line.
Complete this before asking an agent to design or build.
Outcome
- Site owner:
- Primary visitor:
- One job the page must do:
- Primary call to action:
- Definition of done:
Scope
- Pages required:
- Sections required:
- Languages required:
- Forms or external links required:
- Explicit non-goals:
Source material
| Item | File or URL | May be published? | Owner confirmed? | Gap or conflict |
|---|---|---|---|---|
| Identity | ||||
| Offer | ||||
| Audience | ||||
| Proof | ||||
| Contact details | ||||
| Images |
Use [TBD — name the missing input] instead of inventing copy.
Constraints
- Repository visibility:
- Required launch date:
- Accessibility needs:
- Browser or device priorities:
- Brand rules:
- Content or claims that must not appear:
Human approval
- ☐ The owner approves the audience, claim set, and call to action.
- ☐ Every publishable asset has a known source and permission.
- ☐ Private source material is excluded from the public repository.
- ☐ The definition of done can be checked in a browser.