Skip to content

[API Docs] Generate reference from OpenAPI - #29

Open
phawk wants to merge 3 commits into
mainfrom
pete/conductor-setup-scripts
Open

[API Docs] Generate reference from OpenAPI#29
phawk wants to merge 3 commits into
mainfrom
pete/conductor-setup-scripts

Conversation

@phawk

@phawk phawk commented Sep 2, 2026

Copy link
Copy Markdown
Member

Generate the REST API reference from the sandbox OpenAPI contract so published documentation stays aligned with the Rails API.

  • Add a versioned OpenAPI snapshot and generate Docusaurus pages during start/build
  • Add CI validation plus a scheduled workflow that opens contract-sync pull requests
  • Style generated operation pages to match the existing PayHere documentation theme
  • Remove superseded hand-written API pages and preserve all legacy URLs with HTTP 301 redirects
  • Update navigation and internal links to use the generated reference
  • Add Conductor setup and run scripts for consistent local workspaces

Validation

  • yarn api:lint
  • yarn api:sync --check
  • yarn build

- Install locked Yarn dependencies during setup
- Run Docusaurus on each workspace's allocated port
- Allow independent workspaces to run concurrently
- Expose the local development command as the default action
- Store the deployed public v1 contract as a checked-in snapshot.
- Generate Docusaurus reference pages before local and CI builds.
- Add curated endpoint navigation and language code samples.
- Sync the sandbox contract without formatting-only file churn.
- Validate the contract and documentation through GitHub Actions.
- Open scheduled update PRs when the deployed contract changes.
- Theme generated pages for PayHere light and dark modes.
- Document the reference workflow and supported Node versions.
- Remove superseded hand-written API reference pages
- Use the OpenAPI-generated reference as the sole API sidebar
- Redirect all legacy API URLs with explicit HTTP 301 responses
- Update site links to use canonical generated API routes
- Document redirect maintenance for operation ID changes
@vercel

vercel Bot commented Sep 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
developers Ready Ready Preview Sep 2, 2026 7:24pm UTC

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant