chris.dumas/comfyui-workflows
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refresh daily workflow review notes

Browse Source
This commit is contained in:
Morpheus
2026-08-20 20:07:50 +00:00
parent a84c26a5f5
commit 69f3c0f9c3
7 changed files with 67 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
optimized/notes/zimage.md
+11 -1
View File
@@ -6,19 +6,29 @@
## What to look for
- strong `text-to-image` workflows
- strong official `text-to-image` workflows
- reference and edit workflows
- outpaint / inpaint workflows
- high-quality upscaling or restoration-adjacent workflows
- any workflow that clearly beats a comparable `FLUX` path in practical image quality or simplicity
## Strong current source workflows
- `models/zimage/z-image-turbo-official-example/`
- `models/zimage/z-image-turbo-inpainting-community/`
- `models/zimage/z-image-turbo-controlnet-union-community/`
- `models/zimage/qujincheng-z-image-lora-facetailer/` for face-detail follow-up, not as a core generator
## Current heuristics
- Prefer real workflow assets over showcase pages.
- Favor workflows with clear node requirements and portable imports.
- Treat `Z-Image` as especially relevant for image-generation and image-edit categories, not video categories.
- Keep the official example as the clean text-to-image baseline, then compare the community inpaint and controlnet-union graphs against it for real edit gains.
- Treat facetailer-style graphs as post-pass helpers unless they prove they can stand alone.
## What still needs proof
- which `Z-Image` workflows are genuinely stronger than the best current `FLUX` image-generation paths
- whether `Z-Image` should become a category-master candidate for `text-to-image` or `image-edit`
- whether the inpaint or union-style community graph is the better maintained edit baseline on Chris's machine