TEDY.15 — Landing

State: Built — the app’s default home dashboard. Template: tool-feature. Prefix: TEDY.

Overview

The Landing page is TEDY’s home dashboard, shown at the app root (/ and /landing). A faithful port of the reference editor’s landing page: per-resource count cards grouped into Resources · Modeling · Management, each card linking to the resource’s list. Every card is gated by the resource’s read privilege, and a group renders only when it has at least one visible card.

Cards

• Resources — Code Systems (*.CodeSystem.read) · Value Sets (*.ValueSet.read) · Map Sets (*.MapSet.read).
• Modeling — Structure Definitions (*.StructureDefinition.read) · Structure Maps (*.StructureMap.read) · Implementation Guides (*.ImplementationGuide.read).
• Management — Servers (*.Server.read) · Spaces (*.Space.read) · Ecosystems (*.Ecosystem.read) · Releases (*.Release.read).

Each count is meta.total from the resource’s list search issued with limit: 0 (via the existing useCodeSystems / useValueSets / useMapSets / useStructureDefinitions / useStructureMaps / useImplementationGuides / useServers / useSpaceList / useEcosystems / useReleases hooks). Clicking a card navigates to that list.

Screen

pages/Landing.tsx — a title (Terminology editor) + the three grouped card grids. No new data layer (reuses the list hooks).

Routes & nav

/ and /landing both render Landing (root previously redirected to /code-systems). Nav: General → Home (tedyMenu.ts), beside Global search.

i18n

tedy.landing.* (title, home, resources, modeling, management).

Notes / limits

The reference landing also shows Wiki page metrics and created-by-me / assigned-to-me task lists. TEDY has no Wiki module, and the task search (GET /tm/tasks) is modelled only with context/statuses (no per-user params), so those sections are out of scope; a task-summary section can follow once task management lands.