DekuWorks / DekuWorks/241RunnersAwareness
Create Profile Page Skeleton
- Dominant language
- HTML
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
## Overview
Create a profile page with account management and runners section for authenticated users.
## Acceptance Criteria
- [ ] /profile route with two sections:
- Account: name, email, role badge; Edit modal → PUT /api/v1/users/me
- My Runners: empty state text + "Create Runner" button
- [ ] Toasts: success and error; API errors shown plainly
- [ ] Profile renders from /api/v1/users/me; edits persist; user feedback is clear
## Test Notes
- Test profile page loads with user data
- Test account edit functionality
- Test error handling for API failures
- Test responsive design on mobile
## Implementation Notes
- Use existing API endpoints for user data
- Implement proper form validation
- Add loading states and error handling
- Ensure proper user feedback for all actions
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the existing frontend route structure and API client, then trace /api/v1/users/me and the PUT endpoint. Build and test the /profile page against the listed account, runner, loading, validation, toast, error, persistence, and responsive criteria; done means authenticated users can view and edit their profile and see the empty runners state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html, react
- Domain
- authentication, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100