Patterns
Manage supporting project context
Keep tasks, events, links, and files organized around the same project outcome.
On this page
User goal
Keep tasks, events, links, and files organized around the same project outcome.
Workflow
| Step | Expected behavior |
|---|---|
| 1 | Open the project and retain its title, appearance, Space, and lifecycle state. |
| 2 | Use the section menu to choose Tasks, Events, Links, or Files. |
| 3 | Create or edit an event/link with its dedicated modal and fields. |
| 4 | Keep external URLs normalized before rendering a navigable resource. |
| 5 | Return to the same project context after closing the editor. |
Decision rules
- Milestones organize execution; links and files organize supporting material.
- A date/time resource event is different from a project block reserved in the daily agenda.
- Use the project palette consistently without substituting status meaning.
- Separate opening a resource from editing its metadata.
Edge cases and recovery
- Invalid/unsafe URLs must not become outbound links.
- Long resource titles, descriptions and filenames need overflow testing.
- File uploads involve reservation, transfer and completion stages; they are not simulated as successful transfers in this pilot.
- Archived Space/project interactions need explicit read-only/lifecycle rules.
Source references
| File | Responsibility |
|---|---|
| app/components/project-detail-content.tsx | Context and section composition |
| app/components/project-link-modal.tsx | URL validation |
| app/components/project-event-modal.tsx | Date/time resource editing |
| app/components/project-files-workspace.tsx | File boundary |
Examples from the app
Actual Radarist components with fictional data. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-07 · Revision 0103e2549959 · Documentation v0.1