Is your feature request related to a problem? Please describe.

The docs are now deployed ad-hock when the need occurs. Ideally you would deploy the docs after every change in the /docs/ directory of the Timber main repo.

Describe the solution you’d like

Create a github action that does the following:

• Checkout timber/timber in a directory
• Checkout timber/docs in another directory
• Run the build process
• Deploys the artifacts of that build to Github pages.

At first this could be a manual trigger from the docs repo but we could automate that even further so that the action is triggered when in the main timber branch a commit is merged that changes the docs.

If this all works we could delete the content, docs and build folder from the repo since these are artifacts anyway.