I also found clojure-doc.org accidentally, and was surprised it didn't show up in earlier searches, especially in the context of the high quality of the documentation.
I think merging the two resources (clojuredocs and clojure-doc) would greatly help (I'd be happy to help in this effort), and getting high profile links pointed to it (particularly on clojure.org itself) would make all the difference in adding to its visibility, regardless of the frequency of the updates to the site itself. On Thursday, February 28, 2013 12:06:46 AM UTC+6, Michael Klishin wrote: > > Started in October 2012, http://clojure-doc.org is a pretty extensive > community documentation effort. It covers Clojure, its ecosystem > and tools and has two key goals: > > * We produce beginner-friendly content > * It is dead easy to join and help > > Even though recently that hasn't been > as much activity as in the past, it is not abandoned and continues > to accumulate useful, beginner-friendly material. > > We constantly get praises from newcomers to Clojure who discover > clojure-doc.org. Unfortunately, it does not appear even in top 10 > in Google for "clojure docs" or "clojure documentation" and > many community members are not aware of it. > > In part it is less visible because we no longer actively post > progress reports. Things have settled down and most of changes > now are small edits and improvements all over the place. It is > a bit pointless to post progress reports more often than > once a month or so. > > So I'd like to start a discussion about what can be done about it. > The community (we have 40 contributors) has worked very hard > on clojure-doc.org and I'd like to see high profile resources > (namly clojure.org and leiningen.org) link to it. What would > it take to convince clojure.org maintainers to do so? > > There are still guides left ot be written (macros, gen-class), > but overall, I'd say there is no better source of freely available, > beginner-friendly, hackable (no Clojure CA, everything is developed > on GitHub [1], content is in Markdown) documentation. All it needs > is some linking and promotion love. > > One way to help would be to start a campaign such as Mozilla's > Promote JS [docs]. Unfortunately, unlike Mozilla key contributors > behind clojure-doc.org largely lack graphic and Web design skills, > so replicating that campaing is probably not an option. > > Do you have any ideas about how we can make clojure-doc.org more > visible? Do you know who can help with getting a link from clojure.org? > Do you think clojure-doc.org is not good enough to be the "blessed" > open source documentation resource? Please post your suggestions > and concerns. > > Improving CDS visibility will benefit the entire community plus all the > people who will join it in the future. Most of the work is already done, > it just needs to be promoted better. > > Thanks you. > > > 1. https://github.com/clojuredocs/cds > > -- > MK > > http://github.com/michaelklishin > http://twitter.com/michaelklishin > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
