> The tutorials do put too strong a focus on JSON in my opinion (Matt wrote them). I don't mean to start a fight between friends! :-) > But on the other hand

> The tutorials do put too strong a focus on JSON in my opinion (Matt wrote them). I don't mean to start a fight between friends! :-) > But on the other hand I think it's pretty important to understand that the Caddyfile _is_ an adapter to JSON and not the native config language. It's key to knowing how to debug and inspect how Caddy actually runs. Agreed. > I'm not sure I understand this point though, what are you trying to say here? You can definitely just download the caddy binary and run it wherever, you don't need to use a package manager. I'm not sure what this is trying to point to. Sorry, I mangled that with a run-on sentence, didn't I! What I mean is, I think more users are likely to want the package manager, systemd-configuration deal. The automatic-HTTPS thing is such a strong sell that I think a lot of people will seek to replace nginx just for that. I could totally be wrong here but this is where I think a sort of narrative document for Nginx users at least is perhaps worth it. Some of this is always going to be a challenge because Caddy is a fascinating, category-straddling project; you've made a product that is somewhere between a magical automatic appliance, a Golang web dev framework and a traditional configurable server, that avoids the downsides of all of those things as far as is really possible. Documenting that is definitely a unique challenge. I'm prattling on now but thank you again for Caddy; it really is a great contribution.