-
Notifications
You must be signed in to change notification settings - Fork 35
Open
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/weeksEstimated to take multiple weeksEstimated to take multiple weeksexp/intermediatePrior experience is likely helpfulPrior experience is likely helpfulgood first issueGood issue for new contributorsGood issue for new contributorshelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featurestatus/readyReady to be workedReady to be workedtopic/design-contentContent design, writing, information architectureContent design, writing, information architecturetopic/design-front-endFront-end implementation of UX/UI workFront-end implementation of UX/UI worktopic/design-uxUX strategy, research, not solely visual designUX strategy, research, not solely visual designtopic/design-visualVisual design ONLY, not part of a larger UX effortVisual design ONLY, not part of a larger UX effort
Description
This issue is one of the prioritized recommendations in the Q1 2020 IPFS Ecosystem Audit for execution in Q2/Q3 2020. Tagging it with $auditrecommendation
means it's searchable! See all tagged issues in this repo.
IPLD Explorer is awesome once you know what all of it means ... but that's making a massive assumption. We're missing out on a large learning opportunity.
Add explanatory info and context to the site, so someone inexperienced in IPFS could use this as an entry point to learning more in general. This could include ...
- Inroductory content provided in a non-intrusive way, so it could ignored by those in the know
- Hover links with extensive cross-linking to docs, ProtoSchool, etc
Also see ipfs/ipfs-companion#610 for additional brainstorming on better integrating IPLD Explorer.
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/weeksEstimated to take multiple weeksEstimated to take multiple weeksexp/intermediatePrior experience is likely helpfulPrior experience is likely helpfulgood first issueGood issue for new contributorsGood issue for new contributorshelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featurestatus/readyReady to be workedReady to be workedtopic/design-contentContent design, writing, information architectureContent design, writing, information architecturetopic/design-front-endFront-end implementation of UX/UI workFront-end implementation of UX/UI worktopic/design-uxUX strategy, research, not solely visual designUX strategy, research, not solely visual designtopic/design-visualVisual design ONLY, not part of a larger UX effortVisual design ONLY, not part of a larger UX effort