I'm maybe oversimplifying a bit - I'm thinking about maybe dropping the content on get, nth, conj, into... the super-common ones, but maybe leaving in what I think are more esoteric functions/use cases (e.g. using pop and peek on a vector), and definitely hitting on idioms like "`contains?` probably isn't what you want for a vector, use some with a set"

Good observation, yes, I would prefer a brighter line between the tutorials (covering the basics) and the cookbooks (showing how to build more complex/advanced stuff).

Part of what I was supposed to be working on this period (July/August) was reviewing the ecosystem and tutorials sections and then dealing with cookbooks in the next period and language in the final period... but now you have me rethinking that...

Maybe I should do language first, then tutorials, then cookbooks?

I've been pretty distracted this month -- my mum, mentioned in a couple of my long-term funding update posts, passed away early in July (on my birthday!) and I've been dealing with that on and off (in England, 5,500 miles away) most of this month. Her funeral was Wednesday last week and I think everything is squared away with her husband at this point (he's wreck -- worse than me).

I'm sorry to hear that - I don't want to be a distraction/disturbance to handling important stuff.

Nah, it's all handled at this point. Life must go on.

Sounds like I might need to add some more guidelines for contribution... I'll create an issue for that...

https://github.com/clojure-doc/clojure-doc.github.io/issues/52 -- thoughts @U013JFLRFS8?

I guess two factors come to mind immediately with ordering sections: how rapidly sections will evolve, and how much they're already covered - tutorials will probably be fairly static (the fundamentals aren't going to change very often), but there are also probably tens to hundreds of tutorials, where there might be less extant material that's trying to aggregate ecosystem, and new libraries are releasing daily. So maybe (just a proposal) ecosystem is a good first hit, and that might trigger library authors to contribute. Then some more 'static' content, and the occasional 'did anything big change?' on ecosystem.

I like the guidelines listed in that issue, I feel like it draws some nice lines to facilitate wider contribution without as much burden on you for "where should I put this?" and similar

Ecosystems has been a bit of a graveyard, unfortunately. The main elements were java.jdbc docs (a library long-since superseded), core.typed (outdated), and various editor guides (also outdated). A lot of it has been deleted since it was so outdated. I'd love to see people contribute but... Best I can do is point to http://clojure.org material and Practicalli both of which have better coverage and links.

You're right about a lot of competing tutorials. I'd like to be able to point to the best of them online and only provide somewhat novel material on http://clojure-doc.org. I think the cookbooks section is the area that is the most unique.

The language section is mostly just basics and somewhat duplicated elsewhere (although I haven't reviewed it yet). But it does have the advantage of interactive examples via Klipse 🙂

I agree about the cookbooks - I have the 'Clojure Cookbook' book (along with way too many other Clojure books), and a lot of the recipes are about using libraries (not a complaint, just an observation). I like the idea of capturing the idioms and common questions (why does any? exist? why is there doall and dorun and doseq and run!?)

Yes! The things that tutorials rarely cover 🙂

I have those things in a file called 'blog ideas', but I definitely think putting them somewhere that's central and combined with lots of other info can maybe make it another good reference site.

I could add a section called "Bob's Blog" 🙂

oh, I prefer it being "community docs"

you've got my brain brewing now... I wonder if those sorts of things would fit into an "FAQ", but I guess that would lead to http://ask.clojure.org.... although maybe summarizing some of the conversation threads would make them more palatable

that almost certainly needs some hammock time - I'll work on the data structures cookbook before worrying too much about trying to add new stuff