atomic-design-poc/docs/project/readable-codebase/RD-36-overzicht-secties.md

RD-36 — ui/dashboard/ becomes ui/overzicht-secties/

Status: done Phase: 5 — fix the docs that describe this flow

Why

RD-03 moved the dashboard page to overzicht/ui/overzicht.page.ts and left four data sections in registratie/ui/dashboard/. The folder is now named after a page that lives somewhere else. A reader who opens registratie/ui/dashboard/ finds four sections that are not the dashboard, and the page it is named for is in another context.

RD-04 recorded the name as stale and left it. This ticket fixes it.

Read first

• docs/project/readable-codebase/PLAN.md:267-282 — the decision and its measured cost.
• apps/ssp/src/app/overzicht/ui/overzicht.page.ts — the only importer.

Decisions (pre-made, do not relitigate)

1. The new name is overzicht-secties/. It says what the four files are: registratie's sections for the overzicht page. It keeps the Dutch that CLAUDE.md requires of a domain context.
2. Flattening into registratie/ui/ is rejected. That directory holds one folder per component. Eight loose files would break its shape.
3. The alias does not change. The four sections stay in the registratie context, so the imports stay @registratie/ui/…. Only the folder segment changes.
4. Story titles do not change. They are Domein/Registratie/<Name>, which is a context name, not a folder name. Both Storybook globs are recursive, so no config changes.
5. Fold in the two stale dashboard.page paths named in PLAN. docs/reference/feature-flags.md:55 and .claude/skills/new-ssp/SKILL.md:65 both cite registratie/ui/dashboard.page, a file that no longer exists. The flag logic they describe lives in apps/ssp/src/app/overzicht/ui/wat-wilt-u-doen.section.ts now.
6. Fix the other live citations of the deleted file too. Same defect, same commit: docs/reference/architecture/ARCHITECTURE.md:55 (the pages node in the Mermaid diagram) and :79 (the ui/ row of the layer table), and libs/shared/docs/remote-data.mdx:64. Each names dashboard.page.ts as a live example. The current name is overzicht.page.ts.
7. Leave docs/project/archive/ and the shipped RD ticket records alone. They describe the tree as it was when they ran. A historical record that cites a path from its own time is correct, not stale.

Files

The move — 8 files, git mv the directory:

apps/ssp/src/app/registratie/ui/dashboard/ → apps/ssp/src/app/registratie/ui/overzicht-secties/

mijn-aanvragen.section.ts        mijn-aanvragen.section.stories.ts
mijn-registratie.section.ts      mijn-registratie.section.stories.ts
specialismen.section.ts          specialismen.section.stories.ts
wat-moet-ik-regelen.section.ts   wat-moet-ik-regelen.section.stories.ts

The importer — one file, four import lines plus one comment:

• apps/ssp/src/app/overzicht/ui/overzicht.page.ts:3-6, and the comment at line 12 that says "four sections stay in registratie/ui/dashboard/".

RD-31 added two more. Its rewrite of ARCHITECTURE.md §6a links the read walkthrough to registratie/ui/dashboard/mijn-registratie.section.ts and registratie/ui/dashboard/wat-moet-ik-regelen.section.ts by full path. Both move here. Fix them, or §6a's links break the day this ticket lands.

The five doc citations: docs/reference/feature-flags.md:55, .claude/skills/new-ssp/SKILL.md:65, docs/reference/architecture/ARCHITECTURE.md:55 and :79, libs/shared/docs/remote-data.mdx:64.

Steps

1. git mv the directory.
2. Fix the four imports and the comment in overzicht.page.ts.
3. Fix the five doc citations per decisions 5 and 6.
4. npm run ci --full.

Acceptance criteria

• apps/ssp/src/app/registratie/ui/dashboard/ no longer exists.
• grep -rn "ui/dashboard" apps libs docs/reference libs/shared/docs .claude returns nothing outside the .xlf extraction metadata named in Out of scope.
• No live document cites dashboard.page. Historical records under docs/project/archive/ and the shipped RD-*.md files are exempt.
• git diff --stat -M shows renames plus small edits, no rewritten files.
• npm run ci --full is green.

Verification

1. npm run ci --full. The four story files move, and only build-storybook proves that both Storybook globs still pick them up.
2. npm run storybook — the four Domein/Registratie/… stories are still in the sidebar under the same titles.
3. npm start, open http://localhost:4200/dashboard. All six sections render.

Out of scope

• The <context context-type="sourcefile"> metadata in apps/*/src/locale/messages*.xlf. It still names src/app/registratie/ui/dashboard.page.ts, which RD-03 renamed. That metadata comes from ng extract-i18n and no build reads it, so it is stale extraction output from before RD-03, not a citation this ticket created. Regenerating it is its own job.
• Renaming the /dashboard route to /overzicht. PLAN.md puts it under "Deliberately out of scope": it needs a redirect and it is user-visible.
• Moving the four sections into the overzicht context. They read BigProfileStore and belong to registratie; overzicht composes them. That is RD-03's decision and it stands.

Risks

1. A missed specifier fails the typecheck, not the build. Run npm run ci --full, which typechecks all four tsconfigs.
2. git mv of a directory, then edits, can look like deletes and adds. Commit the rename and the edits together and check git diff --stat -M before you push.
3. The route stays /dashboard. Do not "tidy" it while renaming the folder. The folder name and the URL are separate decisions, and only one of them is in this ticket.