iGrant.io use-case UI (default look and feel)

When to use

The default chrome for any iGrant.io frontend (igrantio-issuer-frontend, igrantio-verifier-frontend, or a bespoke use-case UI). Reach for it whenever the user has not specified their own UI or layout. It gives you the iGrant.io navbar, footer, theme, and a small set of primitives so a flow looks on-brand with zero design work. If the user brings their own design system, skip this.

Intentionally minimal: a theme, a shell, a few primitives, strings-driven i18n. No component-library sprawl, and no runtime deps beyond what igrantio-frontend-client already uses (React peer plus qrcode).

Before you build: run the integrator intake in igrantio-ows-overview - environment, API key, tenancy, backend host, webhooks, frontend - one question at a time, a recommended default with each.