Skip to content

feat(profile): structured sections for skills, experience, projects, and education #3

@leobrqz

Description

@leobrqz

Summary

Extend the Profile page with additional structured sections below the existing preset/custom profile entries. Each section supports multiple user-defined entries with typed subfields, editing, reordering, and copy-friendly presentation for reuse in applications.

The current profile models short key-value style data well but not CV-style blocks (employment history, education, grouped skills). Job seekers need reusable, structured narratives that stay editable and easy to copy into external forms.

Proposed behavior

  • New sections (e.g. Experience, Education, Projects, Skills) appear as distinct cards or regions under the current profile content.
  • Experience-style entries support fields such as job title, company, date range, seniority, compensation (optional), summary, and a list of bullet points (each bullet is its own editable line).
  • Skills support user-named subgroups (e.g. “Backend”) with free text or tag-like content under each group; groups and items are add/remove/rename capable.
  • Education and projects follow the same pattern: defined subfields per entry, lists where needed, optional descriptions.
  • All blocks are editable in place, reorderable within their section, and presented in a layout that is easy to scan and to copy (e.g. plain-text or structured export later can build on this).

Scope notes

  • First version prioritizes data model clarity and UX for add/edit/reorder/copy; deep formatting (rich text, PDF export) can follow.
  • Sections should not duplicate the entire resume file concept; they complement resumes as structured data the app can reuse elsewhere later.

Success criteria

  • User can maintain at least one full employment history entry and one skills grouping without leaving the profile area.
  • Bullets and subsections behave as independent editable units.
  • Empty sections degrade gracefully (hide or show helpful empty state).

Metadata

Metadata

Assignees

Labels

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions