Polymorphic resource links on pathway nodes #311

New issue

Open

opened 2026-07-27 14:01:49 +00:00 by AI · 0 comments

AI commented

2026-07-27 14:01:49 +00:00

Collaborator

Context

Pathway nodes can already surface inductions (via checker config) and drawer keywords. #258 asks to also attach Events, Tools, Drawers, and FAQs. Doing each as a bespoke field/UI will thrash the schema and editor.

Inductions stay as completion checkers. This issue is about linked resources shown on the node — "here's what this step points at" — not "you must hold this induction".

Proposal

One generic attachment model for portal entities:

Field	Purpose
`achievement_id`	Pathway node
`resource_type`	`tool` \| `drawer` \| `faq` \| `event` \| `induction` (and later types without a migration)
`resource_id`	UUID of the target
`sort_order` / optional label	Display order / override title

Committee UI: one "Linked resources" picker that switches target search by type. Member graph/detail: unified list with type badge and deep link.

Migrate any induction "attachments" that are informational (not checkers) into this table if they exist separately; leave checker_config induction leaves alone.

Acceptance criteria

Pathway managers can attach/detach Tools, Drawers, FAQs, Events (and Inductions as resources) from a node without code changes per type beyond a type registry entry
Member-facing node detail lists linked resources with working links
Adding a new resource type is a small registry + search adapter, not a new column
#258 closed as done by this

Feeds homepage recommended next step (#314) once progress + pins (#313) exist
Complements, does not replace, induction completion checkers
Supersedes #258

## Context Pathway nodes can already surface inductions (via checker config) and drawer keywords. #258 asks to also attach Events, Tools, Drawers, and FAQs. Doing each as a bespoke field/UI will thrash the schema and editor. Inductions stay as *completion checkers*. This issue is about *linked resources* shown on the node — "here's what this step points at" — not "you must hold this induction". ## Proposal One generic attachment model for portal entities: | Field | Purpose | | --- | --- | | `achievement_id` | Pathway node | | `resource_type` | `tool` \| `drawer` \| `faq` \| `event` \| `induction` (and later types without a migration) | | `resource_id` | UUID of the target | | `sort_order` / optional label | Display order / override title | Committee UI: one "Linked resources" picker that switches target search by type. Member graph/detail: unified list with type badge and deep link. Migrate any induction "attachments" that are informational (not checkers) into this table if they exist separately; leave `checker_config` induction leaves alone. ## Acceptance criteria - [ ] Pathway managers can attach/detach Tools, Drawers, FAQs, Events (and Inductions as resources) from a node without code changes per type beyond a type registry entry - [ ] Member-facing node detail lists linked resources with working links - [ ] Adding a new resource type is a small registry + search adapter, not a new column - [ ] #258 closed as done by this ## Related - Feeds homepage recommended next step (#314) once progress + pins (#313) exist - Complements, does not replace, induction completion checkers - Supersedes #258

AI added this to the Project Pathways milestone

2026-07-27 14:01:49 +00:00

AI added the

enhancement

label

2026-07-27 14:01:49 +00:00

AI referenced this issue

2026-07-27 14:02:51 +00:00

AI referenced this issue

2026-07-27 14:02:58 +00:00

Attach more portal types to project nodes #258

AI referenced this issue