General
Community name, links, branding, theme, navigation and languages.
Almost everything a fan sees before they do anything is on this screen. Which accounts a fan can sign in with and link is Sign-in.
Basics
| Field | What it does |
|---|---|
| Name | The community name in the header, in the browser tab and in the link preview when someone shares your app. |
| Description | The one line under the name, and the text in that same link preview. Write it for someone who has never heard of the app. |
Important links
The links fans see in your app: Website, X, Discord, YouTube, Twitch, Instagram and TikTok. Fill in the ones you actually run and leave the rest empty. An empty field hides the icon rather than showing a dead one.
These are display links. Announcing quests to Discord is Automations, and a Discord role check on a quest needs the Discord integration.
Visual customisation
| Setting | What it does | What goes wrong |
|---|---|---|
| Accent colour | The single brand colour carried through the app: buttons, progress bars, active states, highlights. | A pale accent on a dark background makes buttons look disabled. Check a button, not a swatch. |
| Logo | 240x240 recommended, 5 MB max. Sits in the header and on the sign-in screen. | Anything with padding baked in looks small next to other apps. Crop tight. |
| Cover image | 1920x1080 recommended, 5 MB max. The banner at the top of the app. | Detail near the centre gets cropped on a phone. Keep faces and text away from the edges. |
| Page backgrounds | A separate background per section: quests, events, store, leaderboard, newsfeed, battlepass, profile, settings. | Busy artwork behind a quest board makes the card text unreadable. Test with the board full, not empty. |
| Fonts | A primary typeface and an alternate for headings. | A font with no bold weight flattens every heading in the app. |
| Corner radius | Base, large, compact or none, applied to every card and button. | |
| Spacing scale | Base, large or compact. Compact fits more on screen, large reads more calmly on a phone. |
Changes save immediately and appear on the next page load for fans. There is no publish step here, so make branding changes when nobody is mid quest.
Theme
| Option | What fans get |
|---|---|
| Dark | The default, and what most communities ship. |
| Light | Light only. |
| Both | A toggle in the app, remembered per fan. |
Pick one and stay there unless you have a reason. Both doubles what you have to check. Every quest image, every background, every logo and every custom colour has to work on two grounds. If your brand is built on a dark palette, ship dark.
Navigation
The order and the labels of the sections in your nav bar.
- Reorder the sections so the one you care about most is first. Most communities lead with quests.
- Rename a section, so Store can read as Shop.
- Hide a section you do not use. Hiding it removes it from the nav rather than deleting the content behind it.
- Add a custom link out to your main site, your ticket shop or your Discord. It sits alongside the built-in sections.
A nav bar with nine entries reads as a settings menu. Six is plenty on a phone.
Feature labels
Rename a whole feature across the app rather than only in the nav. Quests become Missions, events become Tournaments, the store becomes the Shop.
You choose the singular and the plural, and the label is applied everywhere the word appears: page titles, empty states, buttons, notifications. Tell your FanBase contact the words you want and we apply them.
Rename before launch. Changing the word after fans have learned it costs you more than the better word gains you.
Languages
English, French, Portuguese, Italian and Indonesian. Tell us which ones you want and we enable them on your community.
Enabling a language does not translate your content. Quest titles, descriptions and event copy are written per language in the admin panel, and a quest missing a translation falls back to your default language rather than disappearing. If you offer French, budget for someone writing every quest twice.