
shite's job is to help me make my website (https://evalapply.org). Thus, shite's scope, (mis)feature set, polish will always be production-grade, where production is 'works on my machine(s)' :)

See the 'Concept' section in the README. Basically, 'multiproject' addresses my own specific requirements; viz. indie and hobby SaaS apps of my own; RAD for outcomes-driven customers (like me) who want long-lived, stable software; and to benefit from the Clojure ecosystem's creativity, reach, stewardship, and software stability. Polylith (https://polylith.gitbook.io/) is the (far) more sophisticated alternative to my approach.

This workshop aims to get your brain and fingers accustomed to just enough of the Clojure programming language to start doing useful things with it. In other words, 'What could one do with just a little bit of Clojure?'.

Sean's original 'User Manager' example project and its variants (including this one), aim to demystify 'How to construct a Clojure web application using only libraries?'. 'Composition over inheritance', 'Libraries over frameworks', and 'Data orientation' feature prominently in the Clojure world's canonical mental model of programming, including programming the web. Absent some of these key intuitions, even experienced developers who are new to Clojure tend to struggle to build apps using libraries. The 'User Manager' collective of demos aim to address this specific challenge.
How to support
GOTO evalapply.org && do that 'like, share, subscribe, sponsor' thing :)
A small brief about your project
Typically, I release software for programmer education and instruction, developer workflow / experience ('DevX'), and personal software for fun and utility (see: https://justforfunnoreally.dev and 'houseplant programming': https://www.hannahilea.com/blog/houseplant-programming .
One FOSS maintainer lesson for your younger self
Be license-savvy. Pick one that protects your own time, interests, and goals as maintainer, first and foremost.
Why do you do it? Why do you bother maintaining a FOSS project?
'Learn Generously' is the guiding principle behind everything I open source to the Wild Wild Web.
If your repo had a theme song, what would it be?
Why one? Here are one zero songs... Because the lone open source 'artist's way' feels like any (or all) of that in any given week.
Which file in your project would you most like to set on fire?
templating.sh in shite, because of this gawdawful case statement: https://github.com/adityaathalye/shite/blob/6d30eb1df29d65945e445287798ca1ce4c987a51/bin/templating.sh#L188.
What's your open-source villain origin story?
Small crimes, er, commits led to bigger commits... and now there's not going back.
If you had to use one emoji to convey what it is like to be a FOSS maintainer, what would it be?
☯️