Repository readyPreview

Keep your docs close to the code.

Docs for API teams, kept close to code and ready to review.

A working surface for the docs workflow.
Repository authoringwrite beside the code
Reusable patternsrepeat what works
API referenceendpoint content
Release noteskeep changes clear
Versionskeep context close
Searchfind the right page
Preview checksreview before publish
Migration supportmove in stages
Wallach workflowauthorversionreferencepreviewpublish

Make the patterns repeatable.

Give every page the same useful building blocks without making every page feel the same.

Use components for explanations, endpoint details, version notes, and the small moments that help readers keep moving.

Use original examples for cURL, JavaScript, and Python.

code
cURLJavaScriptPython
curl /v1/workspaces
  --header authorization

response 200 OK

Tabs: cURL / JavaScript / Python

reference
GET
workspace_id

Reference block: parameters, response, errors

release
changednew endpoint content
deprecatedprevious route
migratedversion note

Release block: changed, deprecated, migrated

review
Rendered page
Links and navigation
Version context
Ready for review

Preview

endpoint
GET
/v1/workspaces/{workspace_id}/pages

GET endpoint

Sample endpoint: GET /v1/workspaces/{workspace_id}/pages.

Check the rendered page, links, navigation, and version context before publishing.

Open preview checks

A clear path from repository to preview.

Keep source, endpoint content, and preview together.

Explore the workflow

Turn the next docs change into a reviewable step.

WALLACH / WORKFLOW
01 / AUTHOR

Write with code.

Keep guides and reference content in a repository-shaped workspace.

/docs/getting-started.mdx
02 / GENERATE

Shape the reference.

Use endpoint content, examples, and reusable blocks together.

GET /v1/workspaces/:id/pages
03 / REVIEW

Preview before publishing.

Check links, navigation, and version context in one rendered pass.

preview: ready for review

Useful patterns, shown in context.

Use the same patterns across guides, reference, and releases.

Browse component examples
Original mint documentation guide orbit
CalloutKeep context beside the action.

Component catalog

Original patterns for guides and reference.

Original coral and blue endpoint route prism

Code tabs

cURL, JavaScript, and Python.

Original violet and green release-note sculpture
GET /pagesparameters

response

errors

Reference blocks

Parameters, response, and errors.

changednew content
deprecatedold route
migratednew version

Release blocks

Changed, deprecated, migrated.

GET
/v1/workspaces/{workspace_id}/pages

200 OK

GET endpoint

Reference beside the explanation.

curl https://api.wallach.example/v1/workspaces/ws_123/pages

-H Authorization: Bearer
$WALLACH_TOKEN

Request examples

Original examples for the docs team.

Review the rendered page.

Preview checks keep the useful details visible before a change is published.

Preview the docs workspace
01

Rendered page

Read the page as a developer will see it.

02

Links and navigation

Check the route, hierarchy, and page connections.

03

Version context

Keep the selected version visible through the review.

04

API examples

Compare the endpoint explanation with its request.

05

Release notes

Make changed and migrated content easy to scan.

06

Ready for review

Leave a clear next step for the docs team.

Move docs in clear steps

Map the current structure, then review the first pages before moving more.

Guidesinventory
API referenceinventory
Release notesreview
Navigationready

Content inventory

Start with the pages and routes already in motion.

/guides
→ /v2/guides
/reference
→ /v2/reference

Map routes and versions

Keep the destination structure visible before moving pages.

Calloutsconverted
Code tabsconverted
API blocksreview

Convert components

Move reusable pieces in deliberate stages.