Workshop Notes
Feature Detail
Description
Workshop Notes provides coordinators with a dedicated note editor scoped to a specific career workshop session. Unlike the general Notes area, these notes are attached to the workshop record and are not surfaced elsewhere in the app. The editor supports free-text multi-line input and auto-saves drafts locally to prevent data loss during a session. Multiple notes can be created per workshop, each attributed to its author with a timestamp, giving the coordinator a running log across the two days of a session.
Sources & reasoning
Section 3.1 explicitly names "eget notatverktøy" (own note tool) as one of three distinct capabilities within karriereverksted. The qualifier "eget" (own/dedicated) signals it is separate from the general Notes area. Target release v1.1 is inherited from the Phase 3 placement of the karriereverksted parent in section 5.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Without a structured note tool tied to a specific workshop, coordinators capture session observations in personal notebooks or generic phone apps that cannot be searched, shared, or referenced later within the platform. Workshop Notes closes this gap by persisting notes directly against the session record, making them available to the coordinator during future sessions or handovers. For Blindeforbundet the notes also serve an administrative function: they document what was covered and what follow-up was required, which supports internal quality assurance and can be referenced if Bufdir queries the content or scope of a mentoring event.
Workshop notes are stored in a workshop_notes table (workshop_id, author_id, content, created_at, updated_at). The Note Editor Screen reuses the text-input infrastructure from the Notes area but scopes its Riverpod provider to workshop_id rather than contact_id. Auto-save debounces on 1.5 s of inactivity, writing to Drift locally before the mutation outbox syncs to the server. The editor is pushed as a named route from the workshop detail screen. Content must scale to 200 % without horizontal scrolling per WCAG 2.2 AA, and the save-state indicator must be accessible to screen readers.
Components (46)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.