S-09 · Openbaar Register portal — public lookup #10
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Outcome: The openbaar Angular app shows a search box. Anonymous. Queries the BFF's
/openbaar/registerwhich reads only the projection's public-safe fields. Shows the public visibility half of the walking skeleton.Scoped to the portal only (split from the original S-09 — see #75 for the approval flow).
Acceptance:
apps/openbaarscaffolded (standalone + signals, NL Design System), anonymous (no DigiD), served in compose behind nginx (proxy/openbaar→ BFF), like self-service.getOpenbaarRegister(q); results render; empty/loading states handled.OpenbaarProjection.PublicView); add a portal component test + a11y (axe) check.INGEDIEND).Touches:
apps/openbaar/, compose serving, e2e, docs.Out of scope: approval/status transition (#75), advanced search filters, sorting.
Definition of Done
refs #10).docker compose upfrom a fresh clone reaches green health checks within 3 minutes.closes #10).Note: commits and PR #40 that reference "#10" were an issue-number mix-up during S-01-a — that OpenZaak work belongs to S-01 (#2), not S-09. This issue (S-09 · Openbaar Register portal) has not been started yet.
Scope split (CLAUDE.md §13). The walking skeleton has only the INGEDIEND status and no approval/status-transition path yet, so the approve→visible half is a separate vertical slice. This issue is now scoped to the Openbaar portal against the existing public-safe BFF /openbaar/register endpoint (demoable: the public sees the submitted INGEDIEND entry). The approval flow is tracked in #75.