Documentation

[danielsz]

Typically, learning about the project means reading the README and studying the examples.

What kind of documentation effort do we want to undertake? What can we realistically achieve?
Would a Wiki fill in a need?

The discussion is open to everyone, especially new users since they know best about how smooth or how rugged their approach was. As long as the memory of your pain is alive, your opinion will matter more. Even if you don't intend to contribute to a documentation effort, please feel free to tell your experience on this thread.

[coyotespike]

I'll jump in. I've built a couple of full-fledged apps with Leiningen, re-frame, etc. Since I'd really like to use Boot, it seems System is the way to go.

For me, I'm figuring out what System is and how it works - while trying to distinguish my confusions about Boot from my confusions about System.

A comparison of how project.clj starts a web server (where the web server can access a database and so on), with how System starts a web server, might be helpful.

My picture of the Leiningen way is "Leiningen uses project.clj to start a web server, which goes to main and opens the html file it finds there, and then our ClojureScript can go live there."

By contrast, System seems to declare the server and database and other components upfront. Because they can be dynamically controlled piece by piece, the whole things seems more like a verb than a noun. It's a process, not a thing.

Hope any of that helps.