Skip to content

Commit fc7bcae

Browse files
committed
Add overview
Signed-off-by: Ben Sherman <[email protected]>
1 parent 99851c7 commit fc7bcae

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/workflow.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,13 @@
22

33
# Workflows
44

5-
In Nextflow, a **workflow** is a function that is specialized for composing {ref}`processes <process-page>` and dataflow logic.
5+
In Nextflow, a **workflow** is a function that is specialized for composing {ref}`processes <process-page>` and dataflow logic:
66

7-
See {ref}`syntax-workflow` for a full description of the workflow syntax.
7+
- An [entry workflow](#entry-workflow) is the entrypoint of a pipeline. It can take [parameters](#parameters) as inputs using the `params` block, and it can publish [outputs](#outputs) using the `output` block.
88

9-
:::{note}
10-
Workflows were introduced in DSL2. If you are still using DSL1, see {ref}`dsl1-page` for more information about how to migrate your Nextflow pipelines to DSL2.
11-
:::
9+
- A [named workflow](#named-workflows) is a workflow that can be called by other workflows. It can define its own inputs and outputs, which are called *takes* and *emits*.
10+
11+
- Both entry workflows and named workflows can contain [dataflow logic](#dataflow) such as calling processes, workflows, and channel operators.
1212

1313
## Entry workflow
1414

0 commit comments

Comments
 (0)