Text and formatting

A screen reads as part of the app only when its words, dates and links behave like everyone else's. Modules ship their strings in Danish and English, and dates and money follow the visitor's locale. This page gives the rules for strings and values, and ends with a checklist that sums up all four UX pattern pages.

Text

• Translated strings. Every string goes through useModuleT('<namespace>') with an English fallback. The module ships da and en JSON files. See Module Kit i18n.
• Shared strings. Open, Edit, Delete and "Not set" come from the patterns.* keys of UI, and an app can override them.
• Button labels. Buttons and menu items name the object: "Add unit", "Delete application", "Revoke token". Never a bare "Add", "Delete" or "Save", unless the button sits in a section that is clearly about one thing.
• Dates and money. Format them with useFormat(), so they follow the active locale. Do not call toLocaleString or Intl directly.
• Links. Build them with useLocaleLink().localize, so a visitor on /da/... stays in their locale.

In a table, dates come from useFormat() and statuses are status badges (StatusBadge):

Checklist for a new page

1. Pick the area: admin, account or public. Register the route, and add one item to the matching menu. See Layouts and navigation.
2. Use the heading for the area. App pages use PageHeading, and every app page renders its own: account pages through AccountHeader. Public pages use UPageHeader.
3. Build lists from TableCard and UTable, with a RowMenu and a UEmpty. Build detail pages from SectionCards, with a breadcrumb. See Pages.
4. Send writes through a use<Entity>Actions() composable and a FormSlideover. Destructive writes confirm. See Forms and actions.
5. Send strings through useModuleT, with da and en JSON. Buttons name the object.
6. Check the page in light and dark mode, at desktop width and at 375px.

Where things live

Next steps

• Add an admin page – run through the checklist on a real page.
• UI – override the shared patterns.* strings in your app.
• UI composables – look up useFormat and useLocaleLink.