Ship the docs site with GitLab

What we need to solve

The difference of styles between /help and docs.gitlab.com makes the work on the docs site much more complicated and truncated. It doesn't allow us to do anything special to the docs because it doesn't render or render weirdly in /help.

Once we change the markdown engine to Kramdown, there will be quite some noise in markdown files rendered with GFM, making them little more confusing for reading through /help
/help doesn't have breadcrumbs or any kind of docs navigation
We're willing to get rid of /help, but, instead, I'm proposing to build the docs site with GitLab, the application.

Advantages of maintaining `/help`

/help is helpful for self-managed instances without access to the internet. If we just remove it, we'll make their lives a lot more complicated
By maintaining /help we have up-to-date versioned docs for GitLab.com in gitlab.com/help
We won't need to refactor the whole app/views files in CE/EE (i.e. the question-mark links out to /help pages) as we would if we just removed of /help

How to solve all the problems

Maintaining /help but making it look exactly like docs.gitlab.com.

Ship and build gitlab-docs with CE and EE
Add a configuration in GitLab to make it optional (something like docs: true or docs: false)
Locally, render on /help the same as we see in localhost:3000 when we run bundle exec nanoc live
Keep the relative links in the docs and in app/views
Only use pull paths for Runner and Omnibus, as we currently do

Implementation

Pull gitlab-docs into CE/EE
Once we start GitLab, make it build the docs site (nanoc compile)
Serve the docs site under your-instance/help
I asked a few devs during the summit if this would be a great deal of work and they all said that it would probably be doable, no biggie.