Build Trigger for new/updated cloud resources or embedded external repositories
If documents in a cloud resource or an external repository are newly added or updated the project itself does not recognize those changes and will not start the mkdocs build process. Therefore, a trigger url woud be covenient to start the process by hand maybe with some time-out or threshold to avoid an overload by repeated trigger calls within a given time.
Alternatively, we need a reliable schedule for frequent re-builds.
Possible pifalls:
- versioning (how to tag those external changes so that the CI script which waits for tags recognizes the task?)