Skip to content
This repository has been archived by the owner on Jun 2, 2020. It is now read-only.

Make it clear what "the community section" means #354

Merged
merged 1 commit into from
Oct 21, 2019

Conversation

terichadbourne
Copy link
Contributor

I arrived at the community section of this documentation by clicking "Community" in the footer of the ipfs.io website. I actually assumed it was going to take me to a GitHub repo I've seen before (not that I enjoy that as a presentation mechanism) and wasn't expecting the docs site.

I was trying to find links to all of the social channels (IRC, etc.) for someone who asked me where to discuss IPFS questions. When I got to the phrase "See the other links in the community section" I tried scrolling down within the page I was on but felt like I was already in the community section. The nav is so long that there was no hint of community on the portion of it in view, though it actually didn't occur to me to look there. ¯_(ツ)_/¯

Is there a way to link someone to an anchor in the nav or do I just need to describe the process of scrolling in the nav until you find the links? Should they be duplicated in the content of the community section here?

I arrived at the community section of this documentation by clicking "Community" in the footer of the ipfs.io website. I was trying to find links to all of the social channels (IRC, etc.) for someone who asked me where to discuss IPFS questions. When I got to "See the other links in the community section" I tried scrolling down within the page I was on but felt like I was already in the community section. The nav is so long that there was no hint of community on the portion of it in view, though it actually didn't occur to me to look there. ¯\_(ツ)_/¯ 

Is there a way to link someone to an anchor in the nav or do I just need to describe the process of scrolling in the nav until you find the links? Should they be duplicated in the content of the community section here?
@terichadbourne
Copy link
Contributor Author

For the record, I clicked the "change this on GitHub" link to create this. :)

@jessicaschilling
Copy link
Contributor

jessicaschilling commented Oct 16, 2019

Thanks @terichadbourne ... we've also got ipfs-inactive/website#307 to try to disambiguate this better, but it got a little bogged down in the weeds of trying to get Hugo to play well with the left-hand nav. I'd say merge this PR, but if you wanted to help chip away at ipfs-inactive/website#307 too, that would be awesome!

@jessicaschilling jessicaschilling added topic/design-content Content design, writing, information architecture topic/docs Documentation labels Oct 16, 2019
@terichadbourne
Copy link
Contributor Author

terichadbourne commented Oct 16, 2019 via email

@jessicaschilling
Copy link
Contributor

Indeed it wasn't ... I meant 307 in a different repo: ipfs-inactive/website#307

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
topic/design-content Content design, writing, information architecture topic/docs Documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants