App Shell And Branding¶

Use this guide when you need to change the visible shell identity of a Mozaiks app without changing framework-owned runtime code.

What Branding Owns¶

Branding is split across a few app-owned files:

• app/brand/theme_config.json for visual tokens and theme inputs
• app/brand/assets/ for logos and icons
• app/brand/fonts/ for local fonts
• app/config/shell.json for shell content and navigation chrome
• app/app.json for startup route and auth intent, not raw theme tokens

In this repo, the first-party Studio bundle follows the same contract under factory_app/app/.

What Branding Does Not Own¶

Do not put these concerns into branding files:

• workflow logic
• module business rules
• runtime host wiring
• admin shell ownership

Typical Changes¶

Common branding tasks include:

• updating logos and icons
• adjusting theme tokens
• changing header actions or footer links
• changing the startup route
• configuring auth-facing shell chrome

Read Next¶

• Platform Authoring
• App Manifest And Platform Targets
• Getting Started