| Order | Section | Total Pages | Markdown | ERB | Start | Finish | Status |
|---|---|---|---|---|---|---|---|
| 1 | Job Families | 408 | 408 | 0 | 2023-03-28 | 2023-03-31 | Completed |
| 2 | TeamOps | 7 | 0 | 7 | 2023-04-19 | 2023-04-21 | Completed |
| 3 | Company Handbook Content | 52 | 49 | 3 | 2023-05-02 | 2023-05-12 | In-Progress |
| 4 | Tools and Tips | 12 | 12 | 0 | 2023-05-16 | 2023-05-19 | Scheduled |
| 5 | Engineering | 1144 | 574 | 547 | 2023-06-06 | 2023-02-16 | Planning |
| 6 | Infrastructure Standards | 21 | 21 | 0 | 2023-06-06 | 2023-06-09 | Scheduled |
| 7 | IT Self Service | 12 | 12 | 0 | 2023-06-27 | 2023-06-30 | Scheduled |
| 8 | Company | 265 | 200 | 53 | 2023-07-25 | 2023-07-28 | Planning |
| 9 | CoST Team Pages | 14 | 12 | 2 | 2023-08-15 | 2023-08-18 | Scheduled |
| 10 | Security | 153 | 148 | 3 | 2023-09-05 | 2023-09-08 | |
| 11 | Finance | 83 | 67 | 16 | 2023-09-26 | 2023-09-29 | |
| 12 | People Group | 199 | 180 | 18 | 2023-10-17 | 2023-10-20 | |
| 13 | Marketing | 415 | 423 | 44 | 2023-11-14 | 2023-11-17 | |
| 14 | Sales | 471 | 423 | 44 | 2023-12-05 | 2023-12-08 | |
| 15 | Legal | 67 | 67 | 0 | 2024-01-16 | 2024-01-19 | |
| 16 | Product | 414 | 351 | 64 | 2024-03-05 | 2024-03-15 |
Scheduled - This content will be migrated on the start date indicated Planning - This content is in the planning stages of its migration and the start and finish dates are guides only In Progress - This content is in the process of being migrated Completed - This content has already been migrated to the new handbook Blank - This content has provisional start and completion dates but are subject to change
We are providing a Google Calendar with all the dates for the migration in. This also includes public holidays and notable dates for the US and UK and other dates important to the migration team.
If the above iFrame is blank you can also access the Calendar Directly.
The order is based largely on the table of contents for the handbook but its been weighted slightly so that those sections with lots of Ruby Template files (erb) are pushed to the bottom of the list. The idea is that content which is easier to move is the content which moves first. This will give more time for those teams who are using ruby templating to move their content to markdown. Where content can't be easily moved to Markdown this will give the Handbook team time to work with teams to find and develop solutions to meet their needs.
We also hope to run in parallel the migration of the Engineering content from the existing handbook to the new handbook which we hope will reduce the time it takes to migrate all of the content from www-gitlab-com. If we are unable to do this we'll still migrate engineering after Company Handbook Content.
This is the order we have identified to migrate content but it is subject to change based on factors such as operational need and how smooth the migration goes for each section. We won't hesitate to bring forward a migration date if the current piece of content has moved smoothly and quickly. We'll also communicate changes in #whats-happening-at-gitlab and #handbook on Slack.
**What are we moving: ** Company Handbook Content
Target Date: 2nd - 12th May 2023
This is content is at the start of the Handbooks Table of Contents. Its a collection of smaller sections of the handbook that are widely referenced by other sections of the handbook. The team responsible for the handbook and its migration sit within the Chief of Staff Team (CoST) so this represented a good opportunity to dogfood the migration.
The following content has been earmarked as the next content to move. This will be done as a series of small merge requests over the course of a week or so before the end of April.
/sites/handbook/source/handbook/values/sites/handbook/source/handbook/only-healthy-constraints/site/handbook/source/handbook/documentation/sites/handbook/source/handbook/being-a-public-company/sites/handbook/source/handbook/communications/sites/handbook/source/handbook/about/sites/handbook/source/handbook/faq-gitlab-licensing-technology-to-independent-chinese-company /sites/handbook/source/handbook/key-review/sites/handbook/source/handbook/group-conversations//sites/handbook/source/handbook/e-group-weekly/sites/handbook/source/handbook/environmental-sustainability/sites/handbook/source/handbook/content-websites-responsibility/sites/handbook/source/handbook/inspired-by-gitlab//sites/handbook/source/handbook/about/sites/handbook/source/handbook/handbook-usage/sites/handbook/source/handbook/practical-handbook-edits/sites/handbook/source/handbook/using-gitlab-at-gitlab/sites/handbook/source/handbook/style-guideWe hope to do this as a series of small MRs over the course of a week. Each of these sections is typically only a page or two. So we shall one small section at a time over the course of 4 days. Each move is a pair of MRs. One brings the content over to the new handbook while the other removes the content from www-gitlab-com and sets up a redirect to the new content.
If you have any questions about this please feel free to ask in #handbook on Slack or reach out directly to @jamiemaynard.
Completion Date: 31st March 2023
Content to move:
Completion Date: 21st April 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Finish Date: 12th May 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: 16th May 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: End of June 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: End of June 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: End of July 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: End of August 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: End of September 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: End of September 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: End of October 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: End of November 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: End of December 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: End of January 2024
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: End of February 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Expected Date: End of March 2023
Content to move:
A full breakdown of this sections content files can be viewed on our Migration details page
Target Date: End of Q2 2023
The contents of the www-gitlab-com data directory is a Source of Truth in its own right. It is shared by a number of functions of the www-gitlab-com repository as well as the internal-handbook, digital-experience and the new handbook . This represents a significant dependency for all these repositories and the content they drive.
Like the refactor of www-gitlab-com refactoring data will allow this dependency to have a single DRI and provide a single place where all repositories which depend on this data to call on. Data will be benefit from faster pipelines and changes to data can quickly propagated to those repositories that depend on them.
This is currently in the planning stages and we'll share more as soon as we can.