Clearly define which content should be in the separate Handbook project
Problem
We are preparing to move the handbook content into it's own Middleman project as part of the www-gitlab-com monorepo refactor.
Most handbook content are currently located in the /handbook/ namespace of the website, however there are some content that don't reside in this namespace that are a grey area where we need to make clear whether to include it into the handbook project or not.
Proposal
The projects currently considered for the monorepo are:
- Website (will contain all content not covered by the other projects in the repo)
- Blog - all content under
/blog/ - Handbook - all content under
/handbook/ - Jobs - all content under
/jobs/ - Product - various areas of content (see table below)
The only content in the repo that sits outside of the above and should be considered for inclusion into the handbook is the job families (/job-families/). I propose we move job families to the /handbook/hiring/job-families/ section and formally make it part of the handbook.
All other content in the repo have a logical project it belongs to as per the above projects, but for the sake of explicitly defining the below tables lists all the top level directories of the repo and its associated project in the monorepo structure.
| Top level content | Project |
|---|---|
| 20-years-open-source | Website |
| 2020-devsecops-survey | Website |
| DIY-DevOps | Website |
| agile-delivery | Website |
| analysts | Website |
| application-security | Website |
| blog | Blog |
| ci-cd | Website |
| cloud-native | Website |
| community | Website |
| company | Website |
| compare | Website |
| concurrent-devops | Website |
| customer-care | Website |
| customers | Website |
| demo | Website |
| demo-leader | Website |
| developer-survey | Website |
| devops | Website |
| devops-tools | Website |
| digital-transformation | Website |
| direction | Product |
| events | Website |
| experiments | Website |
| features | Product |
| forms | Website |
| free-trial | Website |
| gdpr | Website |
| get-help | Website |
| get-started | Website |
| gitlab-hosted | Website |
| handbook | Handbook |
| install | Website |
| is-it-any-good | Website |
| job-families | Handbook |
| jobs | Jobs |
| just-commit | Website |
| multicloud | Website |
| ops | Website |
| partners | Website |
| pdfs | Website |
| posts | Blog |
| press | Website |
| pricing | Website |
| privacy | Website |
| products | Website |
| releases | Product |
| renewals | Website |
| resellers | Website |
| resources | Website |
| roi | Website |
| salary | Handbook |
| sales | Website |
| search | Website |
| security | Website (uses handbook layout) |
| services | Website |
| simplify-devops | Website |
| single-application | Website |
| solutions | Website |
| stages-devops-lifecycle | Website |
| submit-feedback | Website |
| support | Website |
| templates | Website |
| terms | Website |
| thank-you-for-registering | Website |
| topics | Website |
| training | Website |
| upcoming-releases | Website |
| update | Website |
| upgrade | Website |
| upgrade-to-package-repository | Website |
| video | Website |
| webcast | Website |
| what-is-gitlab | Website |
| why | Website |