Site Settings
Every repository has one settings screen for its published documents. Open the repository, then Publish Center → API & Documents → Setting.
The screen has a list on the left in four groups, and one panel per topic on the right. Each panel has its own Save button, which becomes active when you change something.

| Group | Panel | What you set |
|---|---|---|
| Appearance | General | Document name, API category, site description |
| Styling | Theme, brand colour, brand colour in dark mode, light or dark appearance | |
| Branding | Square logo, wide logo, logo in dark mode, logo link, favicon | |
| Typography | Heading font, body font | |
| Layout | Navbar | A button and up to six links |
| Footer | Text, links, social links | |
| Banner | One announcement line | |
| Content | Content | The Copy page menu and the last-updated date on pages |
| API reference | Three-panel or stacked layout; where the list of operations is shown | |
| Configuration | SEO | Search engine listing, social image, verification tags |
| Redirects | Old addresses and where they lead now | |
| Analytics | Your Google Analytics ID | |
| Domain | Custom domain | |
| Access | Readable by AI agents, Hide the APIGIT logo |
When a change takes effect
A saved change applies at once to every published version of the repository, including versions pinned to an older commit. Nothing is committed to the repository, and you do not need to publish again.
To look at a change before your readers do, use the Preview button at the top of the screen. It shows the branch chosen under Preview branch with the saved settings. After saving, use Refresh in the preview.
What apigit.json holds
The site settings are kept in this screen and nowhere else. They are not files in your repository, and they are the same for every published version.
The apigit.json file of the repository holds two things, which belong to the versions published from a commit that
contains it:
| Key | What it sets | Described in |
|---|---|---|
nav | The navigation: which pages are listed, in which order and groups | Navigation |
theme | Optional. The theme of that version, in place of the one chosen in the Styling panel | Themes |
Nothing else in apigit.json is read. A logo, footer, banner or any other site setting written there has no effect:
enter it in the screen.
Content and API reference
Copy page menu, in the Content panel: turns the Copy page button on published pages on or off. It is on by default.
Last-updated date, in the Content panel: shows “Last updated” with the date of the page’s last commit under a Markdown page. It is off by default.
Layout, in the API reference panel: an API reference shows descriptions and examples side by side (Three panels, the default) or one under the other (Stacked).
Operation menu, in the API reference panel: by default the operations of an OpenAPI document are listed in the site’s own sidebar, under the document’s entry (In the site sidebar). Choose Inside the API page to show the reference’s own menu and search box instead. See API references.
Source mode
Source mode, at the foot of the list, shows what the Branding, Navbar, Footer, Banner, Content, API reference, SEO and Redirects panels have saved, as one JSON object. You can edit and save it there, for example to copy the settings of one repository to another. A syntax error is reported before anything is sent, and an entry that breaks a rule is refused with a message naming it.
The theme, colours, fonts, appearance, document name, custom domain, analytics ID and the two Access switches are not
part of this object; set them in their panels. An uploaded image appears as a reference that starts with upload: and
belongs to the repository it was uploaded to, so it cannot be copied to another repository.
Plans
The settings on this page are available on every plan. A custom domain needs Team or Enterprise, and hiding the APIGit badge needs Enterprise; see What each plan includes.