Skip to content
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

Update landing page to better direct users how to use IPFS #1701

Closed
ElPaisano opened this issue Sep 20, 2023 · 0 comments · Fixed by #1711
Closed

Update landing page to better direct users how to use IPFS #1701

ElPaisano opened this issue Sep 20, 2023 · 0 comments · Fixed by #1711
Assignees
Labels

Comments

@ElPaisano
Copy link
Contributor

ElPaisano commented Sep 20, 2023

Problem description

The landing page https://docs.ipfs.tech/ contains the following subsections:

However, the page doesn't do a great job of directing the user how they can use IPFS. https://docs.ipfs.tech/#develop sort of attempts this, and directs the reader to pages like https://docs.ipfs.tech/install/ and https://docs.ipfs.tech/reference/. However, this could be done better:

Suggestion

Create a Get started section at the top of https://docs.ipfs.tech/ that resuses info from:

  1. https://docs.ipfs.tech/install/
  2. https://docs.ipfs.tech/reference/

Goal should be to make it clear the main ways (kubo, helia, desktop, companion, pinning service, etc.) in which users can actually do things with IPFS, and direct them quickly to the info on how to get started

@ElPaisano ElPaisano added the need/triage Needs initial labeling and prioritization label Sep 20, 2023
@ElPaisano ElPaisano linked a pull request Sep 25, 2023 that will close this issue
@ElPaisano ElPaisano added status/in-progress In progress and removed need/triage Needs initial labeling and prioritization labels Sep 25, 2023
@ElPaisano ElPaisano self-assigned this Sep 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant