This is a guide on what you'll need to install and run on your machine so you can make edits locally. This is quicker than in the web interface and allows you a better overview and preview when making complex changes.
Once you're set up, you will find the source files for the Handbook here /source/handbook/
1. Help is available for team members
If you work for GitLab Inc., we don't expect you to figure this out by yourself.
If you have questions, ask anyone for help. You're more likely to have success with:
People that have been here longer than 3 months. The team page lists people in order of how long they have been here.
People that have 'engineer' in their title.
We encourage you to meet someone new by asking someone you don't know for help. You can also ask for help in #questions or #peopleops by posting 'Who can do a video call with me to help me work on the website locally /handbook/git-page-update/ ?'. If the other options don't work for you, please ask your onboarding buddy.
For more information about using Git and GitLab see GitLab University.
3. Install Git
Open a terminal.
Check your Git version by executing: git --version.
If Git is not installed, you should be prompted to install it. Follow this guide to installing Git and
linking your account to Git.
4. Install Ruby Version Manager (RVM)
Ruby Version Manager (RVM) is a command-line utility that allows you to easily install and switch between different versions of the Ruby programming language, which is used to build this website. It can be installed directly from a command prompt (e.g., in macOS Terminal) with the following command:
curl -sSL https://get.rvm.io | bash -s stable
Once RVM has been installed, ensure that your updated terminal environment has been loaded by closing your terminal window and opening a new one.
5. Install Ruby and Bundler
The version of Ruby that you'll need to build this website will change from time to time, but you can always check what version that is by looking at the contents of .ruby-version in the root of the www-gitlab-com directory. You can always check it on GitLab even if you haven't yet cloned your own local copy of the repository.
If .ruby-version specifies version 2.6.5, you can install it with RVM like so:
In a terminal, execute: rvm install 2.6.5 to install Ruby
(enter your system password if prompted).
Execute: rvm use 2.6.5 --default to set your default Ruby to 2.6.5.
Execute: ruby --version to verify Ruby is installed. You should see:
ruby 2.6.5p114 (2019-10-01 revision 67812).
6. Clone the source of the website and install its dependencies
If you set up SSH keys previously, in terminal execute: git clone git@gitlab.com:gitlab-com/www-gitlab-com.git to clone the website. If you prefer using https, then execute: git clone https://gitlab.com/gitlab-com/www-gitlab-com.git, but note that if you've activated 2FA on your GitLab.com account, you'll need to take some additional steps to set up personal access tokens. If you ever want to switch between SSH and https, execute git remote remove origin, followed by git remote add origin [..] where the [..] is the part that starts with git@ for SSH, or with https: for https.
Execute: cd www-gitlab-com to change to the www-gitlab-com directory.
Execute: bundle install to install all gem dependencies.
7. Prevent newlines from causing all following lines in a file to be tagged as changed
Git is able to automatically convert line endings between CRLF and LF and vice versa. Execute the following command to configure Git to convert CRLF to LF on commit but otherwise leave line endings alone:
git config --global core.autocrlf input
If you'd like to learn more about Git's formatting and whitespace options see the "Formatting and Whitespace" section under "Git Configuration" in "Pro Git".
8. Preview website changes locally
In a terminal, execute: bundle exec middleman --verbose.
Wait for the log line: == View your site at "http://localhost:4567", "http://127.0.0.1:4567".
You will need to install a text editor to edit the site locally. We recommend
Sublime Text 3 or Atom. Use command / ctrl P to quickly open the file you need.
Refresh your browser to see your changes.
9. Test if all URL links in a page are valid
Until this is automated in CI, a quick way to see if there are any invalid
links inside a page is the following.
Open the page you wish to preview (see previous step).
Click the newly installed extension in the upper right corner of Chrome.
A pop-up window will open and tell you how many links, if any, are invalid.
Fix any invalid links and ideally any warnings, commit and push your changes,
and test again.
All internal links (links leading to other parts of the website) should be relative.
10. Start contributing
Most pages that you might want to edit are written in markdown Kramdown.
Read through our Markdown Guide to understand its syntax and create new content.
We are happy to have you join our company and to include you in our team page! Ask anyone in the company for
help if you need it. There are three ways to update the website. Choose the method below that feels most comfortable and have the following information handy:
On the Repository page, click on the button labeled Web IDE near the middle of the page next to History and Find File buttons.
In the file browser, navigate to source/images/team.
Click the ⋁ icon next to the team directory and choose upload file and choose the photo of yourself. Be sure to follow the picture requirements.
Next, navigate to data/team.yml in the file browser and click on it to open the editor.
Search for a placeholder entry with your first name and last initial or just first and last initial as X.Y. (note the lack of a space) and update your profile information (make sure you are searching within the file you want to edit by clicking on the file first). If you don't find the placeholder entry with your initials, look through placeholders named "New Vacancy" for your position title. Copy/paste another team member's entry if you don't have a placeholder. You can place your entry at the end of the page.
Change name to your FirstName LastName and slug to your name without spaces.
Verify your title.
If your position title is incorrect or not filled in, navigate to the job_families.yml and use command+F to search for your job title.
If present placeholder: true can be removed or left in (it does not affect visibility of your entry).
Verify reports_to lists your manager using the slug value from their team page entry.
If you are a manager, verify two extra things,
reports_to of your team member using your slug
reports_to of vacancies in your team using your slug
Change type to person or you will not appear on the interactive map.
Add the filename of your profile picture making sure to match exactly even letter case. Ensure to delete "../gitlab-logo-extra-whitespace.png", if present. Completed line should look like this "picture: yournameinlowercase.jpg".
Add your Twitter and GitLab handles without the leading @.
Add your pronouns.
Change your locality to your city and state, province, region.
Change country to your country.
Add your own story. Use other team member's stories as a reference.
If remote work has changed your life in a meaningful way, consider adding your own remote_story, using other team member remote stories as a reference.
Important: Do not use the tab character and respect the spaces between lines otherwise the page format will break. Note that referenced file names/extensions are case sensitive, and a file which is not found will cause a pipeline failure.
Once you have finished this, click the Commit button in the bottom left. It should say something like 2 unstaged and 0 staged changes. This will bring up a sidebar with an Unstaged and Staged area.
Check the files to ensure your updates are what you expect. If they are, click the check mark above the changed file list to "stage" all changes. You can also use the Stage button in the upper-right of the changed file view to stage each one individually. You should now see 0 unstaged and 2 staged changes.
Once you have verified all of the edits, click commit and enter a short commit message in the box that appears. Your commit message should describe what you have changed. Choose Create a new branch. Name the branch in the format of add-YOURNAME-to-team-page or similar. Tick the Start a new merge request checkbox. Then click Commit once more.
Fill out the merge request details and assign it to your manager. If your manager does not have access to merge your MR based on the permissions described above, then please reference the specific members page for the www-gitlab-com project for review. Check the Delete source branch when merge request is accepted box to cleanup your merge request when complete. Click Submit merge request to submit the MR for review.
Method 2: Add your info on GitLab.com using the 'web interface'
Click the + under the red line near the top of the screen.
Click New branch.
For Branch name, name it something unique (it's temporary so don't worry too much about the exact name) like Team-Page-Update-yourdepartment and click Create branch
Start by adding your image. Click on Repository on the left side then Files.
Click on source, then images, then team.
At the top of the page click + and choose Upload file to upload your picture. Be sure to follow the picture requirements. Add text Add YourFirstName YourLastName to team page and click Upload file.
Navigate on your branch near the top of the page following the text that has your unique branch name and click on the text that follows your branch name www-gitlab-com.
Now you will edit your biographical information. All the bio information displayed on the Team page is pulled from a data file. Click on data, and then scroll down to team.yml.
Click on edit on the top right side of your screen.
Search for a placeholder entry with your first name and last initial or just first and last initial as X.Y. (note the lack of a space) and update your profile information (make sure you are searching within the file you want to edit by clicking on the file first). If you don't find the placeholder entry with your initials, look through placeholders named "New Vacancy" for your position title. Copy/paste another team member's entry if you don't have a placeholder. You can place your entry at the end of the page.
Change name to your FirstName LastName and slug to your name without spaces.
Verify your title.
If your position title is incorrect or not filled in, navigate to the job_families.yml and use command+F to search for your job title.
If present placeholder: true can be removed or left in (it does not affect visibility of your entry).
Verify reports_to lists your manager using the slug value from their team page entry.
If you are a manager, verify two extra things,
reports_to of your team member using your slug
reports_to of vacancies in your team using your slug
Change type to person or you will not appear on the interactive map.
Add the filename of your profile picture making sure to match exactly even letter case. Ensure to delete "../gitlab-logo-extra-whitespace.png", if present. Completed line should look like this "picture: yournameinlowercase.jpg".
Add your Twitter and GitLab handles without the leading @.
Add your pronouns.
Change your locality to your city and state, province, region.
Change country to your country.
Add your own story. Use other team member's stories as a reference.
If remote work has changed your life in a meaningful way, consider adding your own remote_story, using other team member remote stories as a reference.
Important: Do not use the tab character and respect the spaces between lines otherwise the page format will break. Note that referenced file names/extensions are case sensitive, and a file which is not found will cause a pipeline failure.
After you added your information, add a comment to your commit and click on “Commit Changes”.
Create and checkout a new branch for the changes you will be making.
Add your picture to the source/images/team/ directory in the repository and git add it. Be sure to follow the picture requirements.
Open data/team.yml in your favorite editor.
Search for a placeholder entry with your first name and last initial or just first and last initial as X.Y. (note the lack of a space) and update your profile information (make sure you are searching within the file you want to edit by clicking on the file first). If you don't find the placeholder entry with your initials, look through placeholders named "New Vacancy" for your position title. Copy/paste another team member's entry if you don't have a placeholder. You can place your entry at the end of the page.
Change name to your FirstName LastName and slug to your name without spaces.
Verify your title.
If your position title is incorrect or not filled in, navigate to the job_families.yml and use command+F to search for your job title.
If present placeholder: true can be removed or left in (it does not affect visibility of your entry).
Verify reports_to lists your manager using the slug value from their team page entry.
If you are a manager, verify two extra things,
reports_to of your team member using your slug
reports_to of vacancies in your team using your slug
Change type to person or you will not appear on the interactive map.
Add the filename of your profile picture making sure to match exactly even letter case. Ensure to delete "../gitlab-logo-extra-whitespace.png", if present. Completed line should look like this "picture: yournameinlowercase.jpg".
Add your Twitter and GitLab handles without the leading @.
Add your pronouns.
Change your locality to your city and state, province, region.
Change country to your country.
Add your own story. Use other team member's stories as a reference.
If remote work has changed your life in a meaningful way, consider adding your own remote_story, using other team member remote stories as a reference.
Important: Do not use the tab character and respect the spaces between lines otherwise the page format will break. Note that referenced file names/extensions are case sensitive, and a file which is not found will cause a pipeline failure.
Save changes to data/team.yml and git add it.
To see your changes locally, follow the directions in README.md.
After validating your changes, commit your changes with a comment Add FirstName LastName to team page and push your branch.
Note: When you test locally, the map on top of the page won't show your photo. This is because it is not populated with local data. More about how the map works. You will see your picture on the map as soon as your Merge Request is merged.
Note: Searching the handbook in your local environment yields production results, so navigate directly to the team page via URL to see your changes.
Add your pet(s) to the Team Pets Page
Using what you learned in the steps above, consider adding your pet to the Team Pets page. You can follow these instructions for adding them via the Web IDE.
Again, find the picture that you'd like to add to the team pets page, and update the picture's name to the following format: petname.jpg or petname.png. Ensure the picture size is around 400x400 (it must be square, see picture requirements).
On the Repository page, you will see a Web IDE button near the middle of the page next to History and Find File buttons.
In the file browser, navigate to source/images/team/pets.
Click the ⋁ icon next to the pets directory and choose upload file and choose the photo you prepared in step 1.
Next, navigate to in the file browser data/pets.yml and click on it to open the editor.
Add your pet by following the format of the existing pets on the page (you can copy and paste their lines of code, even). Ensure that you include your pet's name, your full name, and the image you uploaded in step 1.
Once you have finished this, click the Commit button in the bottom left. It should say something like 2 unstaged and 0 staged changes. This will bring up a sidebar with an Unstaged and Staged area.
Check the file to ensure your updates are what you expect. If they are, click the check mark next to the filename to "stage" these changes.
Once you have verified all of the edits, click commit once more. Here, enter a short commit message including what you've changed. Choose Create a new branch and merge request. Choose a branch name of your choosing.
Fill out the merge request details and assign it to your manager for review.
12. Edit the Handbook
WebIDE, using the browser
The Web Integrated Development Environment (IDE) is used to make changes within the browser. This method requires no setup.
Find the handbook page to edit.
Click on the Edit this page button at the bottom of the page.
On the page, you should see the relevant file in the repository displayed. Click on the Web IDE button on the right side.
Edit the page using MarkDown. You can preview your changes (but links will not work).
Note: You can edit other pages by browsing through the filelist on the left side in the Web IDE.
After making your changes, click the Commit... button in the bottom left to review the list of changed files. Click on each file to review the changes and click the tick icon to stage the file.
Once you have staged some changes, you can add a commit message and commit the staged changes. The message should be as brief as possible, since it has a character limit. You can add more detail in the description in a subsequent step. Unstaged changes will not be committed.
Choose the option to create a new branch and create merge request. For your branch, use a descriptive name with hyphens and no spaces, so that you can find it again later, but it's temporary so don't worry too much about the exact name.
Submit and you will be taken to the merge request (MR) page.
Feel free to add a more detailed message in the description box. For the options, check Remove source branch.
Assign the MR to the Handbook Content Manager (or as instructed) for general handbook changes. If the content changes are specific to your team, assign the MR to your manager.
Locally, using the terminal
If you haven't already, follow steps 1-5 in the "Add yourself to the Team Page"'s "Add Locally (using the terminal)" section above. (This step is necessary as the handbook lives in the same repository as the rest of GitLab.com). If you're following this guide in order and have already added yourself to the team page, instead go back to the main branch (via git checkout master) and there create a new branch for your handbook edits.
The handbook lives under source/handbook. For the most part, you can locate the specific item to edit via that item's URL. For instance, this page is /handbook/git-page-update/ and its source lives in source/handbook/git-page-update/index.html.md.
Edit away! See the "Start Contributing" section, above, for details about the Markdown that most pages are written in.
Preview your changes locally by following the directions in README.md. Keep in mind that the local server won't auto-reload when you change a page, so you'll need to restart it to see what you've done.
Once you've made your changes and verified they appear the way you want them to, commit them with a comment and push your branch.
Marking a merge request as a Work in Progress (WIP)
You can easily prevent a merge request from being merged before you're ready by marking it as a work in progress. Simply type "WIP:" at the beginning of your merge request title (e.g. "WIP: My Handbook Change"). To merge once you're ready, edit your MR and remove "WIP:" from the title.
Note: Only mark a merge request as "WIP" (Work in Progress) if it will negatively affect the company if merged too early. That can be the case for application code but is almost never possible for handbook MRs.
Ready to merge
Handbook Merge Requests should have the branch set to delete.
It should not have commits set to squash.
We do not squash commits because of the possible negative effects.
Then assign the MR to a maintainer for review and merging.
How to solve a broken pipeline in a merge request
In the GitLab Unfiltered video above, two colleagues share their screens and walk through the process detailed below.
If you create a merge request during a period where there is an issue in master causing pipelines to fail, you'll notice that failures will continue to occur even if you retry pipeline within the GitLab Web IDE interface.
Once the issue in master is fixed, you can solve this by using terminal to merge the latest version of master into your branch (which you can find in your merge request).
For those who primarily use Web IDE to interface with GitLab, it can feel foreign to engage locally. Before diving in deeper, be sure to read our GitLab 101 – a primer for the non-technical blog post.
Once you are properly equipped to edit locally, open a terminal window and execute the following.
Navigate to the appropriate project. If you've cloned the project to your root directory, try cd www-gitlab-com
git checkout master
git pull (This brings in the most recent changes from master to your local machine.)
git checkout TK (Replace TK with your branch from the merge request. This is easily copied by clicking the Copy Branch Name icon to the right of Request to merge at the top of your merge request page.)
git merge master (This takes the changes from master and merges them into your local TK branch.)
:q (Entering :q followed by a Return keystroke quits vim which is the editor your terminal opened when adding the stock commit message to the merge.)
git push (This takes local machine files and pushes to the cloud.)
Once this has been executed, you'll see new commits added to your merge request, and the pipeline will automatically begin to re-run. If completed correctly, the pipeline will pass now that the latest master was merged into your branch.
If you are a GitLab team member and you get stuck, please ask for help in the #mr-buddies Slack channel.
Example video
Where should content go?
GitLab has a lot of places you can put web content including the website, blog, docs, and the handbook. Here's an overview of where you should create a merge request to add content.
blog: The blog is a great place to start. If you don't know where to put content, then write a blog post! Great blogs can always be then copied or modified for the website, docs, and handbook later. Blog posts are especially good for news, announcements, and current trends because blog posts are tied to a specific date.
website: This is the main marketing site for GitLab and where folks will tend to go first to find out information about GitLab (the product and the company). The website contains a broad set of content from product pages to customer case studies. The website is the best place for evergreen articles such as topic and solution pages since it's not tied to specific date.
docs: The docs are where are all technical information about GitLab self-managed and GitLab.com belongs. If the intended audience for the content is a user of GitLab then it should be in the docs. The docs are great place for both reference docs (what are the configurable settings for a feature, e.g. what can you do with issues) and narrative docs (how to do x with y, e.g. how to set up HA on AWS).
handbook: The handbook is for any content that needs to be used by GitLab team-members to do their job. If you put content on the blog, website, and docs, but you think it would be helpful for GitLab team-members to do their job then link to the content from the handbook.
Sometimes the lines are blurry and it can seem as though there are multiple places that would be a good fit. For example, "how to" articles make great blog posts, but could be more discoverable to users if they are in the docs. Just pick one. It's better to create content somewhere than nowhere. When in doubt, start with the blog.
