Adding blog for Stantt use case (windmill-labs#105)

hcourdent · web-flow · commit 720bc5e353ca · 2023-03-06T16:37:04.000+01:00
diff --git a/blog/2023-03-06-stantt-use-case/0-header.png b/blog/2023-03-06-stantt-use-case/0-header.png
diff --git a/blog/2023-03-06-stantt-use-case/index.md b/blog/2023-03-06-stantt-use-case/index.md
@@ -0,0 +1,42 @@
+---
+slug: stantt-case-study
+title: Windmill for Backend Batch Processing - Stantt Case Study
+authors: [jeffknorr]
+tags: [case study, testimonial, backend, windmill, stantt, ecommerce, python, scripts]
+image: ./0-header.png
+---
+
+
+This is a testimonial written by Windmill Community member [Jeffrey Knorr][jrk-linkedin], Director of Technology at [Stantt][stantt]. Thanks to him for his trust.
+
+
+<!--truncate-->
+
+
+> “Windmill helped us get visibility into our backend batch processing, leveraging the same custom Python scripts with their complex dependencies and requirements used before.”
+
+<br/>
+
+![Stantt Windmill use case](./0-header.png "Stantt Windmill testimonial")
+
+## What before windmill?
+
+**[Stantt][stantt]** is a menswear brand based in New York City and is currently in over 350 retail locations. We focus on finding the perfect fit for shirts, pants, suits etc, with 99 unique sizes and the ability to make and deliver custom fit and styled garments in only 7-10 days.
+
+To help track operations, it is necessary to **synchronize production details from our factory to our main database**. This is accomplished via background jobs scheduled by CRON every 2 hours using custom python libraries and logic.
+
+We previously had little monitoring, nor visibility on previous runs, and it was complex to change the logic or schedule.
+
+## How did Windmill help?
+
+We chose to self-host Windmill and use it for our backend batch processing. It allowed us to **keep working with essentially the same Python scripts and set-up we used before**, but with more visibility on scheduled jobs, error conditions, and script versioning. The platform also enables easier access, by more team members, through the web based UI versus a linux terminal.
+
+Our usage of Windmill is quite simple, but it is powerful and **mission critical**. We look forward to leveraging the Flows and Apps features of the platform in the future as well. The Windmill Team has been outstanding to work with and incredibly responsive to feature requests.
+
+## How to use Windmill?
+
+You can **[self-host](https://docs.windmill.dev/docs/advanced/self_host/#deployment)** it using a docker compose up, our go with the **[cloud app](https://app.windmill.dev/user/login)**.
+
+<!-- Links -->
+[jrk-linkedin]: https://www.linkedin.com/in/jeffreyknorr
+[stantt]: https://stantt.com/
diff --git a/blog/authors.yml b/blog/authors.yml
@@ -17,4 +17,9 @@ tfbecker:
   name: Felix Becker (community)
   title: Contributor from the Windmill Community
   url: https://github.com/tfbecker
-  image_url: https://github.com/tfbecker.png
+  image_url: https://github.com/tfbecker.png
+jeffknorr:
+  name: Jeffrey Knorr (community)
+  title: Contributor from the Windmill Community
+  url: https://github.com/JeffKnorr
+  image_url: https://github.com/JeffKnorr.png
