Skip to main content
The public site presents current guides, reference material, and linked OKF explanations. Mintlify reads docs/public from main in amichne/slopsentral. The repository keeps that deployable input under the same source review and CI gates as its canonical documents.

Keep one source for each explanation

site.json maps canonical documents to public routes. It also owns the Mintlify configuration, navigation, and redirects. The site keeps the original Mint theme, colors, and logo assets. Current prose stays in its mapped source file. Generated copies under docs/public are consumers, rather than another prose owner. The projection keeps the canonical body and changes repository links into public routes or GitHub source links. Public pages receive Mintlify frontmatter instead of native producer metadata. OpenWiki keeps its Claims, sidecars, indexes, and native lifecycle. A public copy cannot replace that evidence or establish a new native review. Use the documentation practice for source review, coverage, links, and reviewed fingerprints. Use the portable procedure to adopt those gates in another project.

Change the site

Install the pinned site tools through checkout setup:
  1. Change the mapped canonical document.
  2. If the change needs a new public page, add its source and route to site.json.
  3. Add the page to the navigation exactly once.
  4. If a public route changes, add a redirect to the replacement.
  5. Refresh the generated public pages.
The npm alias uses the same operation:
Examine the projection and Mintlify input before a push:
That command examines the projection, Mintlify configuration, navigation, local links, heading anchors, and redirects. It also runs the pinned Mintlify validation and broken-link procedures. Missing sources, absent generated pages, stale copies, and invalid destinations fail admission. Deletion of docs/public cannot produce a successful no-op. For a local preview, use:
A local preview does not establish a deployed result. After source review and native finalization, refresh the documentation review record through the documented procedure. Review that record with the canonical and generated page changes.

Examine the deployed result

A merge to main supplies Mintlify’s configured source. The site workflow waits for current content within a bounded interval. It fails when the site continues to serve stale content. Its retained receipt records the comparison result. After a timeout, the receipt keeps the last response results and their rejection reasons. Package publication and a passing source build do not establish website publication. Examine the live site with:
The command compares every projected page’s normalized rendered Markdown content with the expected canonical blocks. The comparison preserves link destinations and code indentation. Mintlify rewrites homepage links and table separators. The comparison treats those forms as equivalent. Table rows, cells, content, and alignment remain part of the comparison. It rejects a missing page or a different body. This comparison establishes returned content, rather than browser layout or an exact hosted build SHA. Mintlify’s deployment status and a browser visit supply separate evidence. For a candidate checker probe, dispatch the workflow from its branch:
A non-main manual run compares the candidate runtime against main source and the current site. The receipt records separate commits for the checker and expected documents. This probe does not expect pending candidate prose on the site. A candidate probe requests each page once. Before a live-site claim, examine the homepage, installation guide, documentation practice, and portable adoption guide in a browser. Use the navigation to reach the changed pages. Examine the content, source links, and retained redirects. Keep the deployment identity, content result, browser result, and their limits separate in the delivery report.

Recover from a failed deployment

Examine Mintlify’s configured repository, deploy branch, and content directory before a retry. They must select amichne/slopsentral, main, and docs/public. An existing domain or an earlier successful build cannot establish current content. If the source gate fails, repair the canonical source, route map, or projection owner. If the live comparison fails, examine the deployment status and the returned page before another publication. Keep earlier release artifacts and unrelated site settings unchanged.