Thank you for the feedback.

> 1. CHICKEN page https://get.scheme.org/chicken/
> <https://get.scheme.org/chicken/> links to Chez resources incl docker
> Logged as https://github.com/schemeorg-community/monorepo/issues/20
> <https://github.com/schemeorg-community/monorepo/issues/20>
>
> I'll happily do a PR but sadly https://get.scheme.org/chicken/
> <https://get.scheme.org/chicken/> does not have a repo listed at
> https://www.scheme.org/source/ <https://www.scheme.org/source/>

It's my fault for uploading unfinished work to the server. I should have
been more careful. Nothing should yet be linking to
https://get.scheme.org/chicken/ though. How did you find it?

https://www.scheme.org/source/ lists the sources at a subdomain
granularity. For get.scheme.org it correctly points at
https://github.com/schemeorg-community/monorepo/tree/master/get but the
unfinished pages have not yet been committed there.

> 2. https://chat.scheme.org <https://chat.scheme.org>
> Seems to duplicate https://community.scheme.org
> <https://community.scheme.org>  !
> Can I suggest that https://chat.scheme.org <https://chat.scheme.org> be
> decommissioned so only one page needs to be maintained?

Again, my mistake.

The plan has been to put IRC logs and other details on chat.scheme.org,
but nobody has yet got around to it. Likewise, mailing list archives at
lists.scheme.org.

The Community page duplicates not only the chat listing that is the area
of chat.scheme.org, but the mailing lists from lists.scheme.org. I agree
that it's confusing. Your suggestion to keep only one listing on the
Community page is probably for the best.

Maybe chat.scheme.org is superfluous in its entirety, but I'd like to
see about gathering the logs before we decide against it.

I hid the Chat link from the scheme.org front page but kept the
subdomain [1].

I will replace the contents of the current chat.scheme.org annd
lists.scheme.org web pages with a link to community.scheme.org.

The listing on community.scheme.org is a bit of a mess, as well. The
info is mostly OK but the layout and writing is inconsistent. It could
certainly be improved in many ways.

[1]
https://github.com/schemeorg/schemeorg/commit/9b2b7049c21e37f3ec0fe8f6cb578d8678c1cdd1

> 3. https://docs.scheme.org <https://docs.scheme.org> replicates books on
> https://books.scheme.org <https://books.scheme.org>
> - I'd suggest just linking to the more comprehensive list at
> https://books.scheme.org <https://books.scheme.org>

docs.scheme.org has been seeking its form since the start. It's a very
common subdomain for tech sites, so we should have it, but it has never
been obvious what to put there specifically.

I think the best approach is a devdocs.io or readthedocs style
hierarchical browser of all the Scheme documentation we can find. No one
has had time to implement this yet.

In its current form, docs.scheme.org should definitely link to
books.scheme.org. You're right about that.

> - Happy to do a PR to https://github.com/schemedoc
> <https://github.com/schemedoc> but I can't identify the repo
> https://github.com/orgs/schemedoc/repositories?type=all
> <https://github.com/orgs/schemedoc/repositories?type=all>

Thank you.

https://www.scheme.org/source/ links to
https://github.com/schemeorg-community/docs.scheme.org for docs.