@@ -31,7 +31,7 @@ delivery layer part in another software (e.g. a shop system) as an extension.
3131- Publish a full, read-only snapshot of your live content to Redis in a so-called * Content Release*
3232- allows for * incremental publishing* ; so if a change is made, only the needed pages are re-rendered. This is
3333 * integrated with the Neos Content Cache* ; so cache flushings work correctly.
34- -Integration with Neos workspace publishing for automatic incremental
34+ - Integration with Neos workspace publishing for automatic incremental
3535 publishing to the Content Store
3636- Configurable Content Store format, decoupled from the internal representation in Neos.
3737- Extensibility: Enrich content releases with your custom data.
@@ -63,14 +63,14 @@ Copy the `pipelines_template.yml` file into your project and adjust it as needed
6363The following flow chart shows the rendering pipeline for creating a content release.
6464
6565```
66- ┌─────────────────────┐
67- │ Node Rendering │
68- ┌───────────┐ │ ┌─────────────┐ │ ┌───────────┐ ┌───────────┐ ┌───────────┐
69- │ Node │ │ │Orchestrator │ │ │ Release │ │Transfer to│ │ Atomic │
70- │Enumeration│────▶│ └─────────────┘ │────▶│Validation │────▶│ Target │────▶│ Switch │
71- └───────────┘ │┌────────┐ ┌────────┐│ └───────────┘ └───────────┘ └───────────┘
72- ││Renderer│ │Renderer││
73- └┴────────┴─┴────────┴┘
66+ ┌─────────────────────┐
67+ │ Node Rendering │
68+ ┌───────────┐ │ ┌─────────────┐ │ ┌───────────┐ ┌───────────┐ ┌───────────┐
69+ │ Node │ │ │Orchestrator │ │ │ Release │ │Transfer to│ │ Atomic │
70+ │Enumeration│────▶│ └─────────────┘ │────▶│Validation │────▶│ Target │────▶│ Switch │
71+ └───────────┘ │┌────────┐ ┌────────┐│ └───────────┘ └───────────┘ └───────────┘
72+ ││Renderer│ │Renderer││
73+ └┴────────┴─┴────────┴┘
7474```
7575
7676- At the beginning of every render, all nodes are ** enumerated** . The Node Enumeration contains all pages
0 commit comments