Configure the generated application's appearance in Project settings → Branding. No custom CSS or generated-file edits are needed for the supported settings. Branding changes your application, not the generator's own interface, permissions, data languages or fonts.
Start with the draft
- Open the project and Project settings → Branding.
- Keep Enable Branding enabled. Decide whether visitors need Enable secondary theme.
- Configure Content, then the independent Login block. Choose colors with the circular picker inside each input or enter
#RRGGBB; clear a color to use its default. - Check the light and dark previews beside each block. On narrow screens they move below the settings; the previews are static illustrations of the unsaved draft, without application data or custom code.
- Click Save project settings, inspect Generate → Preview changes, then Generate and rebuild the application through its normal release process. Importing an image or changing preview does not perform these steps.
Use Reset to discard the settings draft. Leaving with unsaved changes asks you how to proceed. Appearance-only settings do not require a database migration or deploy the application automatically.
Content titles, company and home
| Setting | Behavior |
|---|---|
| Application title | Visible application title; empty falls back to Project title in General. |
| Short title | Compact title where applicable. |
| Company name | Optional centered caption below Log out, also used on Login. |
| Welcome title / Welcome text | Text on the ordinary generated home; not a replacement for Demo or your own dashboard content. |
| Support label / Support URL | Optional shared support link using HTTPS or mailto. |
An explicit Application title replaces the Administration caption above the centered Content logo; it is not duplicated below. Without it, the standard caption and Short title/Project title fallback remain. Branding does not rename the technical Project name, Go module or tables. The toolbar offers Change password when permitted; account roles and Demo restrictions remain unchanged.
For a custom React home, use General → Custom dashboard and the preserved extension described in custom admin.
Independent Content and Login colors
Both blocks have visible Primary (Light) and Secondary (Dark) groups:
| Block | Available colors |
|---|---|
| Content | Accent, Background, Surface, Text, Menu |
| Login | Accent, Background, Surface, Text |
Content Background is the page canvas; Surface is cards, forms, tables and inputs. Menu has its own background with readable navigation text, selection and hover states. Login has its own page background, form surface, accent and normal text including the heading. Empty Login colors use fixed light/dark defaults and never inherit Content colors.
Text, links and focus tones are adjusted against their actual surfaces. A requested text color may become lighter or darker to remain readable; a heading on the page canvas need not have the same tone as a field on a card. Semantic error, warning and success colors remain separate. The project palette does not change the generator's fixed palette.
Login identity and images
Login has its own Application title. Empty hides the application-name line; it does not use Content Application title, Short title or Project title. Login title is the form heading and defaults to Sign in; Login description adds supporting text.
Upload Login image · Light and optionally Login image · Dark. Dark falls back to the light Login image when not set. Without a Login image, the fixed lock icon is shown. Content logos are never used on Login, and there is no icon selector. Identity, heading, description and company/support are centered; credential inputs retain their normal alignment.
Logos, favicon and source files
Content uses Logo · Light, optional Logo · Dark with light fallback, and Favicon. Logos and Login images accept PNG/JPEG/WebP up to 2 MiB; Favicon accepts PNG up to 256 KiB. The uploader validates file contents and dimensions. SVG/HTML, arbitrary local paths and remote image URLs are not supported.
Use the tile's upload, replace or remove action; actions are available by hover, keyboard focus and on touch devices. Remove clears the draft reference rather than deleting the stored source file.
Source assets live in .admingen/branding/ and references are saved with the model. Include both in version control. Generate copies referenced assets to admin/public/branding/; this output remains generator-owned. Branding files are separate from record Image/File storage and require no database upload migration.
Disable and restore appearance safely
Enable secondary theme off forces Light even for a dark OS or previously saved Dark preference, and hides the appearance switch on Content and Login. Its colors and the previous preference are retained for re-enabling.
Enable Branding off hides its settings/previews while preserving all values, files and secondary-theme choice. After Save and Generate, the application uses stock titles, colors and normal light/dark availability without authored logos, support or welcome overrides. Turn it back on to reconnect the saved configuration. Existing projects without either flag keep the enabled behavior.
What to check after generation
Check the actual application in its enabled themes: navigation, sign-in, a long form, read-only details, Content language and keyboard focus. Preview does not execute custom screens or prove API authorization. Saving a layout in Admin editor, configuring access in Content, generating code and publishing a release remain separate actions.