⚡ Generative Microsites — New Zealand
Standalone research artifacts from the pipeline, presented as a regional archive hub rather than a bare list of links.
0 articles — nzNew Zealand archive reproduction route
A portable hand-off for reproducing research later
The New Zealand route is organised around portability: what a reader should capture now so a setup can be reproduced after an interrupted session or on another machine. This is an editorial use case, not a statement about New Zealand connectivity, hardware or vendors. The regional URL remains intact while the page supplies a distinct research function.
Capture the environment before changing it
Write down the operating system, installation type, ComfyUI revision, Python and PyTorch versions, accelerator, driver and available memory. The official troubleshooting guide asks for this class of system information because it helps distinguish a core issue from a custom-node or environment issue. Keep the record beside the workflow, not only in a browser tab.
Package dependencies with the graph
A JSON workflow is compact, but it does not by itself supply every model or custom node. Use the workflow library entry to enumerate those dependencies and their sources. If a dependency cannot be verified, mark it as unresolved; do not substitute a similarly named package and call the run equivalent.
Resume from a recorded checkpoint
After installation, run the smallest validated graph before adding optional nodes. Save the first successful output, console log and workflow revision. If memory becomes the constraint, consult the benchmark hub and official troubleshooting link rather than guessing a memory-saving flag from a result generated under different conditions.
Exit checklist
- Capture environment versions before modification.
- Store the workflow and dependency record together.
- Mark unresolved assets explicitly.
- Keep the first successful output and log as the baseline.
Localized microsites from the 42.uk generative pipeline — standalone research artifacts adapted for regional context.
Each locale route is a stable archive hub for readers who discover the microsite catalogue through a country or language-specific path. It explains what this section covers, keeps the canonical route crawlable, and provides a clean handoff either to the live localized entries below or back to the broader English archive.
When the article count is small, that reflects the actual number of published microsites for this region at the moment. The page is still useful as a navigational landing point because the URL stays constant while the localized catalogue grows.
For readers and crawlers, the key distinction is that /sites/ collects self-contained microsites with their own layout and workflow framing, while /blogs/ remains the broader research feed. Even when the live count is low, this page still acts as the stable regional entry point for discovery, future additions, and clean internal linking.
No microsites are published for this locale yet, but the route still matters because it tells readers and crawlers that the regional archive is intentional rather than broken. The page keeps a stable home for future localized releases, and it documents how this section fits into the wider 42.uk publishing structure today.
Use this regional hub when you want the country-specific path to stay consistent over time. Use the English microsite index for the fuller current catalogue, and use the main blog archive when you need the broader research corpus beyond standalone microsite builds.