Skip to content
This repository was archived by the owner on Jun 2, 2020. It is now read-only.

Examine top inbound-links referrers for proactive-fix opportunities. #506

Closed
3 of 4 tasks
johnnymatthews opened this issue May 1, 2020 · 9 comments
Closed
3 of 4 tasks
Assignees
Labels
dif/easy Someone with a little familiarity can pick up effort/days Estimated to take multiple days, but less than a week kind/maintenance Work required to avoid breaking changes or harm to project's status quo P2 Medium: Good to have, but can wait until someone steps up status/in-progress In progress topic/infra Infrastructure topic/site-deprecation Tasks regarding the deprecation of the legacy docs.ipfs.io website.

Comments

@johnnymatthews
Copy link
Contributor

johnnymatthews commented May 1, 2020

  • Examine top referrers for inbound links to see if there are any opportunities to directly contact those referrers and ask links to be changed
  • Find GitHub repos and add pull-requests to change and relevant links.
  • Make forks.
  • Merge after site goes live.
@johnnymatthews johnnymatthews added dif/easy Someone with a little familiarity can pick up effort/days Estimated to take multiple days, but less than a week topic/infra Infrastructure P2 Medium: Good to have, but can wait until someone steps up kind/maintenance Work required to avoid breaking changes or harm to project's status quo status/ready Ready to be worked labels May 1, 2020
@johnnymatthews johnnymatthews added the topic/site-deprecation Tasks regarding the deprecation of the legacy docs.ipfs.io website. label May 1, 2020
@johnnymatthews
Copy link
Contributor Author

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.

@jessicaschilling
Copy link
Contributor

jessicaschilling commented May 14, 2020

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.

@autonome
Copy link

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

@jessicaschilling
Copy link
Contributor

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.

@johnnymatthews
Copy link
Contributor Author

johnnymatthews commented May 21, 2020

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.

@johnnymatthews johnnymatthews self-assigned this May 21, 2020
@johnnymatthews johnnymatthews added status/in-progress In progress and removed status/ready Ready to be worked labels May 21, 2020
@hugomrdias
Copy link

What else needs to be done here ?

@hugomrdias
Copy link

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

@jessicaschilling
Copy link
Contributor

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.

@jessicaschilling
Copy link
Contributor

jessicaschilling commented May 22, 2020

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dif/easy Someone with a little familiarity can pick up effort/days Estimated to take multiple days, but less than a week kind/maintenance Work required to avoid breaking changes or harm to project's status quo P2 Medium: Good to have, but can wait until someone steps up status/in-progress In progress topic/infra Infrastructure topic/site-deprecation Tasks regarding the deprecation of the legacy docs.ipfs.io website.
Projects
None yet
Development

No branches or pull requests

4 participants