Prepare CE and EE API docs for being sourced from single repo
We currently have differing but similar API docs in /doc/api across ee and ce repos, currently served at https://docs.gitlab.com/ee/api/ * https://docs.gitlab.com/ce/api/. Some api endpoints are only in EE, others exist across both but have different available sets of parameters (and therefore different example responses). We are merging the CE and EE codebases so we will need to build both sets (or a single merged set) of API docs from the same repo.
Solutions under consideration:
We could start by pulling both sets of docs into the same repo, stored at:
It would be optimal to merge these two sets. This can happen before GitLab deprecates the ce and ee repos if there is sufficient time. Or perhaps additional MVC work, other than the above move.
There was a proposed MVC of merging the pages and showing two response examples where the responses differ, but this is not a good experience. Ideally our MVC would be to show a tabbed view with a single toggle on the page, or where clicking any tabs changes all the tabs on the page. Short of this, we should leave /ce/api and /ee/api as they are upon the kickoff of building from the single repo, and plan such merges for afterward.