4.0 KiB
type, title, description, tags, resource, timestamp
| type | title | description | tags | resource | timestamp | ||||
|---|---|---|---|---|---|---|---|---|---|
| Guide | Local Reference Docs Overview | How Sage Utils maintains a local mirror of ComfyUI reference documentation and the upstream sync workflow. |
|
docs/ref_docs/overview.md | 2026-07-01T00:00:00Z |
Local Reference Docs Overview
This concept describes how Sage Utils keeps a local mirror of selected ComfyUI documentation and where that reference material lives.
Purpose
docs/ref_docs/ is the local reference docs collection for Sage Utils developers. It includes:
docs/ref_docs/upstream_docs/— a mirror of selected official ComfyUI docs fromhttps://github.com/Comfy-Org/docs.gitdocs/ref_docs/backend/— local backend development guidance and walkthroughsdocs/ref_docs/frontend/— local frontend JavaScript development referencedocs/ref_docs/extra/— additional resources such as workflow templates and tips
The local mirror is intended as a stable, offline-friendly reference for Sage Utils development.
Note: Custom node docs are authored under
js/docs/in the Sage Utils extension and are a primary source for node help content in the UI. See Node Documentation and Local JS Docs for the supported pattern.
Custom node development reference
For Sage Utils custom node authors, the local reference docs include both backend Python and frontend JavaScript guidance.
-
Backend documentation is under
docs/ref_docs/backend/and covers creating custom nodes in Python, including:walkthrough.md— step-by-step custom node creationserver_overview.md— key server-side custom node conceptslifecycle.md— how ComfyUI loads custom node modulesdatatypes.md,lists.md,tensors.md— ComfyUI data handling detailsimages_and_masks.md,expansion.md,lazy_evaluation.md— advanced runtime patternsmore_on_inputs.md,snippets.md— custom inputs and reusable code patterns
-
Frontend documentation is under
docs/ref_docs/frontend/and explains JS extension points for custom nodes, including:javascript_overview.md— frontend extension entry points andWEB_DIRECTORYjavascript_hooks.md— node hooks, prototype modifications, and app integrationjavascript_examples.md— example fragments for custom node JavaScriptjavascript_objects_and_hijacking.md— frontend object model and overridesjavascript_commands_keybindings.md— command, keybinding, and UI integration patterns
-
The upstream mirror also keeps the official ComfyUI docs in:
docs/ref_docs/upstream_docs/backend/for upstream backend custom node docsdocs/ref_docs/upstream_docs/js/for upstream frontend JavaScript docs
This section is the quick starting point for developers looking for the backend and frontend custom node guidance available in the local docs collection.
Sync workflow
The current sync workflow is:
- Run
./docs/ref_docs/sync_upstream_docs.sh - That wrapper invokes
docs/ref_docs/sync_upstream_docs.py - The script clones
https://github.com/Comfy-Org/docs.gitat the configured ref (defaultmain) - It performs a sparse checkout of these upstream folders:
custom-nodesdevelopmentinterfaceinstallation
- The selected content is copied into
docs/ref_docs/upstream_docs/
The mirror keeps .mdx source files intact but renames them to .md locally.
Sync metadata
Each sync run writes docs/ref_docs/upstream_docs/SYNC_INFO.txt with:
- source repository URL
- source ref
- source commit
- sync timestamp
- included paths
Maintenance guidance
- Keep
docs/ref_docs/sync_upstream_docs.pyaligned with upstream path changes. - Add or remove upstream folders only after verifying the target repo layout and intended developer use cases.
- Use this OKF concept as the canonical overview location; the original
docs/ref_docs/overview.mdhas been retired. - Update
.github/instructions/sage.instructions.mdif the local docs entry points change.