Workflow for docs that are behind a feature flag and only available to GitLab.com

DRAFT

What we want to solve

• Currently, we deploy master in the root path of docs.gitlab.com/.
• In the future we want that path to be the latest stable version.
• A new "version" called dev will be deployed to docs.gitlab.com/dev, which will contain all docs from master.

Some features will be behind feature flags, meaning that they will only be enabled on GitLab.com. We don't want those to be available on the stable branches neither on master.

Possible solution

Have a separate docs-dev branch in CE/EE (in all products?)

• Every feature under a feature flag, should be merged into that branch, not on master.
• Periodically (automatically) merge master into it.
• We use that branch to build docs.gitlab.com/dev which will be the development version.