Like, it's not clear to me what problem it solves.
It's described as "The complete SDK for Chat, Commenting, and Notifications" yet I've read the entire readme and it isn't clear which languages it has client-SDKs for, if any.
If my boss came to me and said, "Can you evaluate Cord for a chat and notification back-end" I'd return a quick message ruling it out on the basis of there being no documentation, no example integrations, no obvious client SDK packages, etc.
It's also hardly zero-friction just getting it running. It needs both Node/NPM and docker.
Why? Either ship me the NPM packages, or point me to a docker command I can run. If it's containerised, why does it need NPM? If it's shipped as NPM/source, why does it insist I deploy with docker?
Show me some simple code examples so I can see how easy it is to get a chat client running, don't give "broken" links to docs and APIs that would only work if I'm already running your software, I'm unlikely to get that far without browsing the API and docs.
Yeah, the open-sourcing process seemed to have destroyed all documentation.
There are still 3-rd party sites with copy of the docs, like https://docs.comment.workcanvas.com/ (full of dead links), but it seems the main site used to be "cord.com" and this is already sold to some job search site.
I am surprised they did not open source the doc... or maybe no one has bothered to bring up the server?
They must have sold the domain to the job portal cord.co. I got an email about it in February:
> We're becoming cord.com
> Hi,
> Over the next few weeks cord.co is becoming cord.com. Adding an "m" to the end of our URL is one of the smaller things we've done. But it represents something much bigger: that cord has become the trusted source for tech hiring in the UK.
Correct. Though the docs do all exist in the repo. We opensourced it after we failed because our partners wanted to continue to use it, so we helped them migrate data and run their own instances of it.
Like, it's not clear to me what problem it solves.
It's described as "The complete SDK for Chat, Commenting, and Notifications" yet I've read the entire readme and it isn't clear which languages it has client-SDKs for, if any.
If my boss came to me and said, "Can you evaluate Cord for a chat and notification back-end" I'd return a quick message ruling it out on the basis of there being no documentation, no example integrations, no obvious client SDK packages, etc.
It's also hardly zero-friction just getting it running. It needs both Node/NPM and docker.
Why? Either ship me the NPM packages, or point me to a docker command I can run. If it's containerised, why does it need NPM? If it's shipped as NPM/source, why does it insist I deploy with docker?
Show me some simple code examples so I can see how easy it is to get a chat client running, don't give "broken" links to docs and APIs that would only work if I'm already running your software, I'm unlikely to get that far without browsing the API and docs.