Repository navigation
docs: add partner-node tutorials for 11 P0 providers - #942
Merged
comfyui-wiki merged 13 commits intoOct 25, 2026
Merged
Conversation
… Magnific, PixVerse, Quiver, Veo, Topaz, HitPaw, WaveSpeed Each provider gets a dedicated mdx page with overview, key capabilities, and available workflows (Cloud Run + Download JSON cards). Follows the existing Seedance 2.0 page format.
Split each single provider .mdx into overview + per-model subpages: - ElevenLabs: overview + 6 model pages (multilingual-v2, scribe-v2, sts, sfx, dialogue, isolation) - Grok: overview + grok-imagine + grok-video - Vidu: overview + q1/q2/q3 - MiniMax: overview + minimax-01 + minimax-s2v-01 - Magnific: overview + upscale + creative-tools - PixVerse: overview + video - Quiver: overview + svg - Veo: overview + veo-2-0 + veo-3-1 - Topaz: overview + image + video-enhance - HitPaw: overview + image-enhance + video-enhance - WaveSpeed: overview + upscale + flashvsr New structure: overview.mdx (platform intro + model index) + per-model .mdx (capabilities + workflows)
…, resolution support, style specialties - Remove 'beta release' phrasing, reflect Pro/Standard/Beta coexistence - Add ~4s/image speed benchmark, 1K/2K resolution info, image edit input limits - Add video generation time estimates (~60s extend, ~100s 720p reference) - Add style specialties: anime, cyberpunk, motion graphics, world rebuilding
…character coordination, dynamic rendering improvements - Expand camera control details (push/pull/orbit/follow/close-up) - Add expression & micro-movement, dynamic rendering capabilities - Add multi-character coordination and scene composition - Note Turbo/Pro/Standard model variants - Remove 'Four generation modes' → 'Six generation modes'
…n, duration/amplitude details Borrowed context from wavespeed.ai model page for parameter details.
PR Comfy-Org#942 restructured partner node pages from flat files (elevenlabs.mdx) to subdirectory structure (elevenlabs/overview.mdx + model pages). Added 6 redirects for the moved files.
|
Important Review skippedWe couldn't safely recover the incremental review. No full review was started, and the last reviewed checkpoint was preserved. Retry later, or explicitly request a full review by commenting You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. ℹ️ Recent review info
Walkthrough
Priority: Merge Risk:
 |
| Check name | Status | Explanation |
|---|---|---|
| Linked Issues check |  |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
✨ Finishing Touches: 💡 1
-
🛠️ Fix failing CI checks: 💡
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Create a new PR
✨ Simplify code
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
tutorials/partner-nodes/vidu/vidu-q2.mdx (1)
73-83: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winRemove the duplicate section.
Double trouble, a magical clone! This entire section is a repeat of the one above. Let's send this duplicate back to the unknown to keep our pages lean and clean.
🧹 Proposed fix to remove the duplicate section
-### First last frame to video - -<CardGroup cols={2}> - <Card title="Run Q2 First-Last-Frame-to-Video on Cloud" icon="cloud" href="https://cloud.comfy.org/?template=api_vidu_q2_flf2v&utm_source=docs"> - Try the Q2 First-Last-Frame-to-Video workflow instantly on Comfy Cloud. - </Card> - <Card title="Download Q2 First-Last-Frame-to-Video workflow" icon="download" href="https://github.com/Comfy-Org/workflow_templates/blob/main/templates/api_vidu_q2_flf2v.json"> - Download the workflow JSON. - </Card> -</CardGroup>🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@tutorials/partner-nodes/vidu/vidu-q2.mdx` around lines 73 - 83, Remove the duplicate “First last frame to video” section, including its CardGroup and both workflow links, from the tutorial. Preserve the original section above and all surrounding unique content.tutorials/partner-nodes/wavespeed/wavespeed-upscale.mdx (1)
28-41: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winFix the
wavesppedtypos in the link targets. Useapi_wavespeed_image_upscaleandapi_wavespeed_seedvr2_ai_image_fixin both the ComfyCloud URLs and the JSON links. One missingesends the links adrift.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@tutorials/partner-nodes/wavespeed/wavespeed-upscale.mdx` around lines 28 - 41, Correct the misspelled “wavespped” segment in the href values for both workflow cards: use api_wavespeed_image_upscale for the image upscale ComfyCloud and JSON links, and api_wavespeed_seedvr2_ai_image_fix for the SeedVR2 ComfyCloud and JSON links. Leave the card labels and surrounding content unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs.json`:
- Around line 6795-6824: Update the redirect configuration around the existing
partner-node redirects to add corresponding zh and ja mappings for every moved
provider page, preserving each old localized flat-file URL while targeting its
localized overview path. Verify Grok, HitPaw, Magnific, PixVerse, and Quiver
against their prior URL structure, and add redirects for them when their pages
also moved; retain the existing English and catch-all locale behavior.
- Around line 321-326: Update the navigation group entries in docs.json at
321-326, 335-370, 436-441, 472-483, and 495-500 so English paths use
tutorials/.../overview and include every corresponding model-specific subpage;
apply the same model-page additions and locale-prefixed overview paths to
docs.json at 2483-2488, 2497-2532, 2598-2603, 2634-2645, and 2657-2662 for
Chinese, and at 4650-4655, 4664-4699, 4765-4770, 4801-4812, and 4824-4829 for
Japanese. Preserve each provider group (ElevenLabs, Grok, HitPaw, Magnific,
MiniMax, PixVerse, Quiver, Topaz, Veo, Vidu, and WaveSpeed) while replacing
stale slugs with the appropriate overview path and adding all newly available
model subpages.
In `@tutorials/partner-nodes/elevenlabs/overview.mdx`:
- Line 10: Use neutral technical wording in
tutorials/partner-nodes/elevenlabs/overview.mdx:10 by replacing “brings
world-class voice AI” with phrasing such as “provides voice AI models.” In
tutorials/partner-nodes/elevenlabs/eleven-multilingual-v2.mdx:10, remove
“flagship” while preserving the factual model description.
- Around line 14-19: Replace every em dash in the specified documentation with
guideline-compliant punctuation: use colons for list-item separators and the
requested title or descriptive separators, and use parentheses, commas, or
rephrasing for the specified descriptions. Update
tutorials/partner-nodes/elevenlabs/overview.mdx lines 14-19;
tutorials/partner-nodes/elevenlabs/eleven-multilingual-v2.mdx lines 2 and 14-17;
tutorials/partner-nodes/elevenlabs/scribe-v2.mdx lines 2 and 14-17;
tutorials/partner-nodes/grok/grok-imagine.mdx lines 2-3, 10, and 16-20; and
tutorials/partner-nodes/grok/grok-video.mdx lines 2, 10, and 16-21.
In `@tutorials/partner-nodes/elevenlabs/speech-to-speech.mdx`:
- Around line 14-16: Remove all em dashes from the documented sections: in
tutorials/partner-nodes/elevenlabs/speech-to-speech.mdx lines 14-16,
tutorials/partner-nodes/elevenlabs/text-to-dialogue.mdx lines 10 and 14-16,
tutorials/partner-nodes/elevenlabs/text-to-sound-effects.mdx lines 10 and 14-16,
tutorials/partner-nodes/elevenlabs/voice-isolation.mdx lines 10 and 14-17, and
tutorials/partner-nodes/grok/overview.mdx lines 3 and 16-21. Replace them with
colons in the key capabilities lists, a period at text-to-dialogue line 10,
commas for the appositive phrase at text-to-sound-effects line 10, and a colon
introducing examples at voice-isolation line 10.
In `@tutorials/partner-nodes/hitpaw/overview.mdx`:
- Around line 10-11: Use a technical-reference tone by removing
“production-grade” from the HitPaw overview description in
tutorials/partner-nodes/hitpaw/overview.mdx lines 10-11 while preserving the
functionality-focused wording. Also remove “professional-grade” and
“studio-quality” from tutorials/partner-nodes/magnific/overview.mdx lines 10-11,
and remove “studio-quality” from
tutorials/partner-nodes/magnific/magnific-creative-tools.mdx lines 10-11; make
no other content changes.
In `@tutorials/partner-nodes/topaz/overview.mdx`:
- Around line 14-20: Replace all em dashes and stacked dash-joined clauses in
the specified documentation sites with the requested punctuation while
preserving the technical meaning. In tutorials/partner-nodes/topaz/overview.mdx
lines 14-20, use colons; lines 3 and 10 require commas and removal of the
marketing clause respectively. Apply the specified comma and colon replacements
in tutorials/partner-nodes/topaz/topaz-image.mdx lines 3 and 14-18 and
tutorials/partner-nodes/topaz/topaz-video-enhance.mdx lines 3 and 14-18. In
tutorials/partner-nodes/veo/overview.mdx lines 3, 10, and 14-19, use
parentheses, separate sentences, and colons respectively; make the listed colon,
sentence-splitting, and colon replacements in
tutorials/partner-nodes/veo/veo-2-0.mdx lines 2, 10, and 14-16, and
tutorials/partner-nodes/veo/veo-3-1.mdx lines 2-3, 14-17, 24, and 33.
---
Outside diff comments:
In `@tutorials/partner-nodes/vidu/vidu-q2.mdx`:
- Around line 73-83: Remove the duplicate “First last frame to video” section,
including its CardGroup and both workflow links, from the tutorial. Preserve the
original section above and all surrounding unique content.
In `@tutorials/partner-nodes/wavespeed/wavespeed-upscale.mdx`:
- Around line 28-41: Correct the misspelled “wavespped” segment in the href
values for both workflow cards: use api_wavespeed_image_upscale for the image
upscale ComfyCloud and JSON links, and api_wavespeed_seedvr2_ai_image_fix for
the SeedVR2 ComfyCloud and JSON links. Leave the card labels and surrounding
content unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 0ed4ec73-cbd6-4cff-9941-481a78a6e3ca
📒 Files selected for processing (37)
docs.jsontutorials/partner-nodes/elevenlabs/eleven-multilingual-v2.mdxtutorials/partner-nodes/elevenlabs/overview.mdxtutorials/partner-nodes/elevenlabs/scribe-v2.mdxtutorials/partner-nodes/elevenlabs/speech-to-speech.mdxtutorials/partner-nodes/elevenlabs/text-to-dialogue.mdxtutorials/partner-nodes/elevenlabs/text-to-sound-effects.mdxtutorials/partner-nodes/elevenlabs/voice-isolation.mdxtutorials/partner-nodes/grok/grok-imagine.mdxtutorials/partner-nodes/grok/grok-video.mdxtutorials/partner-nodes/grok/overview.mdxtutorials/partner-nodes/hitpaw/hitpaw-image-enhance.mdxtutorials/partner-nodes/hitpaw/hitpaw-video-enhance.mdxtutorials/partner-nodes/hitpaw/overview.mdxtutorials/partner-nodes/magnific/magnific-creative-tools.mdxtutorials/partner-nodes/magnific/magnific-upscale.mdxtutorials/partner-nodes/magnific/overview.mdxtutorials/partner-nodes/minimax/minimax-01.mdxtutorials/partner-nodes/minimax/minimax-s2v-01.mdxtutorials/partner-nodes/minimax/overview.mdxtutorials/partner-nodes/pixverse/overview.mdxtutorials/partner-nodes/pixverse/pixverse-video.mdxtutorials/partner-nodes/quiver/overview.mdxtutorials/partner-nodes/quiver/quiver-svg.mdxtutorials/partner-nodes/topaz/overview.mdxtutorials/partner-nodes/topaz/topaz-image.mdxtutorials/partner-nodes/topaz/topaz-video-enhance.mdxtutorials/partner-nodes/veo/overview.mdxtutorials/partner-nodes/veo/veo-2-0.mdxtutorials/partner-nodes/veo/veo-3-1.mdxtutorials/partner-nodes/vidu/overview.mdxtutorials/partner-nodes/vidu/vidu-q1.mdxtutorials/partner-nodes/vidu/vidu-q2.mdxtutorials/partner-nodes/vidu/vidu-q3.mdxtutorials/partner-nodes/wavespeed/overview.mdxtutorials/partner-nodes/wavespeed/wavespeed-flashvsr.mdxtutorials/partner-nodes/wavespeed/wavespeed-upscale.mdx
Comment on lines
+321
to
+326
| { | ||
| "group": "ElevenLabs", | ||
| "pages": [ | ||
| "partner-nodes/elevenlabs/elevenlabs" | ||
| ] | ||
| }, |
There was a problem hiding this comment.
🎯 Functional Correctness | 🔴 Critical | 🏗️ Heavy lift
Broken navigation links and orphaned model pages.
The navigation entries here are pointing to stale flat-file slugs (like [provider]/[provider]) instead of the new hierarchical overview structure. Additionally, the English entries completely missed the tutorials/ prefix! If these point to non-existent files, the documentation build will throw a fit (or at least silently drop them). Furthermore, the newly added model-specific subpages (e.g., eleven-multilingual-v2, veo-2-0, etc.) are missing from the sidebar arrays. Let's fix this glitch so the links don't end up in a ditch!
docs.json#L321-L326: Replace"partner-nodes/elevenlabs/elevenlabs"with"tutorials/partner-nodes/elevenlabs/overview"and add its model subpages to the array.docs.json#L335-L370: Update Grok, HitPaw, Magnific, MiniMax, PixVerse, and Quiver entries to use thetutorials/.../overviewpath and include their respective model subpages.docs.json#L436-L441: Update the Topaz entry to usetutorials/.../overviewand include its model subpages.docs.json#L472-L483: Update the Veo and Vidu entries to usetutorials/.../overviewand include their model subpages.docs.json#L495-L500: Update the WaveSpeed entry to usetutorials/.../overviewand include its model subpages.docs.json#L2483-L2488: Update the Chinese ElevenLabs entry to"zh/tutorials/partner-nodes/elevenlabs/overview"and include its model subpages.docs.json#L2497-L2532: Update Chinese entries for Grok, HitPaw, Magnific, MiniMax, PixVerse, and Quiver to use/overviewand include their model subpages.docs.json#L2598-L2603: Update the Chinese Topaz entry to use/overviewand include its model subpages.docs.json#L2634-L2645: Update the Chinese Veo and Vidu entries to use/overviewand include their model subpages.docs.json#L2657-L2662: Update the Chinese WaveSpeed entry to use/overviewand include its model subpages.docs.json#L4650-L4655: Update the Japanese ElevenLabs entry to"ja/tutorials/partner-nodes/elevenlabs/overview"and include its model subpages.docs.json#L4664-L4699: Update Japanese entries for Grok, HitPaw, Magnific, MiniMax, PixVerse, and Quiver to use/overviewand include their model subpages.docs.json#L4765-L4770: Update the Japanese Topaz entry to use/overviewand include its model subpages.docs.json#L4801-L4812: Update the Japanese Veo and Vidu entries to use/overviewand include their model subpages.docs.json#L4824-L4829: Update the Japanese WaveSpeed entry to use/overviewand include its model subpages.
📍 Affects 1 file
docs.json#L321-L326(this comment)docs.json#L335-L370docs.json#L436-L441docs.json#L472-L483docs.json#L495-L500docs.json#L2483-L2488docs.json#L2497-L2532docs.json#L2598-L2603docs.json#L2634-L2645docs.json#L2657-L2662docs.json#L4650-L4655docs.json#L4664-L4699docs.json#L4765-L4770docs.json#L4801-L4812docs.json#L4824-L4829
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs.json` around lines 321 - 326, Update the navigation group entries in
docs.json at 321-326, 335-370, 436-441, 472-483, and 495-500 so English paths
use tutorials/.../overview and include every corresponding model-specific
subpage; apply the same model-page additions and locale-prefixed overview paths
to docs.json at 2483-2488, 2497-2532, 2598-2603, 2634-2645, and 2657-2662 for
Chinese, and at 4650-4655, 4664-4699, 4765-4770, 4801-4812, and 4824-4829 for
Japanese. Preserve each provider group (ElevenLabs, Grok, HitPaw, Magnific,
MiniMax, PixVerse, Quiver, Topaz, Veo, Vidu, and WaveSpeed) while replacing
stale slugs with the appropriate overview path and adding all newly available
model subpages.
Comment on lines
+6795
to
+6824
| { | ||
| "source": "/tutorials/partner-nodes/elevenlabs/elevenlabs", | ||
| "destination": "/tutorials/partner-nodes/elevenlabs/overview" | ||
| }, | ||
| { | ||
| "source": "/tutorials/partner-nodes/minimax/minimax", | ||
| "destination": "/tutorials/partner-nodes/minimax/overview" | ||
| }, | ||
| { | ||
| "source": "/tutorials/partner-nodes/topaz/topaz", | ||
| "destination": "/tutorials/partner-nodes/topaz/overview" | ||
| }, | ||
| { | ||
| "source": "/tutorials/partner-nodes/veo/veo", | ||
| "destination": "/tutorials/partner-nodes/veo/overview" | ||
| }, | ||
| { | ||
| "source": "/tutorials/partner-nodes/vidu/vidu", | ||
| "destination": "/tutorials/partner-nodes/vidu/overview" | ||
| }, | ||
| { | ||
| "source": "/tutorials/partner-nodes/wavespeed/wavespeed", | ||
| "destination": "/tutorials/partner-nodes/wavespeed/overview" | ||
| }, | ||
| { | ||
| "source": "/zh-CN/:slug*", | ||
| "destination": "/zh/:slug*" | ||
| } | ||
| ] | ||
| } | ||
| } No newline at end of file |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Missing redirects for localized pages and other providers.
You've added redirects for the English files to map the old flat-file URLs to their new overview homes. However, the localized equivalents (zh and ja) are missing their redirects! Furthermore, 5 out of the 11 providers documented in this PR (Grok, HitPaw, Magnific, PixVerse, Quiver) don't have any redirects listed here. Were they born as folders, or did they also move? Better check twice, or your users might roll the 404 dice!
Please add the corresponding zh and ja redirects for the moved files, and verify if the other 5 providers need redirects as well to preserve existing links.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs.json` around lines 6795 - 6824, Update the redirect configuration around
the existing partner-node redirects to add corresponding zh and ja mappings for
every moved provider page, preserving each old localized flat-file URL while
targeting its localized overview path. Verify Grok, HitPaw, Magnific, PixVerse,
and Quiver against their prior URL structure, and add redirects for them when
their pages also moved; retain the existing English and catch-all locale
behavior.
| import ReqHint from "/snippets/tutorials/partner-nodes/req-hint.mdx"; | ||
| import UpdateReminder from "/snippets/tutorials/update-reminder.mdx"; | ||
|
|
||
| ElevenLabs brings world-class voice AI to ComfyUI, covering text-to-speech, speech-to-text, sound effects, voice isolation, and voice transformation. Its **Eleven v3** and **Multilingual v2** models deliver emotionally expressive speech across 29 languages, while **Scribe v2** provides fast, accurate transcription with speaker diarization and entity detection. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Tone down the marketing language for technical documentation.
As per coding guidelines, English documentation should match the tone of a technical reference rather than a marketing blog. Time to ditch the sales pitch, and scratch that technical itch!
tutorials/partner-nodes/elevenlabs/overview.mdx#L10-L10: Replace "brings world-class voice AI" with a more neutral phrasing like "provides voice AI models".tutorials/partner-nodes/elevenlabs/eleven-multilingual-v2.mdx#L10-L10: Remove the word "flagship" to maintain a factual, technical tone.
📍 Affects 2 files
tutorials/partner-nodes/elevenlabs/overview.mdx#L10-L10(this comment)tutorials/partner-nodes/elevenlabs/eleven-multilingual-v2.mdx#L10-L10
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@tutorials/partner-nodes/elevenlabs/overview.mdx` at line 10, Use neutral
technical wording in tutorials/partner-nodes/elevenlabs/overview.mdx:10 by
replacing “brings world-class voice AI” with phrasing such as “provides voice AI
models.” In tutorials/partner-nodes/elevenlabs/eleven-multilingual-v2.mdx:10,
remove “flagship” while preserving the factual model description.
Source: Coding guidelines
Comment on lines
+14
to
+19
| - **Text to Speech** — Generate lifelike audio from text with three model tiers (Eleven v3, Multilingual v2, Flash v2.5) | ||
| - **Speech to Speech** — Transform a source audio clip into a different voice while keeping the original intonation and pacing | ||
| - **Speech to Text** — Transcribe audio with Scribe v2: 90+ languages, 32-speaker diarization, entity detection, keyword boost | ||
| - **Sound Effects** — Generate audio effects from text descriptions | ||
| - **Voice Isolation** — Separate voice from background noise, music, or ambient sound | ||
| - **Multi-Character Dialogue** — Generate conversations between multiple distinct voices in a single pass |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Replace em dashes with colons or parentheses to comply with documentation guidelines.
As per coding guidelines, avoid using em dashes (—) in MDX documentation, preferring colons, commas, or parentheses instead. Don't be a dash-ing rogue; let's keep our punctuation in vogue!
tutorials/partner-nodes/elevenlabs/overview.mdx#L14-L19: Replace the em dashes separating the list items with colons.tutorials/partner-nodes/elevenlabs/eleven-multilingual-v2.mdx#L2-L2: Replace the em dash in thetitlewith a colon.tutorials/partner-nodes/elevenlabs/eleven-multilingual-v2.mdx#L14-L17: Replace the em dashes separating the list items with colons.tutorials/partner-nodes/elevenlabs/scribe-v2.mdx#L2-L2: Replace the em dash in thetitlewith a colon.tutorials/partner-nodes/elevenlabs/scribe-v2.mdx#L14-L17: Replace the em dashes separating the list items with colons.tutorials/partner-nodes/grok/grok-imagine.mdx#L2-L3: Replace the em dash in thetitlewith a colon and the em dash in thedescriptionwith parentheses or a comma.tutorials/partner-nodes/grok/grok-imagine.mdx#L10-L10: Replace the em dash before "dramatic lighting" with a colon.tutorials/partner-nodes/grok/grok-imagine.mdx#L16-L20: Replace the em dashes separating the list items with colons.tutorials/partner-nodes/grok/grok-video.mdx#L2-L2: Replace the em dash in thetitlewith a colon.tutorials/partner-nodes/grok/grok-video.mdx#L10-L10: Replace the em dash with a comma or rephrase.tutorials/partner-nodes/grok/grok-video.mdx#L16-L21: Replace the em dashes separating the list items with colons.
📍 Affects 5 files
tutorials/partner-nodes/elevenlabs/overview.mdx#L14-L19(this comment)tutorials/partner-nodes/elevenlabs/eleven-multilingual-v2.mdx#L2-L2tutorials/partner-nodes/elevenlabs/eleven-multilingual-v2.mdx#L14-L17tutorials/partner-nodes/elevenlabs/scribe-v2.mdx#L2-L2tutorials/partner-nodes/elevenlabs/scribe-v2.mdx#L14-L17tutorials/partner-nodes/grok/grok-imagine.mdx#L2-L3tutorials/partner-nodes/grok/grok-imagine.mdx#L10-L10tutorials/partner-nodes/grok/grok-imagine.mdx#L16-L20tutorials/partner-nodes/grok/grok-video.mdx#L2-L2tutorials/partner-nodes/grok/grok-video.mdx#L10-L10tutorials/partner-nodes/grok/grok-video.mdx#L16-L21
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@tutorials/partner-nodes/elevenlabs/overview.mdx` around lines 14 - 19,
Replace every em dash in the specified documentation with guideline-compliant
punctuation: use colons for list-item separators and the requested title or
descriptive separators, and use parentheses, commas, or rephrasing for the
specified descriptions. Update tutorials/partner-nodes/elevenlabs/overview.mdx
lines 14-19; tutorials/partner-nodes/elevenlabs/eleven-multilingual-v2.mdx lines
2 and 14-17; tutorials/partner-nodes/elevenlabs/scribe-v2.mdx lines 2 and 14-17;
tutorials/partner-nodes/grok/grok-imagine.mdx lines 2-3, 10, and 16-20; and
tutorials/partner-nodes/grok/grok-video.mdx lines 2, 10, and 16-21.
Source: Coding guidelines
Comment on lines
+14
to
+16
| - **Preserve delivery** — Retain original intonation, pacing, and emotional expression | ||
| - **Voice transformation** — Apply a different voice identity to existing audio | ||
| - **Style transfer** — Change the vocal style or character without re-recording |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Remove em dashes across MDX files to comply with formatting guidelines.
A dash is a flash, but our rules say it's trash! As per coding guidelines, we must avoid em dashes (—) in English documentation and use periods, commas, colons, or parentheses instead to keep everything neat and spiffy in a jiffy.
tutorials/partner-nodes/elevenlabs/speech-to-speech.mdx#L14-L16: Replace the em dashes with colons in the key capabilities list.tutorials/partner-nodes/elevenlabs/text-to-dialogue.mdx#L10-L10: Replace the em dash with a period to separate the sentences.tutorials/partner-nodes/elevenlabs/text-to-dialogue.mdx#L14-L16: Replace the em dashes with colons in the key capabilities list.tutorials/partner-nodes/elevenlabs/text-to-sound-effects.mdx#L10-L10: Replace the em dashes with commas for the appositive phrase.tutorials/partner-nodes/elevenlabs/text-to-sound-effects.mdx#L14-L16: Replace the em dashes with colons in the key capabilities list.tutorials/partner-nodes/elevenlabs/voice-isolation.mdx#L10-L10: Replace the em dash with a colon to introduce the examples.tutorials/partner-nodes/elevenlabs/voice-isolation.mdx#L14-L17: Replace the em dashes with colons in the key capabilities list.tutorials/partner-nodes/grok/overview.mdx#L3-L3: Replace the em dash in the frontmatter description with a colon.tutorials/partner-nodes/grok/overview.mdx#L16-L21: Replace the em dashes with colons in the key capabilities list.
📍 Affects 5 files
tutorials/partner-nodes/elevenlabs/speech-to-speech.mdx#L14-L16(this comment)tutorials/partner-nodes/elevenlabs/text-to-dialogue.mdx#L10-L10tutorials/partner-nodes/elevenlabs/text-to-dialogue.mdx#L14-L16tutorials/partner-nodes/elevenlabs/text-to-sound-effects.mdx#L10-L10tutorials/partner-nodes/elevenlabs/text-to-sound-effects.mdx#L14-L16tutorials/partner-nodes/elevenlabs/voice-isolation.mdx#L10-L10tutorials/partner-nodes/elevenlabs/voice-isolation.mdx#L14-L17tutorials/partner-nodes/grok/overview.mdx#L3-L3tutorials/partner-nodes/grok/overview.mdx#L16-L21
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@tutorials/partner-nodes/elevenlabs/speech-to-speech.mdx` around lines 14 -
16, Remove all em dashes from the documented sections: in
tutorials/partner-nodes/elevenlabs/speech-to-speech.mdx lines 14-16,
tutorials/partner-nodes/elevenlabs/text-to-dialogue.mdx lines 10 and 14-16,
tutorials/partner-nodes/elevenlabs/text-to-sound-effects.mdx lines 10 and 14-16,
tutorials/partner-nodes/elevenlabs/voice-isolation.mdx lines 10 and 14-17, and
tutorials/partner-nodes/grok/overview.mdx lines 3 and 16-21. Replace them with
colons in the key capabilities lists, a period at text-to-dialogue line 10,
commas for the appositive phrase at text-to-sound-effects line 10, and a colon
introducing examples at voice-isolation line 10.
Source: Coding guidelines
Comment on lines
+10
to
+11
| HitPaw brings production-grade AI image and video enhancement to ComfyUI as native nodes. Its **image enhancement** and **video enhancement** models handle upscaling, denoising, and restoration with minimal configuration, all powered by ComfyCloud with no local GPU needed. | ||
|
|
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Tone down the marketing language for a technical reference.
As per coding guidelines, match the tone of surrounding pages by writing a technical reference rather than a marketing blog. We don't want to sound like a wizard selling potions, let's just stick to the technical notions! 🧙♂️
tutorials/partner-nodes/hitpaw/overview.mdx#L10-L11: Remove "production-grade" and focus directly on the node's functionality.tutorials/partner-nodes/magnific/overview.mdx#L10-L11: Remove "professional-grade" and "studio-quality" descriptors.tutorials/partner-nodes/magnific/magnific-creative-tools.mdx#L10-L11: Remove "studio-quality" to keep the focus purely on the features.
📍 Affects 3 files
tutorials/partner-nodes/hitpaw/overview.mdx#L10-L11(this comment)tutorials/partner-nodes/magnific/overview.mdx#L10-L11tutorials/partner-nodes/magnific/magnific-creative-tools.mdx#L10-L11
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@tutorials/partner-nodes/hitpaw/overview.mdx` around lines 10 - 11, Use a
technical-reference tone by removing “production-grade” from the HitPaw overview
description in tutorials/partner-nodes/hitpaw/overview.mdx lines 10-11 while
preserving the functionality-focused wording. Also remove “professional-grade”
and “studio-quality” from tutorials/partner-nodes/magnific/overview.mdx lines
10-11, and remove “studio-quality” from
tutorials/partner-nodes/magnific/magnific-creative-tools.mdx lines 10-11; make
no other content changes.
Source: Coding guidelines
Comment on lines
+14
to
+20
| - **Reimagine creative upscaling** — Guide the upscaling process with text prompts to creatively reinterpret and enhance images, not just enlarge them. | ||
| - **Face enhancement** — Dedicated facial detail reconstruction model that detects and sharpens faces in images and video, preserving natural skin texture and expression. | ||
| - **8K output support** — Upscale images and video frames to ultra-high 8K resolution while maintaining sharpness and visual coherence. | ||
| - **Starlight diffusion upscaler** — Diffusion-based upscaling optimized for landscape photography, hallucinating realistic detail like foliage, rock textures, and clouds. | ||
| - **Apollo frame interpolation** — Generate smooth intermediate frames between existing video frames for slow-motion effects or frame rate conversion. | ||
| - **Illustration-optimized upscale** — Specialized model for flat-colored artwork, line art, and digital illustrations that preserves hard edges and clean gradients. | ||
| - **Video enhancement pipeline** — Comprehensive video processing including denoising, deinterlacing, stabilization, and intelligent frame-by-frame upscaling. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Replace em dashes (—) and stacked clauses to meet documentation guidelines!
The mischievous em dash has crept in everywhere, let's clean it up with flair! As per coding guidelines, English MDX documentation must avoid em dashes (—) and stacked clauses joined by dashes; use periods, commas, colons, or new sentences instead. We also need to maintain a technical reference tone rather than a marketing blog feel. Let's fix these up so they shine bright and fair:
tutorials/partner-nodes/topaz/overview.mdx#L14-L20: Replace the em dashes in the bullet points with colons.tutorials/partner-nodes/topaz/overview.mdx#L3-L3: Replace the em dashes wrapping the model descriptions with commas.tutorials/partner-nodes/topaz/overview.mdx#L10-L10: Drop the marketing tone ("trusted by professionals worldwide") and remove the em dash; end the sentence after "ComfyUI".tutorials/partner-nodes/topaz/topaz-image.mdx#L3-L3: Replace the em dash with a comma.tutorials/partner-nodes/topaz/topaz-image.mdx#L14-L18: Replace the em dashes in the bullet points with colons.tutorials/partner-nodes/topaz/topaz-video-enhance.mdx#L3-L3: Replace the em dash with a comma.tutorials/partner-nodes/topaz/topaz-video-enhance.mdx#L14-L18: Replace the em dashes in the bullet points with colons.tutorials/partner-nodes/veo/overview.mdx#L3-L3: Replace the em dashes wrapping the model names with parentheses.tutorials/partner-nodes/veo/overview.mdx#L10-L10: Split the stacked clauses joined by the em dash into two separate sentences.tutorials/partner-nodes/veo/overview.mdx#L14-L19: Replace the em dashes in the bullet points with colons.tutorials/partner-nodes/veo/veo-2-0.mdx#L2-L2: Replace the em dash in the title with a colon.tutorials/partner-nodes/veo/veo-2-0.mdx#L10-L10: Split the stacked clauses joined by the em dash into two separate sentences.tutorials/partner-nodes/veo/veo-2-0.mdx#L14-L16: Replace the em dashes in the bullet points with colons.tutorials/partner-nodes/veo/veo-3-1.mdx#L2-L3: Replace the em dash in the title with a colon, and the em dash in the description with a period for a new sentence.tutorials/partner-nodes/veo/veo-3-1.mdx#L14-L17: Replace the em dashes in the bullet points with colons.tutorials/partner-nodes/veo/veo-3-1.mdx#L24-L24: Replace the em dash in the heading with a colon.tutorials/partner-nodes/veo/veo-3-1.mdx#L33-L33: Replace the em dash in the heading with a colon.
📍 Affects 6 files
tutorials/partner-nodes/topaz/overview.mdx#L14-L20(this comment)tutorials/partner-nodes/topaz/overview.mdx#L3-L3tutorials/partner-nodes/topaz/overview.mdx#L10-L10tutorials/partner-nodes/topaz/topaz-image.mdx#L3-L3tutorials/partner-nodes/topaz/topaz-image.mdx#L14-L18tutorials/partner-nodes/topaz/topaz-video-enhance.mdx#L3-L3tutorials/partner-nodes/topaz/topaz-video-enhance.mdx#L14-L18tutorials/partner-nodes/veo/overview.mdx#L3-L3tutorials/partner-nodes/veo/overview.mdx#L10-L10tutorials/partner-nodes/veo/overview.mdx#L14-L19tutorials/partner-nodes/veo/veo-2-0.mdx#L2-L2tutorials/partner-nodes/veo/veo-2-0.mdx#L10-L10tutorials/partner-nodes/veo/veo-2-0.mdx#L14-L16tutorials/partner-nodes/veo/veo-3-1.mdx#L2-L3tutorials/partner-nodes/veo/veo-3-1.mdx#L14-L17tutorials/partner-nodes/veo/veo-3-1.mdx#L24-L24tutorials/partner-nodes/veo/veo-3-1.mdx#L33-L33
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@tutorials/partner-nodes/topaz/overview.mdx` around lines 14 - 20, Replace all
em dashes and stacked dash-joined clauses in the specified documentation sites
with the requested punctuation while preserving the technical meaning. In
tutorials/partner-nodes/topaz/overview.mdx lines 14-20, use colons; lines 3 and
10 require commas and removal of the marketing clause respectively. Apply the
specified comma and colon replacements in
tutorials/partner-nodes/topaz/topaz-image.mdx lines 3 and 14-18 and
tutorials/partner-nodes/topaz/topaz-video-enhance.mdx lines 3 and 14-18. In
tutorials/partner-nodes/veo/overview.mdx lines 3, 10, and 14-19, use
parentheses, separate sentences, and colons respectively; make the listed colon,
sentence-splitting, and colon replacements in
tutorials/partner-nodes/veo/veo-2-0.mdx lines 2, 10, and 14-16, and
tutorials/partner-nodes/veo/veo-3-1.mdx lines 2-3, 14-17, 24, and 33.
Source: Coding guidelines
This was referenced Oct 14, 2026
Resolve conflicts against current Partner Models nav (Image/Video/Audio/3D/LLMs): - docs.json: keep main structure; register PR partner tutorials under the matching categories (ElevenLabs, HitPaw, Magnific, PixVerse, Quiver, Veo, WaveSpeed, plus additive Vidu/MiniMax/Topaz pages). EN-only pages are registered in English nav only. Add flat→overview redirects from the PR. - grok-video.mdx: keep main's Grok Imagine Video page (full rewrite with workflows/examples). Fold in PR additive notes (motion graphics / timing). - Drop PR-only grok/overview.mdx and grok-imagine.mdx (superseded by main's grok-overview and grok-image*). Fold ~4s / style notes into grok-image.mdx. Rebase onto main would have re-conflicted docs.json on multiple commits; merged main instead.
Member
|
Status check: this branch currently has merge conflicts with |
Salvage partner-node tutorials still missing on main (ElevenLabs, HitPaw, Magnific, PixVerse, Quiver, Veo, WaveSpeed, plus MiniMax/Vidu/Topaz hubs). Keep main's Grok pages and model-specific Topaz docs; drop superseded topaz-image/topaz-video-enhance. Register new pages in EN Partner Nodes nav and add overview redirects from the prior restructure.
Contributor
Preview approval requiredThis pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit |
Copy EN pages into locale trees and sync translationSourceHash so the i18n sync check sees matching adds (fork PRs cannot post the reminder comment when translations are missing). Real translation can follow via the automated workflow.
Point zh/ja/ko partner-node stubs at /snippets/{lang}/... so
validate-links accepts them as locale-aware imports.
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
Adds tutorial documentation for all P0 partner-node providers under
tutorials/partner-nodes/. Each page follows the existing Seedance 2.0 format with overview, key capabilities, and available workflow cards.New pages (11 files)
partner-nodes/elevenlabs/elevenlabs.mdxpartner-nodes/grok/grok.mdxpartner-nodes/vidu/vidu.mdxpartner-nodes/minimax/minimax.mdxpartner-nodes/magnific/magnific.mdxpartner-nodes/pixverse/pixverse.mdxpartner-nodes/quiver/quiver.mdxpartner-nodes/veo/veo.mdxpartner-nodes/topaz/topaz.mdxpartner-nodes/hitpaw/hitpaw.mdxpartner-nodes/wavespeed/wavespeed.mdxOther changes
docs.json— registered all 11 new pages under en/zh/ja navigation sections, inserted alphabeticallyFormat
Each page follows the Seedance 2.0 format:
CardGroup cols={2}(Cloud Run + Download JSON)