Rename feature branch from 002-at-the-moment to 002-product-list

Changed branch name and updated all references:
- Git branch: 002-at-the-moment → 002-product-list
- Specs directory: specs/002-at-the-moment/ → specs/002-product-list/
- spec.md: Updated feature branch reference
- requirements.md: Updated feature references

Reason: More descriptive name that better reflects the feature purpose
(product selection landing page).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
2025-10-17 14:01:10 +02:00
co-authored by Claude
parent 0dc9e6a0b5
commit fb418bac65
2 changed files with 3 additions and 3 deletions
@@ -0,0 +1,104 @@
# Requirements Checklist: Product Selection Landing Page
**Feature**: 002-product-list
**Created**: 2025-10-17
**Status**: Draft
## Functional Requirements
### Core Landing Page Functionality
- [ ] **FR-001**: System MUST display a landing page at the root URL (`/`) showing all active products available for feedback submission
- [ ] **FR-002**: System MUST retrieve product list from the file-based storage (`data/products/*/config.yaml`)
- [ ] **FR-003**: System MUST filter products to show ONLY those with `status: active` in their config.yaml
- [ ] **FR-004**: System MUST display for each product: product name (`name` field from config.yaml)
- [ ] **FR-005**: System MUST provide a clickable link/button for each product that navigates to `/submit/{submission_url_slug}`
### Data Handling & Edge Cases
- [ ] **FR-006**: System MUST handle products without descriptions gracefully (show name only or placeholder)
- [ ] **FR-007**: System MUST maintain existing direct URL functionality (`/submit/{product-slug}` continues to work)
- [ ] **FR-009**: System MUST sort products in a consistent, predictable order (alphabetical by name recommended)
- [ ] **FR-010**: System MUST handle the case where no active products exist (display appropriate message)
### Security & Technical Constraints
- [ ] **FR-008**: Landing page MUST be accessible to anonymous users (no authentication required)
- [ ] **FR-011**: Product listing MUST be server-side rendered (consistent with project's no-JavaScript requirement)
- [ ] **FR-012**: System MUST escape all product names and descriptions to prevent XSS attacks
- [ ] **FR-013**: Landing page MUST use the same minimal HTML/CSS styling as the rest of the application (no frameworks)
- [ ] **FR-014**: System MUST log when the landing page is accessed (for monitoring/analytics)
## User Stories
### P1: Browse and Select Product
- [ ] Visitor can view landing page at root URL
- [ ] All active products are displayed with names
- [ ] Product descriptions are shown (if available)
- [ ] Clicking a product navigates to its submission form
- [ ] Products are visually distinguishable
### P2: Product Availability Status
- [ ] Only active products appear in the list
- [ ] Archived products do not appear (or clearly marked)
- [ ] Visitor can trust listed products accept feedback
### P3: Direct Navigation Compatibility
- [ ] Direct URLs to `/submit/{product-slug}` still work
- [ ] Visitors can quickly identify known products
- [ ] Large product lists remain navigable
## Success Criteria
### Performance & Usability
- [ ] **SC-001**: Visitors can access submission form in ≤2 clicks from landing page
- [ ] **SC-002**: Landing page loads in <1 second for up to 100 products
- [ ] **SC-003**: Active products appear on landing page within 5 seconds of status change
- [ ] **SC-008**: Users can distinguish between 5+ products visually
### Reliability & Security
- [ ] **SC-004**: Zero direct URL submissions broken (backwards compatibility)
- [ ] **SC-005**: Appropriate message shown when no active products exist
- [ ] **SC-006**: Product names/descriptions properly escaped (no XSS)
- [ ] **SC-007**: Landing page renders without JavaScript
## Edge Cases Coverage
- [ ] No active products scenario handled
- [ ] All products archived scenario handled
- [ ] Products without descriptions handled
- [ ] Authenticated user accessing landing page handled
- [ ] Long product names handled (truncation/wrapping)
- [ ] Special characters in product names handled (escaping)
- [ ] Multiple similar product names handled (differentiation)
- [ ] Missing/invalid submission_url_slug handled
## Testing Requirements
### Contract Tests Required
- [ ] GET `/` returns 200 with HTML product list
- [ ] Products filtered by status=active only
- [ ] Product links navigate to correct submission forms
- [ ] No active products shows appropriate message
- [ ] XSS prevention (product names with HTML/script tags)
### Integration Tests Required
- [ ] Complete user journey: landing page → product selection → submission form
- [ ] Backwards compatibility: direct submission URLs work
- [ ] Product list updates when product status changes
- [ ] Authenticated vs anonymous access behavior
### Performance Tests Required
- [ ] Landing page load time with 100 products <1s
- [ ] Product listing rendering performance
## Definition of Done
- [ ] All functional requirements implemented and tested
- [ ] All user stories have passing acceptance tests
- [ ] All success criteria validated
- [ ] All edge cases handled with appropriate error messages
- [ ] Contract tests written and passing
- [ ] Integration tests written and passing
- [ ] Performance tests written and passing
- [ ] Code follows project conventions (Python, Flask, no JS)
- [ ] Security requirements met (XSS prevention, access control)
- [ ] Documentation updated (if needed)
- [ ] Feature committed to branch 002-product-list