The team took an incredible amount of time to make each link redirect to the correct rescript-lang.org resource.
When it was done, the bucklescript github organization was renamed to rescript-lang, which caused a new github pages population to the edges that caused 404s in different regions. It takes a little bit of time until resources are forwarded correctly within GH.
For us in Europe and SF, it was actually working after we made the changes.
As soon as some community members had broken links, they assumed that the team intentionally didn't care about backwards compat, so someone recreated the BuckleScript github organization with a dummy bucklescript.github.io that made a single redirect to the rescript-lang.org site.
From there on all the carefully curated link forwardings were lost. Ironically this actually broke our backwards compat.
It took us a lot of investigation, contacting github, understanding the technical issues with GH pages until we found a solution to restore the original (working) behavior. People should have waited 1-2 days and everything would have just worked fine.
Well, that was a learning nonetheless. We invested many extra hours to get everything up and running again, but now everything works and it will hopefully continue on doing so.
When it was done, the bucklescript github organization was renamed to rescript-lang, which caused a new github pages population to the edges that caused 404s in different regions. It takes a little bit of time until resources are forwarded correctly within GH.
For us in Europe and SF, it was actually working after we made the changes.
As soon as some community members had broken links, they assumed that the team intentionally didn't care about backwards compat, so someone recreated the BuckleScript github organization with a dummy bucklescript.github.io that made a single redirect to the rescript-lang.org site.
From there on all the carefully curated link forwardings were lost. Ironically this actually broke our backwards compat.
It took us a lot of investigation, contacting github, understanding the technical issues with GH pages until we found a solution to restore the original (working) behavior. People should have waited 1-2 days and everything would have just worked fine.
Well, that was a learning nonetheless. We invested many extra hours to get everything up and running again, but now everything works and it will hopefully continue on doing so.