Components
Project section navigation
Keep tasks, events, links, and files within one identifiable project context.
On this page
Purpose and usage
Keep tasks, events, links, and files within one identifiable project context.
Use for project resources; use the application shell for global destinations.
Anatomy
| Part | Contract |
|---|---|
| Trigger | Current section label and icon. |
| Menu | Tasks, Events, Links, Files. |
| Destination | Project-specific route with section context. |
Variants and configuration
| Configuration | Behavior |
|---|---|
| projectSlug | Identifies the current project. |
| section | tasks, events, links, or files. |
State coverage
| State | Implemented behavior |
|---|---|
| Selected section | Visible current label. |
| Open | Menu exposes alternatives. |
| Dismissed | Escape closes and returns focus to the trigger. |
Interaction and responsive behavior
- Keep the project title visible when navigating sections.
- Use route navigation rather than presenting links as preference toggles.
- The files section has its own route in the product.
Accessibility contract
- Trigger references the open menu ID and exposes expanded state.
- Links must remain keyboard reachable.
- Test destination headings and focus after navigation.
Known gaps and readiness
Route context and menu behavior are documented, but the capture harness does not run the production data loader for each destination.
Composition example
<ProjectSectionMenu projectSlug={project.slug}
section="tasks" />Source references
| File | Responsibility |
|---|---|
| app/components/project-section-menu.tsx | Section navigation |
| app/components/project-detail-content.tsx | Section content composition |
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