+- no `sudo`
+- no package manager
+- no messing with system permissions
+- in short: no nonsense
+
+```bash
+curl https://webinstall.dev/webi | bash
+```
+
+This repository contains the primary and community-submitted packages for
+[webinstall.dev](https://webinstall.dev).
+
+# How webi works
+
+- Contacts official release APIs for download URLs
+- Selects the appropriate package version and archive format
+- Installs to `$HOME/.local/opt` or `$HOME/.local/bin`, as appropriate.
+- Updates `PATH` via `$HOME/.config/envman/PATH.env`
+- Symlinks or copies current selected version
+
+More technically:
+
+1. `<package>/releases.js` transforms the package's release API into a common
+ format
+ - (i.e. HTML, CSV, TAB, or JSON into a specific JSON format)
+ - common release APIs are in `_common/` (i.e. `_common/github.js`)
+2. `_webi/bootstrap.sh` is a template that exchanges system information for a
+ correct installer
+ - contructs a user agent with os, cpu, and utility info (i.e. `macos`,
+ `amd64`, can unpack `tar,zip,xz`)
+3. `_webi/template.sh` is the base installer template with common functions for
+ - checking versions
+ - downloading & unpacking
+ - updating PATH
+ - (re-)linking directories
+4. `<package>/install.sh` may provide functions to override `_webi/template.sh`
+5. Recap:
+ - `curl https://webinstall.dev/<pkg>` => `bootstrap-<pkg>.sh`
+ - `bash bootstrap-<pkg>.sh` =>
+ `https://webinstall.dev/api/installers/<pkg>@<ver>.sh?formats=zip,tar`
+ - `bash install-<pkg>.sh` => download, unpack, move, link, update PATH
+
+# Philosophy (for package authors / maintainers publishing with webi)
+
+- Should install to `$HOME/.local/opt/<package>-<version>` or `$HOME/.local/bin`