CFP+ Website Requirements Specification v1.0
<callout icon=\"i\" color=\"yellow_bg\">
\tDocument type: Verification Framework.
\tAudience: Notion AI, Team Website, Team AI, Team Translation, Team Content.
\tThis document converts Mission principles into verifiable requirements.
</callout>
0) Scope
Applies to the official CFP+ website built on Notion.
1) Governance Format (Approved)
Every requirement must use the following fixed block format:
•Requirement ID
•Type (Must / Should / May)
•Statement (one sentence, one idea)
•Rationale (why; link to Mission principle)
•Source Reference (which approved source / registry / baseline it relies on)
•Acceptance Criteria (checklist; verifiable)
•Evidence / Proof (what to show; link/record)
•Owner
•Status
<callout icon=\"✅\" color=\"green_bg\">
\tEvidence proves it was done.
\tSource Reference proves which approved source it was based on.
</callout>
2) Requirement Domains (Locked prefixes)
Requirements must be registered under these domains:
•WEB-REQ-FUNC — Functional Requirements
•WEB-REQ-CONT — Content Requirements
•WEB-REQ-ARCH — Architecture Requirements
•WEB-REQ-AI — AI Readiness Requirements
•WEB-REQ-GOV — Governance Requirements
3) Status Model (Default)
Draft
↓
In Review
↓
Verified
↓
Published
Additional audit states (only when needed):
•Non-conformant
•Waived
4) Non-duplication Rule
Requirements must not restate Mission sentences.
Example:
•Mission: “Website dễ điều hướng.”
•Requirement (verifiable): “User can reach every primary navigation category within defined navigation depth.”
WEB-REQ-FUNC — Functional Requirements
WEB-REQ-FUNC-001
•Type: Must
•Statement: The website must include the full frozen navigation registry.
•Rationale: Mission Baseline → Navigation (Initial set)
•Source Reference: CFP+ Website Design Mission — Baseline v1.0 (Navigation Registry v1.0)
•Acceptance Criteria:
\t- [ ] All navigation items exist as pages or stubs.
\t- [ ] Navigation labels match the frozen registry (no renaming).
•Evidence / Proof:
\t- [ ] Published Home page URL
\t- [ ] Navigation screenshot or page links list
•Owner: Team Website
•Status: Draft
WEB-REQ-FUNC-002
•Type: Must
•Statement: A user must reach every primary navigation category from Home within a defined maximum click depth.
•Rationale: Mission Baseline → “Dễ điều hướng”
•Source Reference: Website Requirements Specification v1.0 (this requirement)
•Acceptance Criteria:
\t- [ ] Max click depth is defined (X).
\t- [ ] All primary navigation categories are reachable within X clicks.
•Evidence / Proof:
\t- [ ] Click-path test record (list of paths)
•Owner: Team Website
•Status: Draft
WEB-REQ-CONT — Content Requirements
WEB-REQ-CONT-001
•Type: Must
•Statement: Public content must originate from approved CFP+ source records.
•Rationale: Mission Baseline → Content Governance / One Source Of Truth
•Source Reference: CFP+ Content Registry (approved source records)
•Acceptance Criteria:
\t- [ ] Each public page includes an approved source reference (ID or link).
\t- [ ] No independent duplicate version exists for the same content.
•Evidence / Proof:
\t- [ ] Published page URL
\t- [ ] Registry record ID / link
•Owner: Team Content
•Status: Draft
WEB-REQ-CONT-002
•Type: Should
•Statement: Each page should include a “Future Content Placeholder” section to support incremental expansion.
•Rationale: Mission Baseline → Content Strategy
•Source Reference: CFP+ Website Design Mission — Baseline v1.0 (Standard Page Structure)
•Acceptance Criteria:
\t- [ ] Placeholder exists on primary pages.
•Evidence / Proof:
\t- [ ] Sample page URLs (≥ 5)
•Owner: Team Website
•Status: Draft
WEB-REQ-ARCH — Architecture Requirements
WEB-REQ-ARCH-001
•Type: Must
•Statement: The website must implement one architecture for multiple languages (no separate websites per language).
•Rationale: Mission Baseline → “One Website. Multiple Languages. One Source Of Truth.”
•Source Reference: CFP+ Website Design Mission — Baseline v1.0 (Website Language Strategy)
•Acceptance Criteria:
\t- [ ] A single IA is shared across languages.
\t- [ ] Language variants do not create independent navigation systems.
•Evidence / Proof:
\t- [ ] IA map showing language variants
•Owner: Team Translation
•Status: Draft
WEB-REQ-ARCH-002
•Type: Must
•Statement: The website must scale to thousands of articles without restructuring the baseline architecture.
•Rationale: Mission Baseline → Scalability Principle / Evolution without reconstruction
•Source Reference: CFP+ Website Design Mission — Baseline v1.0 (Scalability Principle)
•Acceptance Criteria:
\t- [ ] Adding 100 new pages does not require renaming top-level sections.
\t- [ ] Cross-links remain stable after expansion.
•Evidence / Proof:
\t- [ ] Expansion test record (page list + link checks)
•Owner: Team Website
•Status: Draft
WEB-REQ-AI — AI Readiness Requirements
WEB-REQ-AI-001
•Type: Must
•Statement: Pages must use a consistent heading structure so content is extractable by AI.
•Rationale: Mission Baseline → AI Ready / Voice First
•Source Reference: CFP+ Website Design Mission — Baseline v1.0 (Voice First Standard)
•Acceptance Criteria:
\t- [ ] H2/H3 headings are used consistently.
\t- [ ] No critical information is embedded only in images.
•Evidence / Proof:
\t- [ ] Sample page URLs (≥ 10)
•Owner: Team AI
•Status: Draft
WEB-REQ-GOV — Governance Requirements
WEB-REQ-GOV-001
•Type: Must
•Statement: Any change to frozen mission/navigation/language baselines must be handled as a controlled change and reviewed before implementation.
•Rationale: Mission Baseline → Baseline Rule / Change control line
•Source Reference: CFP+ Website Design Mission — Baseline v1.0 (Baseline Rule)
•Acceptance Criteria:
\t- [ ] A review record exists for each baseline change request.
\t- [ ] Implementation references the approved review outcome.
•Evidence / Proof:
\t- [ ] Review record URL(s)
\t- [ ] Change log entry
•Owner: Team Governance
•Status: Draft