DevOps (CircleCI): `build step` to publish latest version on Github Pages

[rjlopezdev]

I've noticed Devicon Web is not updated with the latest icons.

I could design a simple CI cycle to atomate this proccess:

Steps

• First: build static files
• Second: commit new version to gh-pages branch

Triggers

• Commiting over master branch

If you are interested, I would need the scripts you use to publish on gh-pages 🙏

[konpa]

There is none... I want to automate the process (as well as the one to generate the font files) for a long time but never took the time to do it... For now, gh-pages is just an Angular SPA with master branch as submodule.

[rjlopezdev]

Ouh! I see...
I could work on this first:

• Rewriting old angular.js app into a new Angular 7.
• Script to read fonts directory to parse it & generate a JSON with new additions.

Once this is done, build CI cycle.

If you agree that, I could work on it.
Unless, I'll close this issue.

[konpa]

Yes sure, would be great !

[amacado]

@rjlopezdev are u still interested in contributing? Because an automated build process including the font generation would be amazing.

[rjlopezdev]

Sure! Please, can you explain me the build process in order to I can reply it & automate It? @amacado 🙏

[amacado]

I'm working on a document explaining the build process. Update here as soon it's ready

[rjlopezdev]

Awesome! Eager to read it!

[amacado]

I just published the first version of the documentation in my fork. Feel free to take a look at it and enhance it. I also upgraded to gulp v4 in this pull request, since gulp 3 is not compatible with current node version.

I think the main challenge for build automation is the icomoon.app (maybe there is an api?) and we would need to refactor the 'alias'-idea in the stylesheets.

[amacado]

I'm thinking of integrating the gh-pages branch into the master branch so we do not face the issue of keeping the two branches up to date anymore, any thoughts of this?