Should this be part of `CIDER` instead?

[xiongtx]

Nice content, but shouldn't this stuff live under doc/ in the CIDER repo?

For one thing, it's easy for external documentation like this to get out of sync with the development in CIDER itself.

[dpsutton]

Possibly.

The reasons to not do this is that it is a website in its own right. It would be strange to have a clojure website inside of an emacs lisp project. Further, less than documentation, I hope that the documents have a more blog and tutorial feel. The hope is that these posts don't teach those than know in-depth details of CIDER already but introduce would-be contributors that they can approach the codebases. This is plural as the site already spans CIDER and cider-nrepl.

Ideally this site has lots of contributors to both content and appearance. I like the idea of posts about bugs where people get stuck; I like posts that don't "solve" anything but explain subsystems; I like the idea of posts that just explain a possible roadmap for future development and asking for contributions. None of these should be inside of a documents folder of a particular project.

[MalloZup]

autogenerated with https://github.com/MalloZup/doghub: issue inactive since 450 days. Please update the issue or close it