docs: add operations guides and Fumadocs documentation site - #9
Merged
Conversation
Track the root docs/ guide and apps/docs source as the source of truth while ignoring package-level api-extractor artifacts and the fumadocs content build.
Deployment, security model, OIDC integration and development guides published from apps/docs.
Next.js static-export app (apps/docs) that publishes the root guides and per-package API references. prepare-content regenerates content/ from docs/*.mdx and packages' docs.api.json before each build. The design mirrors the platform portal (dark navy, mint accent).
The first consumer does not belong on the public docs landing page.
Matches the api/ group so guides and reference are separated in the sidebar tree.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
development) as MDX sources — the single source of truth
renders the guides plus the per-package API reference generated from each
package's
docs.api.json.github/workflows/docs.ymlpublishes the site to thegh-pagesbranch and Cloudflare Pages (
inft-auth-docsproject)root README now points to the docs site
docs/andapps/docswhile ignoringpackage-level api-extractor artifacts and the fumadocs content build
Verification
apps/docsstatic export builds 97 routes (guides + API reference)/docs/guides/*and/docs/api/{shared,auth-core,auth-sdk}/*apps/docstypecheck passes