Publish the docs
of your Bolt app

Bolt creates a commit for each change that does not break the project. It also pulls changes from GitHub every 30 seconds, so docs that you edit on GitHub come back into Bolt.

In Bolt:

1. In your project, click the GitHub icon in the top-right corner. Click Log in to GitHub and install the Bolt GitHub App.
2. Enter a name for the repository and click Create repository. Bolt starts a private repository on the main branch.
3. Add a docs/ folder with Markdown pages and a docs.json navigation file. Use the prompt in the next section.

In Revdoku:

1. Create a Revdoku account. In the setup steps, select Connect a GitHub repository.
2. Select Connect GitHub and give the Revdoku GitHub App access to the repository.
3. Select Existing GitHub repository. Then select the repository and the main branch.
4. In Folder, type docs. Click Import and sync.
5. Click Publish. Each later push to main publishes the docs again.

To start from a repository that you already have, click GitHub under the chatbox on the Bolt homepage. Then click Choose this repository. Only the project owner can connect a Bolt project to GitHub.

Bolt does not merge branches in the app, so merge them on GitHub. While the site is live, a push to another branch gets a 24-hour preview of the docs.

Paste this prompt into the Bolt chat. Bolt commits the new files to GitHub, and Revdoku publishes them.

Add user docs to this project in a docs/ folder.
Keep the app code as it is.
- docs/index.md: what the app does and how to start.
- One Markdown page for each task in the app, with
  numbered steps. Each page starts with front matter:
  title and description.
- docs/docs.json in the Mintlify format, with
  "navigation" groups that list every page once.
- If the project has server functions that other
  programs call, describe them in docs/openapi.json.
- Write only what the code does.

Revdoku publishes only the folder that you select, so the code of the app stays out of the docs site. With an OpenAPI file, the site also gets an API console, where people send real requests.

Ask Bolt to add two links to the app, for example in the footer or in a Help menu:

• The address of the docs site. Readers search the pages there and use Ask AI.
• A mailto: link to the support address of the docs.

Each email to the support address becomes a ticket. The built-in support agent drafts a reply from your docs, and a person reviews and sends it. The site itself never shows the support address. A reader who still needs help leaves a message there, and the message arrives as a ticket.

The docs site needs no key. A key is necessary only if the app reads Revdoku data, for example the number of open support tickets on an admin page. In Revdoku, a bucket holds the files, the site and the support tickets of one docs site.

1. In Revdoku, open Account → Access and select Create API key….
2. Set Bucket access to Selected buckets only and select the bucket of your docs. Set Permission to Read only.
3. In Bolt, click the database icon in the top menu, then Secrets.
4. In Name, enter REVDOKU_API_KEY. Paste the key in Value and click Save.

Secrets work only with server functions, and server functions need a project database. Do not put the key in .env, because code in the browser can read values from that file. Only the project owner, co-owners and team admins can open the secrets.

Bolt GitHub guide · Bolt secrets guide · Docs for AI agents · Support tickets · Revdoku API