Skip to main content
The root admin object in frogbot.config.ts configures the admin panel as a whole. Collection-level admin settings, such as useAsTitle, group, and views, live on each collection; see Admin Options.

Admin options

Import map options

Page metadata

admin.meta sets the document head for admin routes. Beyond the two FrogBot options, it accepts the Metadata type from next, so apps that install next get its full autocomplete. FrogBot fills in a title suffix, Open Graph site name and description, a FrogBot favicon, and a FrogBot Open Graph image until you set your own.

FrogBot metadata options

Next.js metadata options

Every other key comes from the next Metadata type and is passed through to the page head. FrogBot computes metadataBase from serverURL, so a configured value has no effect. Custom root views can override page metadata with their own meta key; see Adding New Views.

Home-screen icons

When someone adds an app to an iPhone or Android home screen, FrogBot supplies the icon and a web app manifest. With no setup, every app shows the FrogBot frog. To use your own, put a square PNG of at least 512 px in public/ and name it in appIcon:
FrogBot serves every size from that one file, with no sign-in needed:
  • /api/frogbot/app-icon/{32,180,192,512}: the tab icon, the iOS touch icon (on white) and the two manifest icons.
  • /api/frogbot/app-manifest: the manifest, named after applicationName (else FrogBot) and opening the admin panel.
Every admin page links to them unless you set icons or manifest yourself.