返回提示词目录第 1294 页

网站建设需求文档编写

整理网站目标、页面结构、功能与交接验收要求,并标出无障碍及隐私义务待确认项。

完整提示词

<context>
Website projects go wrong in predictable places: the brief says "modern, clean, mobile friendly" and every agency quotes a different project; content is assumed to be the agency's job while the client assumes the opposite, and launch slips by months waiting for text and photos; nobody planned redirects from old pages, so search traffic falls after launch; the site is built on a platform the staff cannot update; the domain, hosting and analytics accounts end up in the agency's name; accessibility is never mentioned, then a customer complains; forms send personal data somewhere nobody chose; and "done" was never defined. A good requirements document states goals and audiences, a sitemap with page purposes, who supplies content, who edits what afterwards and how often, integrations, hosting and maintenance expectations, accessibility and SEO requirements including redirects, privacy needs such as cookie consent, ownership of every account and asset, and acceptance criteria.
</context>

<task>
<project>
{{project}}
</project>
{{#details}}
<details>
{{details}}
</details>
{{/details}}

1. State goals and audience: the business goals the site serves with a measurable signal for each, the main audiences and the top tasks each comes to do.
2. Draft a sitemap: pages and sections with purpose and the key content or action on each, marking pages that need templates (blog posts, products, team members, locations).
3. Specify content and CMS: who writes and supplies text, images and video, whether migration of existing content is included, who updates which parts after launch and how often, editor roles, and preview and approval needs.
4. Specify functionality and integrations: forms and where submissions go, booking, shop or payments, newsletter, CRM, maps, search, multilingual content, and anything requiring accounts.
5. Specify technical and hosting needs: platform preference or constraints, hosting, backups, security updates, performance targets, browser and device support, and the maintenance or support arrangement after launch.
6. Specify accessibility, SEO and privacy: an accessibility target (for example WCAG 2.2 AA) to confirm, redirects from old URLs, page titles and metadata, analytics, cookie consent and privacy policy needs depending on countries, and form data handling.
7. Specify ownership and handover: domain, hosting, CMS, analytics and third-party accounts registered to the client, licences for fonts, images and themes, source code or theme ownership, documentation and training.
8. Specify acceptance and timeline: acceptance criteria and test checklist, review rounds, milestones, and what proposals must state (assumptions, exclusions, ongoing costs).
9. List open questions for the client to answer before sending the brief.
</task>

<constraints>
- Do not recommend a specific agency, product or price; describe needs and leave platform choice open unless the user has a constraint.
- Do not state legal requirements as facts; flag accessibility and privacy obligations as items to confirm for the countries involved.
- Make content responsibility explicit; never leave it implied.
- If the purpose of the site or the audience is unclear, ask before writing.
</constraints>

<output_format>
## Goals and audience
Table: goal, signal of success. Then audiences with top tasks.
## Sitemap
Table: page, purpose, key content or action, template (yes/no).
## Content and CMS
Bullets.
## Functionality and integrations
Table: function, details, connects to.
## Technical and hosting
Bullets.
## Accessibility, SEO and privacy
Bullets.
## Ownership and handover
Checklist.
## Acceptance and timeline
Checklist, then milestones.
## Open questions
Numbered list.
</output_format>

可替换内容

  • {{project}}
  • {{#details}}
  • {{details}}
  • {{/details}}

分类与标签

编程开发、网站需求、站点结构、开发验收、内容管理、交接维护

前往 AI 图片创作