The library is not intended for doing it. It allows to automate anything, for example e-commerce workflows, by encapsulating work in custom stages. It’s just a

The library is not intended for doing it. It allows to automate anything, for example e-commerce workflows, by encapsulating work in custom stages. It’s just a pipeline. The major “selling point” is that the pipelines (workflows) can be written in an easily understandable xml so that even non developers can mantain or edit them. Imagine an ecommerce (or any web application) written for a customer which includes some workflows which runs automatically (or triggered manually). The customer can edit, refine or mantain them by just modifying the pipeline configuration using a reasonable xml (but you can even build a node-base editor, if you want, which produces the xml and configures the pipeline). The AI content generation is just an example usecase on which I’ve made an experimental website (with some custom stages for AI that i’ve developed privately for now), but pipeflow doesn’t provide any core stage for doing that.