Archiving website!

[shiffman]

Hello ml5-website contributors past and present! We are launching a new redesign of the website as documented in these repos:

https://github.com/ml5js/ml5-website-v02-gatsby
https://github.com/ml5js/ml5-website-v02-docsify

We would like this website to be archived so that users of ml5.js versions 0.12.2 and prior can continue to access the documentation.

I don't have the keys to the netlify deployment of this website. Perhaps @bomanimc or @joeyklee you might be able to pass those along?

cc @MOQN and team who is working on the new website!

Thanks everyone for your patience and understanding as we do our best to navigate the complexity of this transition!

cc @sharellb

[joeyklee]

Amazing! Congrats on all the latest developments. I'm so thrilled to see how far everything has come over the last couple years. @shiffman I can add you via netlify. Is there a good email I can send the invite link to? TY!

[shiffman]

Thank you @joeyklee, I'll send you a note via email!

[shiffman]

A quick update, the site has now been transitioned over! Here are all the domains:

https://ml5js.org/ -> homepage for ml5 next gen!
https://docs.ml5js.org/ -> docs for ml5 next gen!

https://archive.ml5js.org/ -> archive of homepage for ml5 0.12.2
https://archive-docs.ml5js.org -> archive of docs for ml5 0.12.2

We can update all the links in this repo then make sure we are referencing / documenting links to the archive on the new website and materials! Feel free to use this thread to note any errors I made or requests to adjust subdomains, etc!

[shiffman]

tagging in @alanvww as we are discussing this!

[shiffman]

The website is now archived and deployed to https://archive.ml5js.org/ with a banner thanks to @alanvww!

The next step is to "archive" this repo via GitHub, @alanvww would you have some time to document that the site is archived with any relevant information in the README and I will then go ahead and select the archive option in the GitHub settings?

After that, we can move onto archiving the ml5-library repo as well.

[alanvww]

@shiffman Sounds good! I will work on it. But I am not sure if archiving the repo will affect the deployment or not. I will test it on my own first.

[shiffman]

@shiffman Sounds good! I will work on it. But I am not sure if archiving the repo will affect the deployment or not. I will test it on my own first.

Oh, good point! We likely should not archive the repo if it's still live deploying, even if just to update necessary security fixes/updates for dependencies. Documenting the state of the repo and the project in the README and maybe renaming this repo to ml5-website-archive are probably the more important pieces!