Repository navigation
Add the Verktøykasse (VK-01–VK-08, TO-07) - #68
Merged
Merged
Conversation
The toolbox filters by tool type and by team type at once, so `chips` is now a list of rows. Each row has a key, and items carry their values for it in `data-filter-<key>`. An item shows when it matches the chosen chip in every row. Roller and Teamoversikt move to the new format with one row each, keyed `type`; they behave as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A library of recommended methods, templates, guides and tools that everyone signed in can browse, and that teams register their tools from. - The collection `verktoy` (VK-01–VK-03, VK-05, VK-07, VK-08): - name; - Verktøytype, a fixed list (Mal, Metode, Veileder, Verktøy); - Beskrivelse; - the team types the tool suits; - a link to the tool where Digdir has a licence; - resources. Administrators maintain it. Links must be absolute http(s) links. - Teams get «Verktøy teamet bruker» (VK-06). The teameier and teamleder edit it like the rest of the team. - `/verktoy/verktoykasse` lists the tools as linked cards, with search and chips for tool type and team type (VK-04, VK-05). `/verktoy/verktoykasse/[id]` shows a tool, its team types, «Åpne verktøyet» and its resources. - The team page shows the tools the team uses (TO-07). - Seed data: the 14 tools from the prototype. Three teams use some of them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ugedal1
marked this pull request as draft
November 18, 2026 13:00
«Åpne verktøyet» takes the visitor away from ilag, so it is a link, like the resources under it and the tool links in the prototype. Designsystemet keeps buttons for actions on the page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Resolves the conflict with the admin panel's collection groups (#74): - Verktøy goes in the «Team» group, after the team type wizard, in the order main sets. - The generated types are regenerated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The header stays on the page, and «Passer for» and «Ressurser» each get a neutral card below it. The team types under «Passer for» are light blue (info), like team types everywhere else. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
All of a tool's links are now in one card. The tool itself comes first, as «Åpne <tool>», and the guidance about it follows. «Ingen ressurser er lenket opp ennå.» shows only when the tool has no links at all. The CMS keeps the two as separate fields: only the tool link is for tools Digdir has a licence for. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The tool itself and the guidance about it are different things, so the tool's link moves out of «Ressurser» into a small card above it. Only tools with a link get the card. «Ressurser» has only the guidance links again, with its own empty text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the Verktøykasse: a library of recommended methods, templates, guides and tools that everyone signed in can browse. Teams register the tools they use from it.
Requirements: VK-01, VK-02, VK-03, VK-04, VK-05, VK-06, VK-07, VK-08, TO-07
CMS
New collection,
verktoy(Tools.ts). Each tool has:Everyone signed in reads the tools, and only administrators edit them. Team editors don't see the collection in the menu, but can still pick tools on their team. In the admin panel, each tool lists the teams that use it.
Links are checked (utils/links.ts). A link without
https://, such aswww.figma.com, would otherwise become a broken relative link on our own site, so it's refused with «Lenken må starte med https://».javascript:and similar links are refused too.Teams get «Verktøy teamet bruker» (VK-06). The teameier and teamleder edit it through the access they already have on the team (TO-08).
Seed data: the 14 tools from the prototype's
TOOLS. Real links are added only where the prototype names a real site. Three teams use some of the tools.Frontend
/verktoy/verktoykasse(VK-01–VK-05): the tools as linked cards, like the team cards, each with its type, name and description./verktoy/verktoykasse/[id]: the type, the description, «Passer for», «Åpne verktøyet» when the tool has a link (VK-08), and «Ressurser» (VK-07), with breadcrumbs from the layout.ListFiltertakes several rows of chips (its own commit).chipsis a list of rows, each with akey, and items carrydata-filter-<key>. Roller and Teamoversikt move to the new format with one row each and behave as before.joins: { teams: false }; that list is for the admin panel. The SDK dropsjoins: false, so turning off just that join is the way to do it.Tests
ListFilterwith two rows.Tried in the running app as
teamleder@example.com: the list, tool pages, the team page, and the REST join turned off.Notes
toolstable and ateams_relstable for the team's tools. In development,pnpm db:seed:resetfills them.LinkCardcomponent for the linked cards (team, tool, sub-unit, wizard answers), in its own refactor PR after this one is merged.🤖 Generated with Claude Code