Make pba-content public

[wirednkod]

This PR is adding gh-pages automation to the content. Once the repository becomes public in the settings of the repo (cc @Asamartino ), then we can merge this PR and automate the publication of the content to the pages;

[JoshOrndorff]

I certainly support making it public.

I'm curious how this ci job compares to the existing one at https://github.com/Polkadot-Blockchain-Academy/pba-content/blob/main/.github/workflows/ci.yml

It seems Nuke already has the content publishing to ipfs / fleek?

[wirednkod]

I certainly support making it public.

I'm curious how this ci job compares to the existing one at main/.github/workflows/ci.yml

It seems Nuke already has the content publishing to ipfs / fleek?

The difference is simple.
I wrote the gh-publish.yml while I never realised that the ci.yml existed.
Also the script was deploying to IPFS, which I do not find a reason why... (will remove)

[Asamartino]

thank you for your help Nikos

[JoshOrndorff]

No strong opinion here, and certainly nothing to block, but I do prefer ipfs to github pages because of the whole centralized-actors-can-censor-stuff problem.

[wirednkod]

No strong opinion here, and certainly nothing to block, but I do prefer ipfs to github pages because of the whole centralized-actors-can-censor-stuff problem.

My intention here is to eventually "place" this in IPFS - BUT under https://polkadot.academy/content link (will mask the IPFS one). I understand the concern of the centralized etc, but for now I'd prefer to place it under github (until I figure out the best decentralized solution)