21 lines
1.4 KiB
Markdown
21 lines
1.4 KiB
Markdown
Functional Requirements (FR)
|
|
|
|
- FR1: Global design tokens for color, typography, spacing, and motion are defined and consumed across components.
|
|
- FR2: Select and apply one headline/display font and one body font globally; remove conflicting fonts.
|
|
- FR3: Sidebar navigation (persistent, collapsible) reflects target IA groups: Projects, Process, Studio, Contact.
|
|
- FR4: Command palette (Cmd/Ctrl+K) for quick navigation and actions.
|
|
- FR5: Projects section includes Reel, Case Studies index with filters, and Case Study detail pages.
|
|
- FR6: Process section includes Pipeline, Tools, and Infrastructure subpages.
|
|
- FR7: Studio section includes About, Team, Values pages.
|
|
- FR8: Contact page implements smart intake form (project type, timeline, budget range, refs) with clear confirmation and next steps.
|
|
- FR9: Sticky Split component pattern implemented and reusable across Home/Projects/Process/Studio.
|
|
- FR10: Accessibility supports reduced motion, keyboard navigation, and visible focus management.
|
|
|
|
Compatibility Requirements (CR)
|
|
|
|
- CR1: Preserve existing public routes behavior and SEO where applicable (redirects if slugs change).
|
|
- CR2: Maintain database schema and NextAuth integration; no breaking changes to auth flows.
|
|
- CR3: UI/UX consistency with new tokens without breaking existing admin functions.
|
|
- CR4: Integration compatibility with current API routes (/api/*) and Prisma models.
|
|
|