Examine top inbound-links referrers for proactive-fix opportunities. about docs HOT 9 CLOSED

With a release manager hat on, I'd characterize this as "non-blocking mustfix"

• doesn't need to block the release, because redirects are in place
• must be fixed as post-release cleanup

from docs.

I'll just fix those myself. Reminder set for the 27th to take care of it.

from docs.

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.

from docs.

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.

from docs.

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.

from docs.

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.

from docs.

What else needs to be done here ?

from docs.

Since the only repo from the above sheet is infra, im closing this.
Refer to ipfs/ipfs-docs#240 for the launch task list.

from docs.

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.

from docs.