Keep your docs close to the code.
Docs for API teams, kept close to code and ready to review.
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.
--header authorization
response 200 OK
Tabs: cURL / JavaScript / Python
Reference block: parameters, response, errors
Release block: changed, deprecated, migrated
Preview
GET endpoint
Sample endpoint: GET /v1/workspaces/{workspace_id}/pages.
Check the rendered page, links, navigation, and version context before publishing.
A clear path from repository to preview.
Keep source, endpoint content, and preview together.
Turn the next docs change into a reviewable step.
WALLACH / WORKFLOWWrite with code.
Keep guides and reference content in a repository-shaped workspace.
Shape the reference.
Use endpoint content, examples, and reusable blocks together.
Preview before publishing.
Check links, navigation, and version context in one rendered pass.
Find the right version
- Version switcher: Current / v2 / v1
- Search prompt: Search guides and reference
Workspace pages
Open the current endpoint reference without losing the version context around it.
Keep current and previous docs visible without making the reader guess where a page went.
Useful patterns, shown in context.
Use the same patterns across guides, reference, and releases.
Component catalog
Original patterns for guides and reference.
Code tabs
cURL, JavaScript, and Python.
response
errors
Reference blocks
Parameters, response, and errors.
Release blocks
Changed, deprecated, migrated.
/v1/workspaces/{workspace_id}/pages
200 OK
GET endpoint
Reference beside the explanation.
-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.
Rendered page
Read the page as a developer will see it.
Links and navigation
Check the route, hierarchy, and page connections.
Version context
Keep the selected version visible through the review.
API examples
Compare the endpoint explanation with its request.
Release notes
Make changed and migrated content easy to scan.
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.
Content inventory
Start with the pages and routes already in motion.
→ /v2/guides
/reference
→ /v2/reference
Map routes and versions
Keep the destination structure visible before moving pages.
Convert components
Move reusable pieces in deliberate stages.