This repository was archived by the owner on Jun 2, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 56
Better integrate browser-addressing content with docs.ipfs.io #256
Labels
dif/easy
Someone with a little familiarity can pick up
effort/hours
Estimated to take one or several hours
help wanted
Seeking public contribution on this issue
topic/design-content
Content design, writing, information architecture
topic/docs
Documentation
Comments
@lidel 🙌 |
@ericronne Is it safe to PR it under "Guides", or should I pause until after content juggling planned on friday? |
Whichever is most convenient for now is fine. It will very likely find a new home after friday :) |
@lidel did you get a chance to work on this one yet? It can go under "Guides" for now, thx! |
hi @lidel ... just pinging you on this one. Do you still have time? Thanks! |
I am really sorry, totally missed previous mention notification for this. |
lidel
added a commit
that referenced
this issue
Sep 30, 2019
This change replaces link to external SPEC with dedicated guide which integrates more natively with the rest of docs.ipfs.io and provides more elaborate introduction of each addressing scheme. Closes #256 License: MIT Signed-off-by: Marcin Rataj <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
dif/easy
Someone with a little familiarity can pick up
effort/hours
Estimated to take one or several hours
help wanted
Seeking public contribution on this issue
topic/design-content
Content design, writing, information architecture
topic/docs
Documentation
Uh oh!
There was an error while loading. Please reload this page.
This issue is part of Epic 3B: Fixes from legacy issue queue.
Currently the
Addressing in Browsers
nav option on docs.ipfs.io links directly to this helpful article on github. In order to create a more cohesive user experience, let's create an introductory page on the docs site, which then links to the full article. (This introduction should then be added to the article, as well.)The text was updated successfully, but these errors were encountered: