54 Commits

Include renames

Author	SHA1	Message	Date
Bendik Aagaard LynghaugandClaude Sonnet 5	755b796ad1	Resource-backed multi/single-select requirement ... Requirement gains an optional `resource` (reuses ResourceSpec/ ResourceSource/jq wholesale - a resource is a resource whether it's displayed read-only or offered as choices to pick from) and `id_field` (which field in each item is its stable id, defaults to _id then id). `type: select` + `multiple` (already-existing field, previously file -only) picks single vs multi. New get_requirement_options server fn shares its auth/fetch/jq logic with get_resource via two extracted helpers rather than duplicating it. Submitted value is the selected id (single) or a JSON array of ids (multi) - a new select_field_map (RwSignal<Vec<String>>, alongside the existing field_map/file_refs maps, since a multi-select's value is a set, not a string) threaded through the same nested <For> structure the other requirement kinds already use. Content validation extended: a `type: select` requirement declaring no resource now fails at load time instead of rendering a dead field. Caught a real bug in my own first version of that check while testing it - it was nested inside a feature-level resource guard, so it never ran unless the *feature* also happened to have its own resource. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-06 11:57:15 +02:00
Bendik Aagaard LynghaugandClaude Sonnet 5	bd702bfbae	Render generic resource lists as cards, not raw JSON dump ... A jq-shaped resource (e.g. the GiteaStarred showcase) previously fell through to the raw <pre> JSON dump - same fallback path meant for truly unstructured data. Added a card renderer for the common case (array of plain objects): name/title as a linked heading, description as body text, everything else as small key/value chips - same visual language as AnswerRow's answer-fields, just for non-Answer data. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-06 11:31:42 +02:00
Bendik Aagaard Lynghaug	00d2a95625	Fix hero-canvas navigation race; style the prosekit editor and add a toolbar ... - Hero: gate RasterizedYES construction on a NodeRef resolving, not just "the Effect ran". Root cause of the reported "loading..." stall + "RefCell already borrowed" panic - navigating back to / client-side could run the Effect before the new <canvas> was actually in the DOM, yes.js did an unchecked getElementById(...).getContext() on null and threw mid-reactive-update, corrupting wasm_bindgen_futures' executor badly enough to panic on the next tick. Same NodeRef-gating pattern the prosekit editor's own mount already used. - style/main.css: .prosekit-wrap/.prosekit-toolbar/.prosekit-editor to match the existing input/textarea look (border, background, focus ring). - prosekit-editor.js: a real toolbar (Bold, Italic, H1, H2, Link, and a dedicated Gitea-repo-embed button reusing the paste rule's own insert logic) with active-state highlighting via the standard ProseMirror markActive/nodeActive idiom.	2026-08-05 14:52:08 +02:00
Bendik Aagaard Lynghaug	aa1a7fa572	Initial commit: content-driven onboarding portal ... Leptos/Axum app that renders a Question/Alternative/Feature schema loaded from a sibling content repo (portal-content). Kanidm OIDC login, content-driven authorization (Question.qualifies), a generic NATS KV-backed resource + state-transition mechanism (no bespoke "applicant" concept baked into the runtime - it's all content), a SHA-256 DAG chain tying submissions and decisions together, and the "YES - Rasterized Lines" piece (ported from the live uhhm.no site) as the landing hero.	2026-07-29 19:38:40 +02:00