01
Front Page
Daily start page for continue, look back, capture, learn, and prepare.
Reference desk / Product PRD
Personal career newsroom.
Leadjr is the living documentation system for a professional story. It captures field material, identifies story arcs, reflects the record back to the user, and prepares them to share or speak about their work when it matters.
Product PRD
The preferred product model, IA, and operating principles for Leadjr.
About Me / Profile
The living public read of the user: career overview, selected features, experience, CV, and contact.
Design System
The visual and component rules that keep the career newsroom consistent while the product evolves.
Product model
The site is organized by intent.
The new IA moves away from database labels and toward newsroom actions. These names are the preferred product direction; old routes can evolve toward them over time.
02
Field Notes
Capture desk for journal entries, transcripts, audits, screenshots, documents, and testimonials.
03
Features
Story arcs that can become case studies, interview answers, profile modules, and portfolio sets.
04
The Mirror
Record Book first, then Growth Outlook: highlights, invisible work, competency map, and growth opportunities.
05
Profile
The canonical external microsite: an editorial career profile built from approved story modules.
06
Press Kit
What the user sends: profile link, resume, cover letter, LinkedIn copy, case studies, and review packets.
07
Prep Desk
How the user prepares to say it: conversation type, season, story order, rehearsal, and follow-up.
08
Archive
Quiet library/admin space for artifacts, people, projects, metrics, skills, and canonical corrections.
Operating principles
- 01Lead with story, not verification.
- 02Evidence is the method, not the headline promise.
- 03Clarify early, then correct once and reuse everywhere.
- 04No interface is complete until its data behavior is explicit.
- 05The Mirror reminds before it evaluates.
- 06Press Kit is what you send; Prep Desk is how you prepare to say it.
- 07Learning feeds the Front Page; growth belongs in The Mirror.
Functionality contract
No page ships on appearance alone.
Every surface must declare whether it is a reader, editor, triage queue, capture surface, or generated output. Editable-looking controls must save, survive refresh, and expose an error state. Read-only surfaces must avoid fake edit affordances.
Reader
Displays record material without edit affordances.
Editor
Changes canonical data, persists it, and survives refresh.
Triage queue
Collects a verdict and records that verdict to the right store.
Capture surface
Creates new record material with a clear source and destination.
Generated output
Transforms approved source material into an audience-ready artifact.
Definition of done
- What does this page read?
- What does this page write?
- Where is the change persisted?
- What happens on failed save?
- How do we prove it survived refresh?
- Which controls are intentionally read-only?