Go module paths tracking issue

[ydnar]

• POC go.bytecodealliance.org with duplicate repo at https://github.com/bytecodealliance/go-modules
• Disable GitHub Pages on https://github.com/bytecodealliance/go-modules repo (@ydnar)
• Delete or rename POC https://github.com/bytecodealliance/go-modules repo (@ydnar)
• Set up CNAME for go.bytecodealliance.org → bytecodealliance.github.io (@ricochet)
• Rename https://github.com/bytecodealliance/wasm-tools-go → https://github.com/bytecodealliance/go-modules (@ydnar)
• Fork https://github.com/bytecodealliance/go-modules → https://github.com/bytecodealliance/wasm-tools-go (@ydnar)
• Mass find & replace github.com/bytecodealliance/wasm-tools-go → go.bytecodealliance.org in https://github.com/bytecodealliance/go-modules repo (@lxfontes)
• Enable GitHub pages on https://github.com/bytecodealliance/go-modules repo @ go.bytecodealliance.org (@lxfontes)
• Fix links in Releases: https://github.com/bytecodealliance/go-modules/releases (@ydnar)
• Deprecate the github.com/bytecodealliance/wasm-tools-go module (@ydnar)
• Blog post? (@lxfontes + @ricochet?)

[lxfontes]

we also talked about a blog post, but didn't get into details on where/when/content

[Mossaka]

I am happy to draft a blog post based on the talk @ydnar and I will present at WasmCon

[ydnar]

Looks like @Mossaka has the blog post. I’ll keep this tracking issue open until we post it!