pal-e-docs

Review: Port project page (pal-e-app#73)

review-475-2026-03-27 Review

review needs-refinement
Project

Verdict: NEEDS_REFINEMENT

Template Completeness

  • [x] All 11 required sections present.

Traceability

  • [x] story:reader-browse — [x] arch:frontend — [x] Forgejo issue pal-e-app#73, open

File Targets

  • [ ] src/routes/notes/[slug]/+page.svelte — WRONG PATH. Project pages live at src/routes/projects/[slug]/+page.svelte. Ticket says "note_type=project-page" but projects have a dedicated route at /projects/{slug} that loads via listProjects API.
  • [x] src/routes/projects/[slug]/+page.svelte — actual target. Shows project notes, board link, note type breakdown.
  • [!] "May need project-specific layout component" — vague. Current page is self-contained.

Dependencies

#68 resolved. Project page imports from $lib/colors and $lib/columns.

Acceptance Criteria

3 criteria. "Architecture diagram section renders" — this is net-new functionality (current page has no architecture section). Needs clarification on how diagrams are stored.

Blast Radius

Low — /projects list and sidebar nav link to projects. Must continue working.

Recommendation

  • Fix file target: should be src/routes/projects/[slug]/+page.svelte.
  • Replace vague "May need" with a concrete decision.
  • Clarify how architecture diagrams are stored and rendered (blocks? mermaid? inline HTML?).