There are two changes I’d like to propose:
Change the tag line to “A lifesaver for templating YAML”
The focus on “templating YAML” is inspired by a suggestion by @singpolyma previously in Idea for a slight rebranding change. Most people who use Dhall and put up with its unfamiliar syntax do so because they need to template configuration files in a way that isn’t terrible.
In other words, they don’t need to replace YAML in general (because sometimes TOML would be a better alternative for some YAML configuration files). They very specifically want to replace their existing YAML template solution (such as Helm).
This change also includes the metaphor of a “lifesaver” instead of saying “non-repetitive alternative to …”. I propose this because:
- “Lifesaver” suggests a metaphor that people are “drowning” in bad YAML templates and need a lifesaver to stay afloat
- People culturally associate a “lifesaver” with “minimum required level of safety” which promotes the perception that the safety assurances Dhall provides are non-negotiable
- The tagline puts words into people’s mouths by suggesting as literally as possible how they should evangelize Dhall to each other (e.g. “Dhall was a lifesaver for us”)
- It fits with the nautical theme of the Kubernetes ecosystem (which I am targeting as a mainstream entrypoint by building towards Dhall as a Helm replacement)
Change the “Human Friendly” section of the dhall-lang.org to “Safe templates” or something similar
The idea is that we want to illustrate how Dhall’s templates always generate correct-by-construction output (i.e. it is not templating