Pics Portal — Docs

Specs, analyses, and plans for growing the Pics Portal from a read-only Pics browser into a feature-complete client portal: subjects management, exports, print layouts, and customer-facing access.

Where to start

1. Read the vision for the 4-phase roadmap.
2. Read the Phase 1 PRD for the next concrete deliverable.
3. Skim the four analysis docs if you want the source-of-truth context the vision and PRD lean on.

Roadmap

Phase	Scope	Status
1 — Subjects + Exports core	Subject CRUD, find duplicates, subject directory, 25 standard SIS exports, async export jobs, download history.	draft
2 — Print layouts (render-only)	Pre-authored layout selection, 4-step print wizard, async PDF render with progress UI, recent prints.	planned
3 — Custom exports + layout authoring	Custom export format editor; canvas-based layout template editor with image slots + field-binding placeholders.	planned
4 — Customer portal + RBAC + Files	Studio / Client / User / Role permission model, customer auth, customer-facing routes, file requests & uploads.	planned

Documents

Vision

Doc	Status	Date
Vision: Pics Portal	draft	2026-05-18

Analysis

Doc	Status	Date
Current pics-portal scaffold	analysis	2026-05-18
Geskus reference repos	analysis	2026-05-18
PlicGo / Captura School Portal feature inventory	analysis	2026-05-18
Pics API gap	analysis	2026-05-18

PRDs

Doc	Status	Date
Phase 1 — Subjects + Exports core	draft	2026-05-18
Phase 2 — Print layouts (render-only)	planned	—
Phase 3 — Custom exports + layout authoring	planned	—
Phase 4 — Customer portal + RBAC + Files	planned	—

ADRs (Architectural Decision Records)

Doc	Status	Triggers
Subject store — portal Postgres, Pics expansion, or hybrid	open	Phase 1 implementation
Async job substrate	open	Phase 1 implementation
Image / S3 strategy	open	Phase 2 — render
Layout render engine	open	Phase 2
Layout authoring approach	open	Phase 3
Customer auth strategy	open	Phase 4

Implementation plans

Doc	Status	Date
Phase 1 impl plan	planned	after ADR pack

What's next

1. Review the vision and Phase 1 PRD. Send edits or approve.
2. On approval, draft the ADR pack (subject store, async job substrate, possibly image strategy).
3. Then the Phase 1 implementation plan.
4. Then Linear epic + tickets.

Reference materials

• Sample rendered layout PDF (PlicGo / Strawbridge): sample-render.pdf
• Pics integration contract: portrait-pics/portal-integration.md
• Geskus reference repos: geskus-client-portal, pics-client-portal