Closed johnnymatthews closed 4 years ago
The overwhelming majority of inbound links into docs-beta.ipfs.io
are coming from GitHub, specifically the ipfs/ipfs-docs-v2
and ipfs/docs
repos. All these links will get caught in the docs-beta.ipfs.io
-> docs.ipfs.io
redirect rules in #503.
What about links to docs-beta from our own codebases -- not so much thinking of links that live within people just clicking on things in GitHub, but things like the "read more" links within IPFS Companion's prefs, the IPFS website, etc? I understand that they'll get redirected ... it's just kind of poor optics if we have out-of-date links in our own products.
With a release manager hat on, I'd characterize this as "non-blocking mustfix"
If we're tentatively pushing to the 27th (to avoid collision with another release @cwaring is critical in), there might still be time to wrap this up before then -- if not, completely agree with @autonome.
This spreadsheet lists all the IPFS, Protocol, and IPFS-Shipyard orgs repos with links to docs-beta
.
Created forks for each of the repos across the orgs. Once the site goes live I'll make PRs against each repo.
What else needs to be done here ?
Since the only repo from the above sheet is infra, im closing this. Refer to https://github.com/ipfs/ipfs-docs/issues/240 for the launch task list.
It doesn't look as though the spreadsheet is complete. There are links to docs-beta in multiple places throughout repos in the IPFS GitHub org.
I'll just fix those myself. Reminder set for the 27th to take care of it.