The state of the art of using mkdocs to update the documentation would be to:
PR in the master branch any change\etc from develop
Pull locally the master
Build the docs with mkdocs build
Push to the gh-pages branch the builded documentations using the built-in mkdocs gh-deploy
Instead of having to manually do all this stuff and use mkdocs gh-deploy from the local master branch to update the docs, I stumbled upon this article that explains how travis-ci can also build and deploy from the source. This way we can just worry about commits and PR to master and travis will do the rest.
The state of the art of using mkdocs to update the documentation would be to:
Push to the gh-pages branch the builded documentations using the built-in
mkdocs gh-deployInstead of having to manually do all this stuff and use
mkdocs gh-deployfrom the local master branch to update the docs, I stumbled upon this article that explains how travis-ci can also build and deploy from the source. This way we can just worry about commits and PR to master and travis will do the rest.Is it worth the implementation? For me, yes