# Docs Site for Your Replit App | Revdoku

> Push your Replit app to GitHub with a docs/ folder. Revdoku publishes the docs on each push, with Ask AI, an MCP server for AI agents and support tickets.

Works with Replit

A docs site
for your Replit app

Push the code of your Replit app to GitHub, with the docs in a docs folder. Revdoku publishes that folder on each push. People search the docs and use Ask AI, and AI agents read them through MCP.

Start Free →

Questions? Ask AI in our docs
No card required.

Publishes from GitHub on every push

Works with Mintlify repositories

API console from your OpenAPI file

MCP server and llms.txt for AI agents

Ask AI and support tickets

Analytics for people and AI agents

Push the docs from Replit to GitHub

In a Replit App, you push to GitHub yourself, from the Git pane or from the Shell. Each push to the branch that Revdoku reads publishes the docs.

In Replit:

In the Project Editor, select Tools , then Git under Setup .

If the app has no repository yet, select Initialize Git Repository . Then connect the repository to GitHub.

Add a docs/ folder with Markdown pages and a docs.json navigation file. Ask Replit Agent with the prompt in the next section.

In the Git pane, stage the docs files and commit them with a message.

Push the commit to GitHub.

In Revdoku:

Create a Revdoku account . In the setup steps, select Connect a GitHub repository .

Select Connect GitHub and give the Revdoku GitHub App access to the repository.

Select Existing GitHub repository . Then select the repository and the branch that you push to.

In Folder , type docs . Click Import and sync .

Click Publish . Each later push to the branch publishes the docs again.

If someone changes the docs on GitHub, select Pull in the Git pane before you edit them in Replit.

Replit can also work on a GitHub repository that you already have. Open Repositories in Replit and select Use in chat . When you ask for a draft pull request, Replit pushes a new branch and opens the request. While the docs site is live, Revdoku makes a 24-hour preview of that branch, and the merge publishes the docs.

Prompt for Replit Agent

Paste this prompt into Replit Agent. It asks for the docs pages and the navigation file, and it keeps the app code as it is.

Write the docs for this app in a docs/ folder.
Do not change the app code.
- docs/index.md: what the app does and how to start.
- One Markdown page for each main task, with 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 app has HTTP routes that other programs
call, describe them in docs/openapi.json.
- Use only facts from the code.

With openapi.json , the docs site gets one reference page for each tag and an API console at /api-reference/console/ .

Send the users of your app to the docs

Put a link to the docs site in the app, for example on the home page or in a Help menu. On the docs site, people search the pages and use Ask AI , which names the pages that it used.

For questions that the docs do not answer, add a mailto: link to the support address of the docs. Each email starts a ticket in Revdoku, and the built-in support agent drafts a reply from your docs. A person sends the reply. A reader can also leave a message on the docs site, which never shows the support address.

If the app calls the Revdoku API, save the key in Replit Secrets

Only an app that calls the Revdoku API needs a key, for example to show the state of the docs site. In Revdoku, a bucket holds the files, the site and the support tickets of one docs site. Replit encrypts each secret and gives it to your code as an environment variable.

In Revdoku, open Account → Access and select Create API key… .

Set Bucket access to Selected buckets only and select the bucket of your docs. Set Permission to Read only .

In the Project Editor, select Tools , then Secrets under Setup .

Select New Secret . Enter REVDOKU_API_KEY as the Key and paste the API key as the Value .

Select Add Secret .

Open Publishing and select Adjust settings . Make sure that Production app secrets has the key.

Static Deployments get no secrets, so use another deployment type for an app that calls Revdoku. Collaborators who join with Multiplayer can see the values of secrets. The Revdoku SDKs for Node.js and Python read REVDOKU_API_KEY from the environment by default.

Replit Git pane · Replit Secrets · Docs for AI agents · Support tickets · Revdoku API

---

[View the canonical page](https://revdoku.com/replit/) · [Browse llms.txt](https://revdoku.com/llms.txt)