GH pages website broken

[cgwalters]

Update: For now we'll need to go through consuming websites and manually update links to point to https://bootc-dev.github.io/bootc/

There is unfinished discussion on adding a new domain name as a redirect (ref #897 (comment) ) but this is semi-blocked on us finishing the CNCF transition, which is blocked on things tracked in that discussion thread.

---

Github does redirects when accessing the main repo, but not for Github Pages.

We need to execute on something like https://dev.to/steveblue/setup-a-redirect-on-github-pages-1ok7

[cgwalters]

Hmm digging at this more I'm not sure much has changed since this 10 year old issue: isaacs/github#492

The core problem is that while we could add a HTTP redirect for the Github Pages site, the only implementation of that is to create a stub git repository to do so, which breaks the redirect for e.g. git clone https://github.com/containers/bootc ...

[cgwalters]

So for the immediate term I think I lean to just update consuming sites

[mabulgu]

@cgwalters Git's submodules might work for this case if the redirection doesn't work. I think I did one in the past. The pages code can be kept in the new org/repo but the pages will still be managed from containers org. Would you go with sth like this? I will find you an example I implemented in the past.

[mabulgu]

here it is:

The website code is located here: https://github.com/SystemCraftsman/strimzi-kafka-cli/blob/main/website/index.html
But the website is broadcasted from here: https://github.com/strimzi-cli/strimzi-cli.github.io

https://strimzi-cli.github.io/

Not as good as redirection but at least sth that works. For your consideration.

[vrothberg]

So for the immediate term I think I lean to just update consuming sites

Yes, let's go over docs and blog posts etc.

[cgwalters]

Yes, let's go over docs and blog posts etc.

We're discussing allocating a domain name, so before we try updating the links at a large scale let's see about the decision on that.

[cgwalters]

Not as good as redirection but at least sth that works. For your consideration.

I don't quite understand this. If we have the capability to deploy HTML, then we can use very standard "meta refresh" that's described in that original post.

The problem is deploying any HTML at all in the old location - as far as I know, the only way to do that would be to put a git repository there, which would break the automatic redirection for git.

[cgwalters]

So far I think we don't know of a solution other than to canonicalize on a domain name that's CNCF owned so we don't have this problem ever again. So let's do that.