I think some of the other sites you linked are great examples.
So move the elevator pitch for Clojurescript to the top of the page. "Clojurescript is a compiler for Clojure that targets Javascript" is an explanation technically, but you might want to write something more about why you'd use Clojurescript.
For example, the first words you see on Elm's site are "A delightful language for reliable webapps.". So you'd use Elm to make webapps, and it should be enjoyable to use. Ruby says "A dynamic, open source programming language with a focus on simplicity and productivity. It has an elegant syntax that is natural to read and easy to write." Note how none of these focus on how the language is implemented; most users don't care. The language could have a compiler written in Brainfuck to compile to Lua, but that's all under the hood.
So write a sentence or two about why a programmer would choose Clojurescript for a task. What kinds of things does Clojurescript do well?
Also, I'd suggest motivating the snippets the way Elm does, where the user isn't left guessing why a snippet is there. It's explicitly explained.
So move the elevator pitch for Clojurescript to the top of the page. "Clojurescript is a compiler for Clojure that targets Javascript" is an explanation technically, but you might want to write something more about why you'd use Clojurescript.
For example, the first words you see on Elm's site are "A delightful language for reliable webapps.". So you'd use Elm to make webapps, and it should be enjoyable to use. Ruby says "A dynamic, open source programming language with a focus on simplicity and productivity. It has an elegant syntax that is natural to read and easy to write." Note how none of these focus on how the language is implemented; most users don't care. The language could have a compiler written in Brainfuck to compile to Lua, but that's all under the hood.
So write a sentence or two about why a programmer would choose Clojurescript for a task. What kinds of things does Clojurescript do well?
Also, I'd suggest motivating the snippets the way Elm does, where the user isn't left guessing why a snippet is there. It's explicitly explained.