[Epic] Career data domain (Profile, Skills, Experience, Projects) #4

Closed
opened 2026-06-12 20:26:37 +00:00 by james · 0 comments
Owner

The user's career data: who they are and what they've done. By the end of this epic:

  • Profile, Skills, Education, Jobs (with positions and contributions), Contracts, and Projects all have full CRUD UIs and API routes backed by the DB abstraction.
  • Every entity is scoped to its owning user via a user_id FK; users only see and modify their own data.

Linked tickets

  • Profile
  • Skills
  • Education
  • Jobs with positions and contributions
  • Contracts
  • Projects

Exit criteria

  • A user can fully populate their profile, skills, education, jobs, contracts, and projects from the PWA, and the data round-trips correctly on both SQLite and Postgres.
  • A second user signing in on the same instance does not see any of the first user's data, and vice versa.
The user's career data: who they are and what they've done. By the end of this epic: - Profile, Skills, Education, Jobs (with positions and contributions), Contracts, and Projects all have full CRUD UIs and API routes backed by the DB abstraction. - **Every entity is scoped to its owning user via a `user_id` FK; users only see and modify their own data.** ## Linked tickets - Profile - Skills - Education - Jobs with positions and contributions - Contracts - Projects ## Exit criteria - A user can fully populate their profile, skills, education, jobs, contracts, and projects from the PWA, and the data round-trips correctly on both SQLite and Postgres. - **A second user signing in on the same instance does not see any of the first user's data, and vice versa.**
james closed this issue 2026-06-24 02:31:05 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
james/carol#4
No description provided.