video1.0<iframe src="https://www.loom.com/embed/0ac77d6e259b48ef8adf684a3d099e5f" frameborder="0" width="2218" height="1663" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>16632218Loomhttps://www.loom.com16632218https://cdn.loom.com/sessions/thumbnails/0ac77d6e259b48ef8adf684a3d099e5f-00001.gif800.1333333333331Hey there! In this Loom, I'm introducing you to the Gitter repository workflow demo. It's a proof of concept for a soft-market texture that supports configurable workflows. I created this demo project as a learning exercise because multiple people came to me saying that it would be difficult for them to implement composable, configurable workflows where you can also stop and restart a workflow. The demo project contains an Elixir project and it implements an architecture that I described. The video walks you through an example workflow that I implemented as part of this proof of concept. The workflow is designed to process a document, and the application receives the document, creates a workflow, and executes the workflow. I explain the different steps in the workflow and how they work. The video also covers the architecture of the application, which is one big OTP application. I didn't use any database persistence in this case, but you could decide on what to use. The video also covers the workflow context, which is a simulation of the CRUD operations of workflows. The engine is one of the most important parts of this whole architecture. It receives a workflow and executes the flow. If you run this application, there are two mocks: the document produced and the customer server. The video is a great resource for anyone who wants to learn more about Gitter repository workflow demo.