On Fri, Dec 10, 2010 at 5:07 PM, Alec Battles <alec.batt...@gmail.com> wrote: >> I strongly suggest improving the docs on the >> Clojure wiki instead; that way errors can be fixed by the community. > > Why does the one preclude the other? > > Also, if people aren't going to blog about Clojure, what future does it have?
Sorry; I'm not saying don't blog about Clojure; I'm saying you should consider whether what you want to write indicates a deficiency in the official documentation. If there's something lacking in the documentation, it's much more profitable to everyone to improve it. For instance, it sounds like it's confusing for Mac users to decide which Emacs to use, so it sounds like the swank readme should have some advice about that. This is something I didn't consider as an Ubuntu user where we don't have that problem. If you just put it on your blog, then you're the only one who can fix it, and experience has shown that this generally does not happen. Documentation is a project and requires maintenance just like code. The context I'm coming from is the fact that the single-most-common issue people ask about on the swank-clojure mailing list is people finding confusing blog posts, most of which are largely out-of-date by the time they've gained enough google juice to make the front page of search results. Another thing that would help would be to link to the official docs from your blog in order to boost the search ranking. -Phil -- 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
