Opening this up to get feedback on whether or not there would be value in replacing gulp-gh-pages with an S3 static site deployment process - or the prospect that deployments are dropped altogether and that is left to the many CI/CD tools that are beginning to gain popularity. For instance yesterday rather than fight with gulp-gh-pages, we just used Codeship to run deployments to our S3 for static site testing.
I would be happy to contribute this enhancement if it is of interest. The rationale for the swap are as follows:
The AWS eco-system starts to open us up to other more robust features, with S3 for static site hosting as the obvious entry point, I think AWS as a platform can lend a lot of knowledge and learning to users of the package that will extend beyond blendid
Opening this up to get feedback on whether or not there would be value in replacing
gulp-gh-pageswith an S3 static site deployment process - or the prospect that deployments are dropped altogether and that is left to the many CI/CD tools that are beginning to gain popularity. For instance yesterday rather than fight with gulp-gh-pages, we just used Codeship to run deployments to our S3 for static site testing.I would be happy to contribute this enhancement if it is of interest. The rationale for the swap are as follows:
gulp-gh-pagesappears fairly abandoned. Most recent updates close to two years ago https://github.com/shinnn/gulp-gh-pages/Let me know what you think!