aa489c7eb8
Add detailed landing page development plan in docs/frontend_landing_plan.md: - Complete landing page structure (Hero, Problem/Solution, Features, Demo, CTA) - Design guidelines from downloaded skills (typography, color, motion, composition) - Security considerations (XSS prevention, input sanitization, CSP) - Performance targets (LCP <2.5s, bundle <150KB, Lighthouse >90) - Responsiveness and accessibility requirements (WCAG 2.1 AA) - Success KPIs and monitoring setup - 3-week development timeline with daily tasks - Definition of Done checklist Download 10+ frontend/UI/UX skills via universal-skills-manager: - frontend-ui-ux: UI/UX design without mockups - frontend-design-guidelines: Production-grade interface guidelines - frontend-developer: React best practices (40+ rules) - frontend-engineer: Next.js 14 App Router patterns - ui-ux-master: Comprehensive design systems and accessibility - ui-ux-systems-designer: Information architecture and interaction - ui-ux-design-user-experience: Platform-specific guidelines - Plus additional reference materials and validation scripts Configure universal-skills MCP with SkillsMP API key for curated skill access. Safety first: All skills validated before installation, no project code modified. Refs: Universal Skills Manager (github:jacob-bd/universal-skills-manager) Next: Begin Sprint 3 landing page development
68 lines
1.8 KiB
Markdown
68 lines
1.8 KiB
Markdown
|
|
### Site Mapping
|
|
|
|
**Creating Site Maps:**
|
|
- Inventory existing content
|
|
- Group related content logically
|
|
- Define hierarchy and relationships
|
|
- Visualize structure
|
|
|
|
**Types:**
|
|
- **Hierarchical**: Tree structure with clear parent-child relationships
|
|
- **Sequential**: Linear flow (checkout processes)
|
|
- **Matrix**: Multiple categorization paths
|
|
- **Database**: Dynamic content organization
|
|
|
|
### Navigation Design
|
|
|
|
**Navigation Types:**
|
|
- **Primary**: Main navigation (header, sidebar)
|
|
- **Secondary**: Sub-navigation within sections
|
|
- **Utility**: Account, search, cart
|
|
- **Contextual**: Related content, breadcrumbs
|
|
|
|
**Best Practices:**
|
|
- Limit top-level items to 7±2
|
|
- Use descriptive, action-oriented labels
|
|
- Indicate current location
|
|
- Ensure consistent placement
|
|
|
|
### Content Organization
|
|
|
|
**Organizing Principles:**
|
|
- **Alphabetical**: A-Z ordering (directories, glossaries)
|
|
- **Chronological**: Time-based (blogs, news)
|
|
- **Categorical**: Topic-based grouping
|
|
- **Task-Based**: Organized by user goals
|
|
- **Audience-Based**: Different paths for user types
|
|
|
|
**Content Hierarchy:**
|
|
- Primary content (most important, prominent placement)
|
|
- Secondary content (supporting information)
|
|
- Tertiary content (supplementary, less visible)
|
|
|
|
### Card Sorting
|
|
|
|
**Types:**
|
|
- **Open**: Users create and name categories
|
|
- **Closed**: Users sort into predefined categories
|
|
- **Hybrid**: Combination of both approaches
|
|
|
|
**Process:**
|
|
1. Prepare content cards (30-60 items)
|
|
2. Recruit participants (15-30)
|
|
3. Conduct sessions (in-person or online)
|
|
4. Analyze patterns and clusters
|
|
5. Validate with reverse card sorting
|
|
|
|
### Taxonomy and Labeling
|
|
|
|
**Best Practices:**
|
|
- Use user language, not internal jargon
|
|
- Be consistent in terminology
|
|
- Test labels with real users
|
|
- Keep labels concise but descriptive
|
|
- Avoid ambiguous terms
|
|
|
|
---
|