docs: rebuild English beginner path and concepts navigation

basic-concepts/custom-nodes.mdx

@@ -4,15 +4,15 @@ description: "Custom nodes in ComfyUI: how they differ from Comfy Core nodes, pl
 icon: "window-maximize"
 ---
 
-## About Custom Nodes
+## When do you need custom nodes?
 
-After installing ComfyUI, you'll discover that it includes many built-in nodes. These native nodes are called **Comfy Core** nodes, which are officially maintained by ComfyUI.
+ComfyUI already includes built-in nodes. A **custom node** is an extra node supplied by a community package. You only need to install one when a workflow requires it or when you want a feature it provides. A missing-model warning is different: it asks for a model file, not a custom node. Use [Fix a workflow that will not run](/get_started/fix-a-workflow) to tell the warnings apart.
 
-Additionally, there are numerous [**custom nodes**](https://registry.comfy.org) created by various authors from the ComfyUI community. These custom nodes bring extensive functionality to ComfyUI, greatly expanding its capabilities and feature boundaries.
+Find community packages in the [Comfy Registry](https://registry.comfy.org). If a package appears in an imported workflow, [ComfyUI Manager](/manager/overview) can help install and manage it.
 
-In this guide, we'll cover various operations related to custom nodes, including installation, updates, disabling, uninstalling, and dependency installation.
+The rest of this page covers installation, updates, disabling, uninstalling, and software dependencies.
 
-Anyone can develop their own custom extensions for ComfyUI and share them with others. You can find many community custom nodes [here](https://registry.comfy.org). If you want to develop your own custom nodes, visit the section below to get started:
+If you want to develop a custom node, start with the developer guide:
 
 <Card title="Start Developing Custom Nodes" icon="link" href="/custom-nodes/overview">
   Learn how to start developing a custom node
@@ -336,4 +336,3 @@ If you have some development capabilities, please start with the documentation b
   Learn how to start developing a custom node
 </Card>
 
-

basic-concepts/dependencies.mdx

@@ -1,24 +1,23 @@
 ---
 title: "Dependencies"
-description: "Understand dependencies in ComfyUI"
+description: "Understand the files and software a shared ComfyUI workflow needs, with advanced Python troubleshooting."
 icon: "file"
 ---
 
 {/*
 description: "Understand asset and software dependencies in ComfyUI"
 */}
 
-## A workflow file depends on other files
+## What a shared workflow may need
 
-We often obtain various workflow files from the community, but frequently find that the workflow cannot run directly after loading. This is because a workflow file depends on other files besides the workflow itself, such as media asset inputs, models, custom nodes, related Python dependencies, etc.
-ComfyUI workflows can only run normally when all relevant dependencies are satisfied.
+A workflow file stores connected steps and settings. It does not include every file or extra node used by its creator. If a shared workflow will not run, check for these requirements first:
 
-ComfyUI workflow dependencies mainly fall into the following categories:
+- **Input files**: Images, video, or audio the workflow expects you to provide.
+- **Local models**: Model files that must be downloaded and selected.
+- **Custom nodes**: Extra node packages that are not installed in your ComfyUI.
+- **Account and credits**: Requirements for hosted Partner Nodes or Comfy Cloud nodes.
 
-- Assets (media files including audio, video, images, and other inputs)
-- Custom nodes
-- Python dependencies
-- Models (such as Stable Diffusion models, etc.)
+Start with [Fix a workflow that will not run](/get_started/fix-a-workflow) to identify the warning. The rest of this page explains these requirements and the Python packages needed by custom nodes. Most users do not need to manage Python packages directly.
 
 ## Assets
 
@@ -145,4 +144,4 @@ This allows multiple ComfyUI instances to share the same model library, reducing
 
 An advanced application like ComfyUI also has **_software dependencies_**. These are libraries of programming code and data that are required for the application to run. Custom nodes are examples of software dependencies. On an even more fundamental level, the Python programming environment is the ultimate dependency for ComfyUI. The correct version of Python is required to run a particular version of ComfyUI. Updates to Python, ComfyUI, and custom nodes can all be handled from the **ComfyUI Manager** window.
 
-![ComfyUI Custom Nodes Manager](/images/concepts/core-concepts_dependecies_custom-nodes-manager.png)
+![ComfyUI Custom Nodes Manager](/images/concepts/core-concepts_dependecies_custom-nodes-manager.png)

basic-concepts/links.mdx

@@ -6,7 +6,9 @@ icon: "share-nodes"
 
 ## Links connect nodes
 
-In ComfyUI, the lines or curves drawn between nodes are called **_links_** (also referred to as **_connections_** or wires). They carry data from one node's output to another node's input, defining the flow of your workflow.
+The lines between nodes are **links**, also called connections. They carry the output of one step into the input of another. Follow them to see how a prompt, model, or image reaches the final output. For a first tour of the canvas, see [How ComfyUI works](/get_started/how-comfyui-works).
+
+The sections below explain display styles, reroutes, and connection types in more detail.
 
 Links can be displayed in several visual styles: curves, right angles, straight lines, or hidden entirely.
 

basic-concepts/models.mdx

@@ -8,7 +8,11 @@ import ExternalModels from "/snippets/install/add-external-models.mdx"
 
 ## Models in plain terms
 
-In ComfyUI, **models** are the weight files that actually run your workflow. They include **checkpoints**, **VAEs**, **LoRAs**, **ControlNets**, and upscalers. The app install is small. These files are **not** included by default. You usually **download them from the web**, place them under `ComfyUI/models/` (or follow a template’s prompts), then choose the file in the right **loader node** (on the canvas, these often appear as nodes whose names start with **Load**).
+A **local model** is a file ComfyUI loads to generate or transform content on your device. A template can tell you which files it needs, but the workflow itself does not contain those large files. If ComfyUI shows a missing-model prompt, follow its file name and folder instructions. See [Fix a workflow that will not run](/get_started/fix-a-workflow) if you are unsure what is missing.
+
+Not every workflow uses a local model. **Partner Nodes** call hosted models and use credits instead of a model download. [Compare where workflows run](/get_started/where-work-runs).
+
+Local model files include checkpoints, VAEs, LoRAs, ControlNets, and upscalers. You usually place them under `ComfyUI/models/` (or follow a template's prompt), then choose each file in the matching loader node. The sections below cover model compatibility and manual setup in more detail.
 
 ### Supported models in ComfyUI
 

basic-concepts/nodes.mdx

@@ -1,25 +1,26 @@
 ---
 title: "Nodes"
-description: "Nodes are ComfyUI's fundamental building blocks: independent Comfy Core or custom modules you connect with links to assemble complex workflows."
+description: "Learn what ComfyUI nodes do, how to read their inputs and outputs, and what common node states mean."
 icon: "circle"
 ---
 
-In ComfyUI, nodes are the fundamental building blocks for executing tasks. Each node is an independently built module, whether it's a **Comfy Core** node or a **Custom Node**, with its own unique functionality. Nodes connect to each other through links, allowing us to build complex functionality like assembling LEGO blocks.
-The combinations of different nodes create the unlimited possibilities of ComfyUI.
+A **node** is a box that performs one step in a workflow. One node might load a model, another might read your text prompt, and another might save the finished image. Connect nodes to pass results between those steps.
+
+Start with a [workflow template](/interface/features/template) to see nodes working together. You can run a template before learning how to add or connect nodes yourself.
+
+For a short explanation of how nodes fit into a complete workflow, read [How ComfyUI works](/get_started/how-comfyui-works). The sections below cover node states, connections, controls, and menus in more detail.
 
 ![Comfy Core K-Sampler Node](/images/comfy_core/sampling/k_sampler.png)
 
-For example, in the K-Sampler node, you can see it has multiple inputs and outputs, and also includes multiple parameter settings. These parameters determine the logic of node execution. Behind each node is well-written Python logic, allowing you to achieve corresponding functionality without having to write code yourself.
+In the KSampler example, connections on the left provide inputs, settings inside the box control generation, and the connection on the right passes its result onward. You can change settings without writing code.
 
 <Note>
 ComfyUI is under active development, so some details here may be outdated. If you spot something that's changed, feel free to [help us update the docs](https://github.com/Comfy-Org/docs).
 </Note>
 
 ## Nodes perform operations
 
-In computer science, a **_node_** is a container for information, usually including programmed instructions to perform some task. Nodes almost never exist in isolation, they're almost always connected to other nodes in a networked graph. In ComfyUI, nodes take the visual form of boxes that are connected to each other.
-
-ComfyUI nodes are usually **_function operators_**. This means that they operate on some data to perform a function. A function is a process that accepts input data, performs some operation on it, and produces output data. In other words, nodes do some work, contributing to the completion of a task such as generating an image. So ComfyUI nodes almost always have at least one input or output, and usually have multiple inputs and outputs.
+Most nodes accept input, do a job, and produce output. A **Load Checkpoint** node, for example, loads a model that other nodes can use. A **Save Image** node receives the final image and saves it. The connecting lines are called [links](/basic-concepts/links).
 
 ## Different Node States
 

basic-concepts/properties.mdx

@@ -1,19 +1,22 @@
 ---
-title: "Properties"
-description: "Master Comfy properties with our official development documentation. Understand core concepts to build custom nodes efficiently. Read the full guide now."
-icon: "circle"
+title: "Node settings and inputs"
+description: "Learn which values you can change inside a ComfyUI node and when a value comes from another node."
+sidebarTitle: "Node settings and inputs"
+icon: "sliders"
 ---
 
-## Nodes are containers for properties
+A node has controls you can change, such as a prompt, image size, or number of generation steps. These values are often called **settings**, **parameters**, or **properties**. You do not need to learn those names before running a [template](/interface/features/template).
 
-Nodes usually have **_properties_**. Also known as **_parameters_** or **_attributes_**, node properties are variables that can be changed. Some properties can be adjusted manually by the user, using a data entry field called a **_widget_**. Other properties can be driven automatically by other nodes connected to the property **_input slot_** or port. Usually, a property can be converted from widget to input and vice versa, allowing users to control property values manually or automatically.
+![Node settings](/images/concepts/core-concepts_properties.png)
 
-Properties can take many forms and hold many different types of information. For example, a **Load Checkpoint** node has a single property:  the file path to the generative model checkpoint file. A **KSampler** node has multiple properties such as the number of sampling **steps**, **CFG** scale, **sampler\_name**, etc.
+## Change a setting inside a node
 
-![node properties](/images/concepts/core-concepts_properties.png)
+Find the field in the node, enter a value, and run the workflow again. For example, a text input holds your prompt. A **Load Checkpoint** node has a selector for a local model file. A **KSampler** node has settings such as steps and sampling method.
 
-## Data types
+## When a value comes from another node
 
-Information can come in many different forms, called **_data types_**. For example, alphanumeric text is known as a **_string_**, a whole number is an **_integer_**, and a number with a decimal point is known as a **_floating point_** number or **_float_**. New data types are always being added to ComfyUI.
+Some controls can instead receive their value through a connection. In that case, follow the line to the node that supplies the input and change it there. The connection points are often called **ports** or **slots**. See [Links](/basic-concepts/links) for how connections work.
 
-ComfyUI is written in the Python scripting language, which is very forgiving about data types. By contrast, the ComfyUI environment is very **_strongly typed_**. This means that different data types can’t be mixed up. For example, we can’t connect an image output to an integer input. This is a huge benefit to users, guiding them to proper workflow construction and preventing program errors.
+Connections accept specific kinds of data. An image output, for example, cannot feed a number input. If two ports will not connect, check their input and output labels and types.
+
+For a simpler introduction to the whole canvas, start with [How ComfyUI works](/get_started/how-comfyui-works).

basic-concepts/workflow.mdx

@@ -8,6 +8,8 @@ icon: "diagram-project"
 
 A workflow is a set of steps that tells ComfyUI how to create something.
 
+If you are new to the canvas, start with [How ComfyUI works](/get_started/how-comfyui-works). This page is a more detailed reference for reading, running, saving, and sharing workflows.
+
 You can think of a workflow like a recipe:
 
 - The recipe is the workflow.
@@ -76,7 +78,7 @@ If a node is missing, has an error, or does not receive the data it needs, Comfy
 
 To get started, open a built-in workflow template from **Workflow** → **Browse Workflow Templates**. Templates provide complete examples that you can run and edit.
 
-Templates use Core nodes included with ComfyUI. They also prompt you to download any required models.
+Some templates use only nodes included with ComfyUI. Others come from custom nodes and may require extra installation. ComfyUI also prompts you when a template needs model files you do not have.
 
 The community has created many custom nodes that add more capabilities. Learn more in [Custom Nodes](/basic-concepts/custom-nodes).
 

docs.json

@@ -28,6 +28,12 @@
                 "group": "Get Started",
                 "pages": [
                   "index",
+                  "get_started/start_here",
+                  "get_started/first_generation",
+                  "get_started/how-comfyui-works",
+                  "get_started/where-work-runs",
+                  "get_started/fix-a-workflow",
+                  "get_started/cloud",
                   {
                     "group": "Local (Self-Hosted)",
                     "icon": "download",
@@ -64,7 +70,6 @@
                       "installation/update_comfyui"
                     ]
                   },
-                  "get_started/cloud",
                   {
                     "group": "Install Custom Nodes",
                     "icon": "puzzle-piece",
@@ -87,8 +92,7 @@
                         ]
                       }
                     ]
-                  },
-                  "get_started/first_generation"
+                  }
                 ]
               },
               {
@@ -103,14 +107,14 @@
                 ]
               },
               {
-                "group": "Basic Concepts",
+                "group": "ComfyUI Reference",
                 "pages": [
                   "basic-concepts/workflow",
                   "basic-concepts/nodes",
-                  "basic-concepts/custom-nodes",
-                  "basic-concepts/properties",
-                  "basic-concepts/links",
                   "basic-concepts/models",
+                  "basic-concepts/links",
+                  "basic-concepts/properties",
+                  "basic-concepts/custom-nodes",
                   "basic-concepts/dependencies"
                 ]
               },

get_started/cloud.mdx

@@ -9,9 +9,13 @@ icon: "cloud"
   Click here to access ComfyUI Cloud directly
 </Card>
 
+<Note>
+Comfy Cloud is the full ComfyUI app in your browser. A **Comfy Cloud node** is one step in a workflow that uses Comfy's hosted GPUs. They are different ways to use cloud compute. See [Where a workflow runs](/get_started/where-work-runs).
+</Note>
+
 ## What is Comfy Cloud?
 
-ComfyUI Cloud is the cloud version of ComfyUI with the same features as the local version. Everything is pre-installed and ready to use.
+Comfy Cloud lets you use ComfyUI in a browser without installing the app on your computer. Choose a supported template to start. Available models and custom nodes can differ from a local installation.
 
 ### Key features