Add Fumadocs plugin/theme API site - #1
Merged
Conversation
Static-export Next.js site for developers.dripnex.app, sourced from @dripnex/plugin-api types (PluginContext, tokens, layout zones) rather than stale user-manual MDX. Publish path is git tag + packed GitHub release; no marketplace. Co-authored-by: Tomás Maritano <tomymaritano@gmail.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (5)
📒 Files selected for processing (36)
📝 WalkthroughWalkthroughAdded the Dripnex developer documentation site. The change includes Next.js and Fumadocs setup, static documentation routes, shared navigation and styling, CI configuration, and comprehensive plugin, theme, publishing, and API reference content. ChangesDocumentation site
Estimated code review effort: 3 (Moderate) | ~25 minutes Sequence Diagram(s)sequenceDiagram
participant Browser
participant NextRoute
participant FumadocsSource
participant MDXComponents
Browser->>NextRoute: Request documentation slug
NextRoute->>FumadocsSource: Load page and metadata
FumadocsSource-->>NextRoute: Return content and table of contents
NextRoute->>MDXComponents: Render MDX body
MDXComponents-->>Browser: Return rendered documentation page
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Fumadocs + Next.js static-export site for developers.dripnex.app, modeled on developers.inkdrop.app. Tooling matches dripnex/docs-site (pnpm, Fumadocs, Cloudflare Pages project
dripnex-developers).Content
init.js(InitApi/dripnex— host plugin-api, not Inkdrop Atom APIs),styles.cssand theme tokens.CORE_THEME_TOKENS/THEME_EXTENSION_SCOPES/theme.json), publishing via git tag +dripnex-plugin packGitHub release. No public marketplace.packages/plugin-apiondevelop(PluginContext, commands, editor, themes, layout zones, DataAPI). Stale docs-site methods (getTheme,themeType, 9-zone list) are not copied.plugin-stamp,plugin-mermaid/plugin-math(insert snippets, not renderers),plugin-vim,theme-*.Deploy
Pages project
dripnex-developers→dripnex-developers.pages.dev. When DNS is ready: CNAMEdevelopers→dripnex-developers.pages.dev.Build (
pnpm build) will be verified on this PR after install.Summary by CodeRabbit
New Features
Documentation
Chores