Files
malkuthro-ComfyUI-Koolook/docs/user_guide
malkuthroandClaude Opus 4.7 ee8ccefdf8 docs(reorg) + chore: roll [Unreleased] forward + bump 0.1.7 (#37)
Bundles two changes for v0.1.7:

1. PR #36 (already on main, just rolling [Unreleased] -> [0.1.7]):
   suffix all node display names with " (Koolook)" so they group
   together in ComfyUI's node-add search. Class IDs unchanged.

2. Docs reorg:
   - git mv Glossary.md            -> docs/reference/glossary.md
   - git mv RELEASING.md           -> docs/maintainers/releasing.md
   - Three audience buckets under docs/: user_guide/ (end users),
     reference/ (lookups), maintainers/ (project ops). Each gets a
     short index README.md.
   - Top-level docs/README.md as the navigation entry point.
   - New: docs/maintainers/registry-api.md captures the Comfy Registry
     undocumented version-management API (deprecate/yank/status enum,
     auto-deprecation behavior, curl recipes, optional GH Actions
     workflow YAML for codified mgmt without exposing the token).
   - New: docs/maintainers/node-versioning.md codifies the rules from
     the v0.1.5 PR-review discussion for changing INPUT_TYPES /
     RETURN_TYPES / class names without breaking saved workflows.
   - Imported the existing untracked docs/ images that the maintainer
     started locally (node inventory screenshot, Easy Image Batch
     helper image).
   - Cross-references updated in README.md, CLAUDE.md, the issue
     template, and .claude/skills/add-external-fork/SKILL.md.

Root drops from 6 -> 4 markdown files. The four that stay (README,
LICENSE, CHANGELOG, CLAUDE.md) are the ones that *must* live there for
GitHub / Comfy Registry / tooling / Claude Code reasons.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-03 23:26:46 +02:00
..

User guide

End-user documentation for the nodes shipped by ComfyUI-Koolook. Search for a node by display name in ComfyUI (type "koolook" in the node-add menu) and see the corresponding guide here.

Available guides

(Stub — guides are added as they're written. The starter image in img/Easy_Image_Batch_v0.1.5.png is the first one queued.)

When to add a guide

If a node has any of:

  • non-obvious input semantics (e.g. aspect-ratio strings, frame indexing conventions),
  • a workflow recipe more useful than the per-input tooltips,
  • a known limitation or compatibility caveat,

→ create a per-node markdown file here, name it after the canonical node ID (e.g. easy_image_batch.md, easy_resize_koolook.md), and add it to the "Available guides" table above.

Screenshots and helper images go in img/, named to match the file they're embedded in (e.g. Easy_Image_Batch_v0.1.5.png).

Where to find the node IDs

The canonical list is in the project README.md and reference/.