Skip to content

fix(web-ui): lowercase the omadia brand name in user-facing text#359

Merged
Weegy merged 1 commit into
mainfrom
fix/omadia-lowercase-branding
Jun 22, 2026
Merged

fix(web-ui): lowercase the omadia brand name in user-facing text#359
Weegy merged 1 commit into
mainfrom
fix/omadia-lowercase-branding

Conversation

@Weegy

@Weegy Weegy commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

What

The brand name is always written omadia (all lowercase). Several
user-facing surfaces in the web-ui still rendered the capitalized
"Omadia". This PR lowercases every one of them.

Changed (web-ui, 16 files)

  • Page <title> metadata — admin, system, routines (+ run detail), agents, channels, store, builder (+ workspace).
  • Wordmarks — the sidebar logo (layout.tsx) and the login header (login/page.tsx).
  • Footers / hero — store footer, builder footer, store hero headline, plugin-detail footer.
  • i18n stringsmessages/de.json + messages/en.json (logo aria-label, meta title/description, login title, setup welcome).
  • ProseREADME.md, Dockerfile header comment, one source comment.

Deliberately NOT changed

camelCase code identifiers are part of the API/data contract and must
stay as-is: actorOmadiaUserId, involvedOmadiaUserIds, and the
OmadiaBridge TypeScript type in the desktop app.

Desktop app

Already lowercase everywhere user-facing (productName: omadia, tray,
window titles, onboarding wizard HTML, updater dialogs). The only
capitalized occurrence is the OmadiaBridge type name — code, left
untouched. So no functional desktop changes were needed.

Verification

  • tsc --noEmit clean (node 22.22.3).
  • de.json / en.json parse as valid JSON.
  • grep confirms the only remaining "Omadia" tokens are the camelCase identifiers above.
  • No test asserts on the changed brand strings.

The brand is always written 'omadia' (lowercase). Several UI surfaces
still rendered 'Omadia': page <title> metadata, the sidebar and login
wordmarks, the store/builder footers, and the de/en i18n strings.
Lowercase them all (plus the README/Dockerfile/comment prose).

camelCase code identifiers (actorOmadiaUserId, involvedOmadiaUserIds,
OmadiaBridge) are deliberately left untouched.

The desktop app already uses lowercase 'omadia' everywhere user-facing
(only the OmadiaBridge type name remains, which is code).
@Weegy Weegy merged commit dfcbefb into main Jun 22, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant