The Elm dev(s?) really need to fix the Architecture Tutorial and write a proper language handbook.
Right now, the bad docs are pretty off-putting to someone coming to the language.
It's a shame, really, because I think Elm is great.
I wish Evan allowed others to contribute to the official documentation. Right now Elm feels more like Evan's personal project than a project that is owned by the community.
Other then that, the community has done a good job of writing up documentation, and Richard Feldman is working on a proper book.
While elm-lang/navigation and evancz/url-parser get you 80% there, the remaining 20% cause a lot of pain.
I am very optimistic that in the coming months this situation is going to improve tremendously. If we all share more knowledge, tutorials, guides, the whole community will win!
I'm really rooting for Elm, I so prefer it to TypeScript and alternatives.
Sadly, no time on my hands to get involved.
I think the docs could use a chapter on functional programming and how that works in the land of ML languages, and perhaps a few walk through examples of some simple, but not overly simplistic, apps.
So far though I think the language is pretty interesting, but I've yet to do anything really fancy with it.
I'll be back in another few months, hope the situation improves.
Also, I could totally make a case for Elm at work right now... if it had usable documentation.