-
Notifications
You must be signed in to change notification settings - Fork 18
Description
This is an epic
This issue acts as an epic tying together issues related to integrating pinning services into IPFS Web UI (and, as a result, IPFS Desktop), as well as any integration that needs to be made to IPFS Companion.
Initial notes on the work and its rationale can be found in the original PRD.
Note that not all issues in this epic will need to be solved for an MVP release. Those that do need to be solved are noted as 🔑 in the list below.
Issues currently in this epic
- Pinning integration: Solve for "pins" item in File screen info bar ipfs-webui#1505: Solve for "pins" item in File screen info bar
- 🔑 Pinning integration [SPIKE]: Determine how/where files are pinned ipfs-webui#1504: Determine how/where files are pinned
- 🔑 Pinning integration: Stub UI for Settings screen ipfs-webui#1501: Stub UI for Settings screen
- 🔑 Pinning integration: descope stats from Settings screen ipfs-webui#1544: Descope stats from Settings screen
- 🔑 Pinning integration: Stub UI for Files screen ipfs-webui#1500: Stub UI for Files screen
- 🔑 Pinning integration: Build additional Joyride helptext for settings and files screens ipfs-webui#1514: Build additional Joyride helptext for settings and files screens
- 🔑 Pinning services: amend CLI tutor mode helptext ipfs-webui#1686: Amend CLI tutor mode helptext
- 🔑 docs: remote pinning services ipfs-docs#369: Add pinning service info to docs
- 🔑 'Delete' modal: improve pin guidance and overall language ipfs-webui#1634: Improve pin guidance in "Delete" modal
- 🔑 Pinning integration: Make Settings screen functional ipfs-webui#1503: Make Settings screen functional
- 🔑 Pinning integration: Make Files screen functional ipfs-webui#1502: Make Files screen functional
- 🔑 Pinning service integration: Augment "Pin IPFS Resource" functionality ipfs-companion#888: Augment "Pin IPFS Resource" functionality in Companion
A note on future enhancements (v2 and onwards)
This epic currently contains only issues that are critical to an MVP release, are important background for critical issues, or are at the top of the nice-to-have list. This is an intentional strategy, for the sake of avoiding defining solutions for problems that may substantially change before we are able to work on them. However, if you'd like an idea of future-state efforts, please check the original PRD; a variety of items have been listed and brainstormed there.