Docusaurus: Adding instructions for Travis CI integration

[flarnie]

Would you be open to adding a section to the docs about Travis CI integration? Right now we talk about Circle CI. https://docusaurus.io/docs/en/publishing.html#automating-deployments-using-continuous-integration

Asking because we will be setting up integration with Travis anyway in the Draft.js repo, thought the info could be good to share. See https://github.com/facebook/draft-js/pull/1607

[JoelMarcey]

Hi @flarnie. Absolutely. We only started with CircleCI because that is what we use for Docusaurus. But we are definitely happy to add other CI flows. Are you thinking a PR?

[Daniel15]

Seems like it'd be better to encourage more flexible hosting services such as Netlify. More reliable and less moving parts compared to having a CI service that's separate to the hosting service. You could use Docusauraus with Netlify without requiring an extra CI system like CircleCI or Travis.

[JoelMarcey]

m whynotboth

In the end, we should probably be fairly agnostic in the hosting service. Having docs for CircleCI, Travis, Netlify all seem quite reasonable. We just chose CircleCI because that was a familiar platform that current docs used for CI and it was easy to get started with that.

[endiliey]

I will claim this issue for travisCI documentation