Settings
A tour of docs.json, the one file that configures your site
docs.json is the single source of truth for how your site looks and what it
contains. This page covers the essentials; theme, localization, SEO, and API
settings each have their own page.
Site identity
{
"name": "Acme",
"description": "Everything you need to build on Acme.",
"logo": {
"light": "/logo/light.svg",
"dark": "/logo/dark.svg"
}
}nameis your site's title — used in the header, browser tab, and social cards.descriptionis the default meta description.logoreplaces the text name in the header. Give alightvariant, and optionally adarkone; paths are underpublic/.
Favicons are picked up by convention — drop a favicon.ico, favicon.svg,
icon.png, or apple-touch-icon.png into public/ and it's used automatically.
Products
Products are the top-level areas readers switch between. Each id maps to a
content/docs/{id}/ folder:
"products": [
{ "id": "platform", "label": "Platform" },
{ "id": "mobile", "label": "Mobile SDK" }
]The schema
Every field is defined by a JSON schema, so a good editor gives you
autocomplete and inline docs. Point docs.json at it and regenerate it any time
with the CLI:
{ "$schema": "./docs.config.schema.json" }npx fiskil schemaValidation
The build refuses to run on an invalid docs.json, so a typo never reaches
readers. Check it any time:
npx fiskil validateNext: theme
Colors, light and dark mode, accents.