There ought to be no need to access external video/storage providers to download installers and packaged versions of this plugin.
Furthermore, since this plugin is rather straightforward in its build process, I highly encourage you to develop in-line CI with GitHub's own Actions and Packages, which may be at a later date expanded into version-bound manual pages updates via Pages, all in made to measure setup within repository.
With that being said, I would be glad to come help with such setup, be it CI maintenance, documentation/manual writing/proofing/editorial or transcribing package creation to different formats, so that Terrain can be included in a more niche setups in a more automated way.
For that, if you agree and would like to make a switch to CI, I kindly ask you to make an initial Actions/Packages pipeline, so I don't interfere with your more important plans and pieces of roadmap upon expanding it.
There ought to be no need to access external video/storage providers to download installers and packaged versions of this plugin.
Furthermore, since this plugin is rather straightforward in its build process, I highly encourage you to develop in-line CI with GitHub's own Actions and Packages, which may be at a later date expanded into version-bound manual pages updates via Pages, all in made to measure setup within repository.
With that being said, I would be glad to come help with such setup, be it CI maintenance, documentation/manual writing/proofing/editorial or transcribing package creation to different formats, so that Terrain can be included in a more niche setups in a more automated way.
For that, if you agree and would like to make a switch to CI, I kindly ask you to make an initial Actions/Packages pipeline, so I don't interfere with your more important plans and pieces of roadmap upon expanding it.