What is Fiskil Docs?

Fiskil Docs is a documentation engine and hosting platform. You own two things — a content/ folder of MDX pages and a docs.json configuration file — and the engine owns everything else: rendering, navigation, search, theming, API reference generation, localization, SEO, and deployment.

How it fits together

Your docs site is a real repository you can run locally:

my-docs/
├── docs.json          ← one config file: brand, products, locales, APIs
├── content/docs/      ← your pages, in MDX
└── public/            ← images, favicons, OpenAPI specs

The fiskil CLI develops, validates, and builds the site. Publishing is one command — or entirely automatic, if you connect a GitHub repository: push markdown to main and your docs are live; open a pull request and you get a preview link in the PR.

What the engine gives you

• Navigation from your folder structure. Products, sections, and sidebars come from how you organize files — plus a small meta.json where you want explicit control. There is no navigation config to maintain by hand.
• API references from OpenAPI. Point docs.json at your specs — local files or URLs — and get categorized sidebars, versioned references, an interactive playground, and hand-written pages side by side with generated ones.
• A theme that rebrands from one file. Colors, logo, and favicon are configuration and convention — no CSS required, though your own components are welcome.
• AI-ready output. Every page serves raw markdown at .md, and the site publishes llms.txt and llms-full.txt automatically.

Where to go next