I have started a new github project https://github.com/deg/clojure-then-you-think. I'm using its Wiki as a place to write articles and docs. My immediate focus here is to deep-dive into some pain points that have tripped me up. I'll keep adding more, as time allows. But this should also include more general docs, and multiple viewpoints. I've opened up the Wiki so anyone can write to it. Please jump in!

🎉 that's awesome!

Thanks @jennifer . It would be great if you could add in an article capturing some of your getting-started lessons.

i definitely will! starred the repo and after i get through a bit of crunch i'm going to start writing again. this is one of my top todos. 🙂 i've been away from clojure for a bit cramming other things, but i'm excited to start back up again.

cool!

hey y'all

just got finished reading the document

i've been in charge of onboarding clojurescript developers @ my company and have gone through this process many times

will definitely want to contribute to this

The immediately obvious idea in my head was something along the lines of a yeoman generator from JS-land

that does precisely what your document suggests: asks you questions based on your problem domain, and spits out a boilerplate project based on your answers

this, in addition to (obviously), the documentation approach

yeoman, rails, react-starter-app. yup. a good starting place for those who want to get up and running quickly would be amazing. the time/energy expended between starting env setup to actually writing some code and learning cljs is much more massive than i had expected.

so happy this discussion is happening. it breaks down that barrier to getting hesitant folks to get started. yes, learning how to do the setup "by hand" is valuable and should be learned. it makes troubleshooting easier if you know what's under the hood. but if you want to show people the strength of what cljs and clojure are capable of there needs to be a path to get them there. encourages the crowd that doesn't have tons of free time but tons of curiosity.

ultimately what we want to sell people on is the productivity and developer-happiness improvements of building things with clojurescript

getting them doing that as soon as possible, with some pre-canned configurations, should be the goal

once we stick em' after that, they'll be a lot more inclined to learn how the configuration side of things goes - it should be an afterthought

my only concern would be people taking the pre-canned configs as gospel and never moving past that. somehow stressing that this is just a handful of ways to go about things would be important. the yeoman model probably helps reinforce that.

definitely, i think that that's something that could be stressed heavily in the documentation and certainly in a tool

just in writing

"hey heads up, we're gonna take care of this step for you, but once you get your feet wet, go take a look at the configuration in the [`project.clj`/`build.boot`]" -- and, additionally, to have the configs themselves documented in comments quite heavily, describing what everything is doing

ive owned for awhile and haven't done anything with it.

this project seems like the perfect candidate if im honest

@samueldev Sounds like you've been through this much more than me. Looking forward to seeing your ideas!