-
Notifications
You must be signed in to change notification settings - Fork 465
SEO fixes #1252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SEO fixes #1252
Conversation
mishmosh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure I agree with renaming server infrastructure to IPFS Cluster. Calling it "server infra" or something descriptive is more likely to catch the attention of users who don't know that Cluster is the solution to their problem. I believe this has been an issue historically. Can you git blame to find who made that change initially and discuss with them?
Everything else looks great, thank you. Your cleanups are a good reminder (for me and hopefully others too) that when deleting or renaming anything, we should also search the full repo for references to that thing and clean up accordingly.
How about forking the "server infrastructure" change into a separate PR and merging everything else?
|
Sounds good. I've reverted the change for now It looks like it was server infrastructure from the get-go 91e5026#diff-1c3779e94655b66d9a2ec90eb95bfcf977a0e04ccc41fc9e2974594e6b5a7d32 |
What's in this PR
.ioto.techBackground
I was baffled to discover we're not the first result for
ipfs cidon Google, only to discover we don't have the keyword in the title