Merge documentation into a central resource on the Keep website

[creckhow-zz]

Including the documentation in a clear flow from the Keep website, and it's easy to get back to the main website. Added legitimacy that it's coming from the keep website domain and not from gitbook in the URL. (edited)

[creckhow-zz]

Even if the "resource center" isn't primarily the gitbook, we must have a flow or window to it on the Keep stakedrop page.

[creckhow-zz]

Tagging @liz-shinn @Gluzman here but this is also one for @mhluongo @Shadowfiend and @sthompson22 to weigh in on. (please assign yourself accordingly)

As we talked about in the stakedrop planning sessions, this is an age old discussion. Our ideal solution for documentation is to build a CMS on keep.network (like we've got for tbtc.network) but where real github issues push the content, so we can have streamlined place for all technical docs and community contribution.

Unfortunately we don't have the resources for that this month. Gitbook is the solution we came up with back in April, and it will continue to work well because:

• it's user friendly
• we can give it our branding & incorporate it into our main site
• we can invite community members to write changes for us to push

But we can agree it is not a long term solution.

For now gitbook is the SOURCE OF TRUTH for official staking documentation.

This card is asking for a strategic design decision on how gitbook is built into the stakedrop section of the new keep.network.

[creckhow-zz]

We need to learn more about how close we can get gitbook to our own website. It looks like we can't imbed it directly (and we might not want to -- it's OK for the docs to be separate).

We'd like the URL tied to our website. And have it easy to go back and forth to the current Keep site and gitbook

[liz-shinn]

[liz-shinn]

@Shadowfiend @ironng We'd like to assign the staking documentation GitBook a custom domain that's the same as the Keep website with a /docs on the end. What are your thoughts on this?