Skip to main content
docs/public contains the authored Mintlify site. docs/public/docs.json owns navigation, colors, and assets. The canonical plugin contracts remain under source/.

​
Preview locally

Use Node.js 20.17.0 or later for the Mintlify CLI. This site uses CLI version 4.2.879 for local evidence. From the repository root, run:
Open the local URL that the command reports. Examine the Guide, Reference, and Maintainers tabs. Make sure that each page supports its stated reader action.

​
Examine a change

From docs/public, run:
Strict validation rejects warnings and errors. The Mintlify CLI reference defines these commands. A successful build does not prove the page’s source claims or reader understanding. Assess each changed prose artifact with the writing procedure. Keep the report and input hashes outside the public site. If a term changes, examine docs/glossary.json and its generated reader view. Do not invent a synonym to remove a finding.

​
Connect Mintlify

A separate Slopsentral deployment keeps this site’s source and identity explicit. The first deployment targets the documentation branch during PR review. Its public URL is slopsentral.michne.com. After the documentation PR merges, set the deploy branch to main. The Mintlify GitHub app must include amichne/slopsentral in its selected repositories. In Git Settings, set the documentation subdirectory to /docs/public. Do not include a trailing slash. The Mintlify monorepo guide describes this setup. The quickstart describes site creation.

​
Use Mintlify MCP

List the deployments that the connection permits. Select Slopsentral’s subdomain and inspect its Git source before edits. Use a checkout branch for a reviewable change. Examine the diff before the save operation. The current MCP tools manage existing deployments. Site creation needs the Mintlify dashboard. The deployment URL comes from that dashboard after setup. Do not claim a live site from a local preview alone.