-
Notifications
You must be signed in to change notification settings - Fork 449
chore: cleanup outdated services and old links #2108
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
base: main
Are you sure you want to change the base?
Conversation
Updated pinning service documentation: - Removed outdated web3.storage references from quickstart guides - Added current pinning services: Storacha, Pinata, and Filebase - Split /quickstart/publish.md and /quickstart/publish_cli.md into distinct GUI-focused and CLI-focused guides - Removed unused web3.storage screenshots Fixed outdated references: - Updated Accelerated DHT Client links from experimental features to current config documentation - Removed unnecessary "go-ipfs" references (now just "Kubo") Improved main install page: - Added "Publish files with a pinning service" section for easy onboarding Files modified - docs/quickstart/publish.md - Focus on web/GUI interfaces - docs/quickstart/publish_cli.md - Focus on CLI/API methods - docs/install/README.md - Added pinning section, minor fixes - docs/how-to/gateway-best-practices.md - Updated DHT client link - docs/how-to/troubleshooting.md - Updated DHT client link - docs/install/command-line.md - Removed "(go-ipfs)" reference - docs/reference/go/api.md - Cleaned up Kubo reference Files removed - docs/quickstart/images/ - Removed 6 unused web3.storage screenshots
🚀 Build Preview on IPFS ready
|
If we're bringing back the publish and publish cli pages, we should add it back to the sidebar menu. |
@@ -5,22 +5,18 @@ description: 'Learn how to publish content with IPFS by pinning a file to a pinn | |||
|
|||
# Publish a file with IPFS |
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'd suggest we name this pinning to be consistent with the terminology used in the lifecycle page https://docs.ipfs.tech/concepts/lifecycle
(I was the one who named this publishing but I no longer think it's a useful term for this, given that you're working with pinning services).
While at it, perhaps rename the files too.
# Publish a file with IPFS | |
# Pinning a file with IPFS |
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.
Nice. LGTM overall. I left a few small comments.
@@ -5,22 +5,18 @@ description: 'Learn how to publish content with IPFS by pinning a file to a pinn | |||
|
|||
# Publish a file with IPFS using the command line |
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.
# Publish a file with IPFS using the command line | |
# Pin a file with IPFS using the command line |
This PR includes some automated cleanup of outdated tutorials that were about web3.storage.
Updated pinning service documentation:
/quickstart/publish.md
and/quickstart/publish_cli.md
into distinct GUI-focused and CLI-focused guidesFixed outdated references:
Improved main install page:
Files modified
docs/quickstart/publish.md
- Focus on web/GUI interfacesdocs/quickstart/publish_cli.md
- Focus on CLI/API methodsdocs/install/README.md
- Added pinning section, minor fixesdocs/how-to/gateway-best-practices.md
- Updated DHT client linkdocs/how-to/troubleshooting.md
- Updated DHT client linkFiles removed
docs/quickstart/images/
- Removed 6 unused web3.storage screenshotsChecklist before requesting a review
Checklist before merging