From 21da4fbef9762b2448a3b3513e0dd58d1355781a Mon Sep 17 00:00:00 2001
From: jamesread <contact@jread.com>
Date: Thu, 22 Jun 2023 15:50:26 -1000
Subject: [PATCH] Found a new purpose

---
 _includes/features.htm | 21 ---------------------
 index.md               | 40 +++++++++++++++++++++++++++++++++++++++-
 2 files changed, 39 insertions(+), 22 deletions(-)
 delete mode 100644 _includes/features.htm

diff --git a/_includes/features.htm b/_includes/features.htm
deleted file mode 100644
index 2322741..0000000
--- a/_includes/features.htm
+++ /dev/null
@@ -1,21 +0,0 @@
-<h3>Easy to understand, to use, to maintain</h3>
-<p markdown = "1">Upsilon has been improved over the years to make it easier, and is motivated to get even easier, as so many other orchestrators take hours, days and weeks to understand, use and maintain.</p>
-
-<h3>Distributed, with a fault tolerant, very lightweight control plane</h3>
-<p markdown = "1">Execute commands on different servers, and store results in a central database. The results are accessible from the [upsilon-web interface](upsilon-web), or via the command line client.</p>
-
-<h3>Lightweight to start, incredibly easy to scale</h3>
-<p markdown = "1">Happily runs on a raspberry Pi, a little laptop, homelab servers, or theoretically thousands of machines.</p>
-
-<h3>Autoconfiguration</h3>
-<p markdown = "1">The services that make up upsilon all try to rely on autodiscovery whenever possible, meaning that most services don't need any manual configuration, or very little. </p>
-
-<h3>Use with scripts and commands you already have</h3>
-<p markdown = "1">Scripts, shell commands - execute whatever you need with no changed need to work with Upsilon.</p>
-
-<h3>Use a Configuration as Code approach</h3>
-<p markdown = "1">Use Modern YAML configuration syntax, with built-in support for pulling updates from Git.</p>
-
-<h3>SQL database</h3>
-<p markdown = "1">Upsilon's use of SQL is very lightweight, and would likely work with any SQL database. MySQL is the only one supported at the moment.</p>
-
diff --git a/index.md b/index.md
index ecdb69d..1e33fab 100644
--- a/index.md
+++ b/index.md
@@ -4,7 +4,45 @@ hideTitle: true
 title: Homepage
 ---
 
-{% include features.htm %}
+# Use cases
+
+Easily orchestrate and run processes (scripts or shell commands) in an identical way, across several machines.
+
+* Easy to use as a replacement for traditional services
+  * eg: Backup Scripts that run at a specific time of day
+  * eg: Monitoring Scripts that run every 30 minutes
+  * eg: Trigger a complex command to run when an admin starts it
+  * eg: Trigger a download, picking the first available server to use
+  * eg: Apply the standard build scripts after a new server has been deployed, and keep them up to date.
+* Build up complex systems, workfloes and pipelines that are way more than the sum of their parts
+  * eg: CI/CD systems
+  * eg: Data Science workflows
+  * eg: Infrastructure application data monitoring processes
+
+# Design principles
+
+## Easy to understand, to use, to maintain
+Upsilon has been improved over the years to make it easier, and is motivated to get even easier, as so many other orchestrators take hours, days and weeks to understand, use and maintain.
+
+## Low effort and resources needed to get started, incredibly easy to scale
+Happily runs on a raspberry Pi, a little laptop, homelab servers, or theoretically thousands of machines.
+
+## The control plane is fault tolerant
+The control plane is made up of 3 components - a message queue (rabbitmq), a database (MySQL), and a microservice (upsilon-custodian) that saves things from the message queue to the database). If any of those components go down, the other services will gracefully buffer anything in progress, and resume when the services come back.
+
+## Use with scripts and commands you already have
+Scripts, shell commands - execute whatever you need with no changed need to work with Upsilon.
+
+## Autoconfiguration
+The services that make up upsilon all try to rely on autodiscovery whenever possible, meaning that most services don't need any manual configuration, or very little.
+
+## Built for a Configuration as Code approach
+Use Modern YAML configuration syntax, with built-in support for pulling updates from Git.
+
+## Easy to backup
+All persistent configuration is just a YAML text file, and Upsilon has builtin support for pulling this from a standard Git repository.
+
+All persistent data is stored in a MySQL database, and there are about 7 trillion standard tools available to backup a MySQL database already well tested and well used.
 
 ---