Flesh out IPFS documentation community page and link to it from ipfs.io footer

[jessicaschilling]

This issue is part of Epic 3B: Fixes from legacy issue queue.

Problem: It's tough to know where one can discuss different aspects of IPFS, either synchronously or asynchronously.

Suggested solution:

1. Right now the footer link to "Community" on ipfs.io links to
   https://docs.ipfs.io/#community -- which doesn't give the user a clear indication that there's actually a whole "Community" section in the documentation table of contents (aka left-hand nav). Can we instead link to https://docs.ipfs.io/community/ -- which is the top level of the "Community" section of IPFS docs?
2. Then, on https://docs.ipfs.io/community/, we'll need to flesh out the content to more accurately represent what's linked outbound in the left-hand nav (see below for a screenshot of the nav section). Even simply duplicating that list of outbound links in the community landing page would be a good start -- even better would be adding short explanations of what the links led to.

[jessicaschilling]

FYI, @meiqimichelle 😄

[jessicaschilling]

Tagging this as a potential docs hotfix under the assumption that the front of ipfs.io is also the front page of our docs :)

[terichadbourne]

I stumbled on this problem by chance when trying to find the various links to community channels. Just merged a PR to temporarily call out that the content mentioned is in the ToC at left, not in the body, but agree this needs more work and body would be ideal in my mind. ipfs-inactive/docs#354

[jessicaschilling]

This issue gets fixed in two PRs:
#347
ipfs-inactive/docs#357
Both have been assigned to @ericronne for review 😊

One note: This leaves the IRC link at the bottom because that's Hugo's annoying auto-generated menu thing. Didn't dig deep into working around this, since it'll be a moot point in a few weeks in the new site.