This issue is probably more of a discussion for collaborators but of course anyone is welcome to chime in with opinions. Once Cord (the company) shuts off their infrastructure then obviously the documentation site will be offline. If people need documentation they can, of course, pull down this repo, get it set up, and serve the documentation themselves. However, I believe it would be beneficial at some point to host the documentation and link to it from this repo. That decreases the effort to get started using Cord. The way I see it, there are a few options.

1. Host the existing docs on GitHub Pages. I'm not certain if that's possible today with no changes, as it seems there is a server component to the built docs and I have not looked fully into it yet.
2. Host the existing docs on some other infra. This obviously will likely have cost associated with it, so unless there is someone or some company willing to eat that cost I don't think this is a viable option.
3. Use something like Read the Docs as they have a free open source plan, but that would obviously require re-documenting everything there. Not ideal unless someone really loves writing documentation or is willing to put in that time. That said, it may be a good longer term option which would then let us remove all the docs code in the repo, simplifying things.
4. Re-write the docs using some other tool to generate a purely static site with no server component at all, which would allow us to easily host this from this repo using GitHub Pages. This is another longer-term option given the time investment that would be needed to re-write the docs using another tool.

I'm hoping there are other much better options I'm just not aware of, which is a big reason for having a public discussion on this subject. The important thing to keep in mind is Cord is shut(ting) down so any effort from here on out is entirely voluntary and community driven. That said, I'm looking forward to the discussion.