Skip to content
Snippets Groups Projects
Verified Commit 9b5eccc2 authored by Ian Pedowitz's avatar Ian Pedowitz :beach:
Browse files

Fixing more formatting issues caused by the handbook migration

parent 4143eb32
No related branches found
No related tags found
1 merge request!7507Fixing more formatting issues caused by the handbook migration
Showing
with 39 additions and 50 deletions
......@@ -5,9 +5,9 @@ description: "Manage Snowflake Permissions"
## Quick Links
[Permifrost Project](https://gitlab.com/gitlab-data/permifrost/){:.btn .btn-purple-inv}
[Permifrost Project](https://gitlab.com/gitlab-data/permifrost/)
[PyPI](https://pypi.org/project/permifrost/){:.btn .btn-purple-inv}
[PyPI](https://pypi.org/project/permifrost/)
## Permifrost
......
......@@ -258,7 +258,7 @@ Anyone in the world (yes, this includes those who are not employed by GitLab) ma
## How does a company create their own handbook?
![GitLab all-remote team](https://about.gitlab.com/images/all-remote/gitlab-com-all-remote-v4-dark-1280x270.png){: .shadow.medium.center}
![GitLab all-remote team](https://about.gitlab.com/images/all-remote/gitlab-com-all-remote-v4-dark-1280x270.png)
Learn more in GitLab's [Handbook-First Documentation guide](/handbook/company/culture/all-remote/handbook-first/#tools-for-building-a-handbook) about how GitLab (the company) uses GitLab (the product) to build and maintain its handbook, as well as tools and tips for other companies who wish to start their own.
......@@ -281,7 +281,7 @@ See below for an A/B comparison of how an inward-facing GitLab *handbook* page i
## Design and illustration assets
![GitLab all-remote team](https://about.gitlab.com/images/all-remote/GitLab-All-Remote-Zoom-Team-Tanuki.jpg){: .shadow.medium.center}
![GitLab all-remote team](https://about.gitlab.com/images/all-remote/GitLab-All-Remote-Zoom-Team-Tanuki.jpg)
GitLab's [Brand and Digital Design](/handbook/marketing/digital-experience/) team are building out images and illustrations to visualize all-remote.
......@@ -349,7 +349,7 @@ The audience we aim to reach with our all-remote and workplace initiatives is bo
## Key Messages for All-Remote and Workplace
![GitLab all-remote computer](https://about.gitlab.com/images/all-remote/GitLab-All-Remote-Learning-Computer.jpg){: .shadow.medium.center}
![GitLab all-remote computer](https://about.gitlab.com/images/all-remote/GitLab-All-Remote-Learning-Computer.jpg)
### GitLab: The Remote Strategy
......@@ -400,7 +400,7 @@ Field Marketing will look up account ownership in SFDC (Salesforce.com) and make
## Channels
![GitLab all-remote illustration](https://about.gitlab.com/images/all-remote/gitlab-all-remote-v1-opengraph-social-1200x630.jpg){: .shadow.medium.center}
![GitLab all-remote illustration](https://about.gitlab.com/images/all-remote/gitlab-all-remote-v1-opengraph-social-1200x630.jpg)
### Web
......
......@@ -178,7 +178,7 @@ Consider also using the [Giphy](https://slack.com/help/articles/204714258-Giphy-
{{% cardpane %}}
{{% card footer="GitLab marketing talent show" %}}
![GitLab marketing talent show](/images/all-remote/gitlab-marketing-talent-show.jpg){: .shadow.medium.center}
![GitLab marketing talent show](/images/all-remote/gitlab-marketing-talent-show.jpg)
{{% /card %}}
{{% /cardpane %}}
......@@ -357,7 +357,7 @@ Hosting an [AMA](learning-and-development/#ask-me-anything-ama-group-conversatio
{{% cardpane %}}
{{% card footer="A bit of Airplane! fun on Halloween" %}}
![A bit of Airplane! fun on Halloween](/images/all-remote/GitLab-Halloween-2019-Costume-Zoom-Call.jpg){: .shadow.medium.center}
![A bit of Airplane! fun on Halloween](/images/all-remote/GitLab-Halloween-2019-Costume-Zoom-Call.jpg)
{{% /card %}}
{{% /cardpane %}}
......@@ -378,7 +378,7 @@ You can now bring peers or colleagues into online game shows through platforms l
{{% cardpane %}}
{{% card footer="Cheers to a fantastic team" %}}
![Cheers to a fantastic team](/images/all-remote/gitlab-zoom-happy-hour.jpg){: .shadow.medium.center}
![Cheers to a fantastic team](/images/all-remote/gitlab-zoom-happy-hour.jpg)
{{% /card %}}
{{% /cardpane %}}
......@@ -392,7 +392,7 @@ Sharing a meal is a powerful way to connect as humans, particularly when you ope
{{% cardpane %}}
{{% card footer="Virtual scavenger hunt at GitLab" %}}
![Virtual scavenger hunt](/images/blogimages/cs-scavenger-hunt/hugo.jpg){: .shadow.medium.center}
![Virtual scavenger hunt](/images/blogimages/cs-scavenger-hunt/hugo.jpg)
{{% /card %}}
{{% /cardpane %}}
......
......@@ -148,7 +148,6 @@ For a better understanding of the nuances, take a look at "[6 People Who Prove Y
## Remote work communities and networking
![GitLab collaboration](/images/all-remote/gitlab-collaboration.jpg)
{: .medium.center}
Staying [connected](events/) with remote workers globally is in many ways much easier than staying connected with peers through in-person networking events. Working remotely forces you to be [intentional about everything](management/), and the same is true for forming and fostering relationships and becoming part of one or more remote work communities.
......
......@@ -8,7 +8,7 @@ twitter_site: "@gitlab"
twitter_creator: "@gitlab"
---
![GitLab customer path](/images/all-remote/gitlab-customer-path.jpg){: .medium.center}
![GitLab customer path](/images/all-remote/gitlab-customer-path.jpg)
On this page, we're detailing what life can look and feel like when embracing a non-linear workday, paired with suggestions on catalyzing your imagination to consider possibilities that simply are not possible in a colocated, synchronous workplace.
......
......@@ -79,7 +79,7 @@ For those looking for a somewhat more stable version of the continual road trip,
{{% cardpane %}}
{{% card footer="Working at GitLab Commit London 2019" %}}
![Working at GitLab Commit London 2019](/images/all-remote/gitlab-commit-london-coworking-2019.jpg){: .shadow.medium.center}
![Working at GitLab Commit London 2019](/images/all-remote/gitlab-commit-london-coworking-2019.jpg)
{{% /card %}}
{{% /cardpane %}}
......
......@@ -14,9 +14,9 @@ title: Airflow Single-Engineer Group
| Date | Tl;DW; | Video |
|------------|-----------------------------------------------------------|--------------------------------------------------------------------------------|
| 2023-01-12 | DAG overview page is now pretty | [https://youtu.be/E3_YGF7Wr2k](https://youtu.be/E3_YGF7Wr2k){:target="_blank"} |
| 2023-01-05 | Developed the first Airflow page with an overview of Dags | [https://youtu.be/oFs4OsHZfRw](https://youtu.be/oFs4OsHZfRw){:target="_blank"} |
| 2022-12-21 | First video that started this SEG | [https://youtu.be/Jrjp6_rdDo4](https://youtu.be/Jrjp6_rdDo4){:target="_blank"} |
| 2023-01-12 | DAG overview page is now pretty | [https://youtu.be/E3_YGF7Wr2k](https://youtu.be/E3_YGF7Wr2k) |
| 2023-01-05 | Developed the first Airflow page with an overview of Dags | [https://youtu.be/oFs4OsHZfRw](https://youtu.be/oFs4OsHZfRw) |
| 2022-12-21 | First video that started this SEG | [https://youtu.be/Jrjp6_rdDo4](https://youtu.be/Jrjp6_rdDo4) |
## Apache Airflow
......
......@@ -18,11 +18,11 @@ Low-code and no-code are [two distinct concepts](https://lowcode.com/articles/lo
| Date | Summary | Video |
|------------|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
| 2023-02-01 | [Showcase #1](https://docs.google.com/presentation/d/1uU7wEd0E0hOxdK-TfR1a3OmzNOHHkzRnQ84hiTcIejQ/) | [https://youtu.be/7RQreQQk1NY](https://youtu.be/7RQreQQk1NY){:target="_blank"} |
| 2022-12-17 | [Visual Workflow Builder POC](https://gitlab.com/gitlab-org/incubation-engineering/no-code-low-code/meta/-/issues/25) | [https://youtu.be/DI-IcY6vm6g](https://youtu.be/DI-IcY6vm6g){:target="_blank"} |
| 2022-11-28 | [Automation UX POC](https://gitlab.com/gitlab-org/incubation-engineering/no-code-low-code/meta/-/issues/24) | [https://youtu.be/w-dGDBlIr0Y](https://youtu.be/w-dGDBlIr0Y){:target="_blank"} |
| 2022-10-31 | [Workflow Automation MVC](https://gitlab.com/gitlab-org/incubation-engineering/no-code-low-code/meta/-/issues/23) | [https://youtu.be/L_pvpjtYdLk](https://youtu.be/L_pvpjtYdLk){:target="_blank"} |
| 2022-10-24 | [Introduce low-code/no-code SEG](https://gitlab.com/gitlab-org/incubation-engineering/no-code-low-code/meta/-/issues/22) | [https://youtu.be/r3Ib00Z5Dj0](https://youtu.be/r3Ib00Z5Dj0){:target="_blank"} |
| 2023-02-01 | [Showcase #1](https://docs.google.com/presentation/d/1uU7wEd0E0hOxdK-TfR1a3OmzNOHHkzRnQ84hiTcIejQ/) | [https://youtu.be/7RQreQQk1NY](https://youtu.be/7RQreQQk1NY) |
| 2022-12-17 | [Visual Workflow Builder POC](https://gitlab.com/gitlab-org/incubation-engineering/no-code-low-code/meta/-/issues/25) | [https://youtu.be/DI-IcY6vm6g](https://youtu.be/DI-IcY6vm6g) |
| 2022-11-28 | [Automation UX POC](https://gitlab.com/gitlab-org/incubation-engineering/no-code-low-code/meta/-/issues/24) | [https://youtu.be/w-dGDBlIr0Y](https://youtu.be/w-dGDBlIr0Y) |
| 2022-10-31 | [Workflow Automation MVC](https://gitlab.com/gitlab-org/incubation-engineering/no-code-low-code/meta/-/issues/23) | [https://youtu.be/L_pvpjtYdLk](https://youtu.be/L_pvpjtYdLk) |
| 2022-10-24 | [Introduce low-code/no-code SEG](https://gitlab.com/gitlab-org/incubation-engineering/no-code-low-code/meta/-/issues/22) | [https://youtu.be/r3Ib00Z5Dj0](https://youtu.be/r3Ib00Z5Dj0) |
### No-code (current focus)
......
......@@ -53,15 +53,15 @@ The most recent weekly update for the Server Runtime SEG can be found at:
| Date | Tl;DR; | Video |
|------------|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
| 2022-12-23 | GitLab Agent - Making changes to workspace state from the UI and k8s | [https://youtu.be/nCIusZfxufo](https://youtu.be/nCIusZfxufo){:target="_blank"} |
| 2022-12-16 | GitLab Agent - A demo of using Python and Jupyter with SR4GA4K | [https://youtu.be/lQK_3xTb55U](https://youtu.be/lQK_3xTb55U){:target="_blank"} |
| 2022-12-12 | GitLab Agent - Rails UI, Authentication, Repository cloning | [https://youtu.be/jxHFOeg9gAw](https://youtu.be/jxHFOeg9gAw){:target="_blank"} |
| 2022-11-29 | GitLab Agent - Started porting server runtime. Support for HTTPS | [https://youtu.be/-E8wJZsYnbM](https://youtu.be/-E8wJZsYnbM){:target="_blank"} |
| 2022-11-16 | Custom Control Plane - Adding Rails UI and connecting to the GDK | [https://youtu.be/wyZbbrCBk6A](https://youtu.be/wyZbbrCBk6A){:target="_blank"} |
| 2022-11-02 | Custom Control Plane - Adding Devfile support, support for SSH authn and authz | [https://youtu.be/f_jfwh4v_q0](https://youtu.be/f_jfwh4v_q0){:target="_blank"} |
| 2022-10-26 | Custom Control Plane - Documentation updates, support for GCP DNS, IDE selection | [https://youtu.be/JIGNEqpdI7k](https://youtu.be/JIGNEqpdI7k){:target="_blank"} |
| 2022-10-19 | Custom Control Plane - Adding Authentication, opening ports, attaching volumes | [https://youtu.be/GFM0xK7Hz_I](https://youtu.be/GFM0xK7Hz_I){:target="_blank"} |
| 2022-10-12 | What is server runtime. Starting work on the custom control plane. | [https://youtu.be/yrhJo_wUuIM](https://youtu.be/yrhJo_wUuIM){:target="_blank"} |
| 2022-12-23 | GitLab Agent - Making changes to workspace state from the UI and k8s | [https://youtu.be/nCIusZfxufo](https://youtu.be/nCIusZfxufo) |
| 2022-12-16 | GitLab Agent - A demo of using Python and Jupyter with SR4GA4K | [https://youtu.be/lQK_3xTb55U](https://youtu.be/lQK_3xTb55U) |
| 2022-12-12 | GitLab Agent - Rails UI, Authentication, Repository cloning | [https://youtu.be/jxHFOeg9gAw](https://youtu.be/jxHFOeg9gAw) |
| 2022-11-29 | GitLab Agent - Started porting server runtime. Support for HTTPS | [https://youtu.be/-E8wJZsYnbM](https://youtu.be/-E8wJZsYnbM) |
| 2022-11-16 | Custom Control Plane - Adding Rails UI and connecting to the GDK | [https://youtu.be/wyZbbrCBk6A](https://youtu.be/wyZbbrCBk6A) |
| 2022-11-02 | Custom Control Plane - Adding Devfile support, support for SSH authn and authz | [https://youtu.be/f_jfwh4v_q0](https://youtu.be/f_jfwh4v_q0) |
| 2022-10-26 | Custom Control Plane - Documentation updates, support for GCP DNS, IDE selection | [https://youtu.be/JIGNEqpdI7k](https://youtu.be/JIGNEqpdI7k) |
| 2022-10-19 | Custom Control Plane - Adding Authentication, opening ports, attaching volumes | [https://youtu.be/GFM0xK7Hz_I](https://youtu.be/GFM0xK7Hz_I) |
| 2022-10-12 | What is server runtime. Starting work on the custom control plane. | [https://youtu.be/yrhJo_wUuIM](https://youtu.be/yrhJo_wUuIM) |
## Server Runtime Architecture
......
......@@ -8,13 +8,10 @@ description: "GitLab Cost Management"
## Quick Links
[Infrafin Board](https://gitlab.com/groups/gitlab-com/-/boards/1502173?label_name%5B%5D=infrafin)
{:.btn .btn-purple}
[Cost Management Epic](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/103)
{:.btn .btn-purple}
[Dashboards](https://app.periscopedata.com/app/gitlab/topic/infrafin/abf4ddd16c954c2d9362f8af28a1be8b)
{:.btn .btn-purple}
## Mission
......
......@@ -8,10 +8,8 @@ description: "Group Cost Metrics"
## Overview
[Group Cost Metrics SSOT](https://app.periscopedata.com/app/gitlab/744908/Group-GCP-Cost-PI's)
{:.btn .btn-purple}
[How to Engage](/handbook/engineering/infrastructure/cost-management/how-to-engage)
{:.btn .btn-purple}
We maintain a set of base level cost metrics for groups to use in Periscope in this [Dashboard](https://app.periscopedata.com/app/gitlab/744908/Infrafin-Base-Cost-Metric-SSOT---Groups). These are created in conjunction with a strict definition that explains what is and is not included in the metric, so understanding the definition is crucial to understanding the metric itself.
......
......@@ -4,10 +4,8 @@ description: "How to Engage with Infrastructure Analyst"
---
[Infrafin Board](https://gitlab.com/groups/gitlab-com/-/boards/1502173?label_name%5B%5D=infrafin)
{:.btn .btn-purple}
[#infrafin slack channel](https://gitlab.slack.com/messages/infrafin/)
{:.btn .btn-purple}
## Overview
......
......@@ -6,7 +6,6 @@ description: "Infra Analyst Workflow Planning"
---
[Workflow Board](https://gitlab.com/gitlab-com/www-gitlab-com/-/boards/1942495?label_name[]=Engineering%20Metrics)
{:.btn .btn-purple}
## Criteria
......
......@@ -7,8 +7,8 @@ description: "Learn about the various aspects of Cost Management"
## Vendor Specific Learning
[GCP](/handbook/engineering/infrastructure/cost-management/learning/gcp){:.btn .btn-purple}
[AWS](/handbook/engineering/infrastructure/cost-management/learning/aws){:.btn .btn-purple}
[GCP](/handbook/engineering/infrastructure/cost-management/learning/gcp)
[AWS](/handbook/engineering/infrastructure/cost-management/learning/aws)
### Cloud Cost Buckets
......
......@@ -170,7 +170,6 @@ After triaging failed tests, possible follow up actions are:
Your priority is to make sure we have an issue for each failure, and to communicate the status of its investigation and resolution. When there are multiple failures to report, consider their impact when deciding which to report first. See the [pipeline triage responsibilities](/handbook/engineering/infrastructure/test-platform/oncall-rotation/#responsibility) for further guidance.
If there are multiple failures we recommend that you identify whether each one is new or old (and therefore already has an issue open for it). For each new failure, open an issue that includes only the required information. Once you have opened an issue for each new failure you can investigate each more thoroughly and act on them appropriately, as described in later sections.
{: name="known-failures"}
The reason for reporting all new failures first is to allow faster discovery by engineers who might find the test failing in their own merge request test pipeline. If there is no open issue about that failure, the engineer will have to spend time trying to figure out if their changes caused it.
......@@ -187,7 +186,6 @@ Known failures should be linked to the current [pipeline triage report](https://
1. If the issue has already been reported please use the existing issue to track the latest status.
1. If there is no existing issue for the failure, please create an issue using one of [classification labels](#classify-and-triage-the-test-failure) via the steps below.
{: name="linking-issue"}
In the relevant Slack channel:
1. Apply the :eyes: emoji to indicate that you're investigating the failure(s).
......
......@@ -103,7 +103,7 @@ We staff our department with the following gearing ratios:
1. Self-manage & Reference Architecture impact
1. Must work areas
1. Development and UX facets (number of Engineers, SUS issues)
- For more information, please see the [SET Gearing Prioritization Model for more (GitLab Only)](https://docs.google.com/spreadsheets/d/e/2PACX-1vRM5jmGgT5H1kDOi6UwHTbK7PnoPYTYATnLe5HgVkJqe2VvaWo9fKpbnB6gR4vhx3UDby4wUeGwPYEq/pubhtml?gid=2059771943&single=true){:target="_blank"}. With these adjustments, we would be at ~85% of the 1:1 ratio to every product group.
- For more information, please see the [SET Gearing Prioritization Model for more (GitLab Only)](https://docs.google.com/spreadsheets/d/e/2PACX-1vRM5jmGgT5H1kDOi6UwHTbK7PnoPYTYATnLe5HgVkJqe2VvaWo9fKpbnB6gR4vhx3UDby4wUeGwPYEq/pubhtml?gid=2059771943&single=true). With these adjustments, we would be at ~85% of the 1:1 ratio to every product group.
- Product groups with high complexity may need more than one SET.
- Newly formed product groups may not have an allocated SET. They may be allocated one in the future.
- Secondary Ratio: Approximately a 1:8 ratio of Software Engineer in Test to Development Department Engineers.
......
......@@ -27,7 +27,7 @@ Create a merge request with the introductory changes *after the previous post ha
1. Confirm that "Delete source branch when merge request is accepted" is selected.
1. Use the release post template for your MR.
![release post MR template](release-post-mr-template.png){:.shadow}
![release post MR template](release-post-mr-template.png)
Now that you have created the release post MR, refer to the checklist in the MR for each action that you need to take and the due dates of each action. Keep in mind the MRs for usability improvements, bugs, and performance improvements have their own checklists to be completed, including a task for the Release Post Manager to merge these MR by the 17th prior to final content assembly.
......
......@@ -68,7 +68,7 @@ Creating a nice look when recording with a green screen requires soft, even ligh
- It is highly recommended to use diffusion sheets with pins as an excellent way to soften the light and create a more even look. You can use the pins to clip the diffusion sheet to the doors of the panel light.
- To light your subject, place the final panel light behind your camera, raised nearly to the ceiling. It can be directed at your subject (using diffusion) or, in some cases, simply faced towards the ceiling and turned to full intensity.
![Green Screen set up diagram](/images/digital-production/green-screen-setup_mvc1.png){: .shadow.medium.center}
![Green Screen set up diagram](/images/digital-production/green-screen-setup_mvc1.png)
<sub>
1. Subject
......
......@@ -9,7 +9,7 @@ twitter_creator: "@gitlab"
## Introduction
![GitLab collaboration illustration](/images/all-remote/gitlab-collaboration.jpg){: .medium.center}
![GitLab collaboration illustration](/images/all-remote/gitlab-collaboration.jpg)
The [GitLab.tv All-Remote Channel](https://www.youtube.com/playlist?list=PLFGfElNsQthY6t1i0UXYr0wFW3DuvWww6) provides guidance and information to business owners, executives and managers on the ways in which they can transition to a remote workforce. Our audience of founders, CROs, CXOs, HR leaders, and managers work in all industries, particularly in tech and enterprise to midsize companies. For additional context, visit the GitLab [All-Remote Marketing Handbook](/handbook/ceo/office-of-the-ceo/workplace/).
......@@ -37,7 +37,7 @@ Everyone can contribute content to the All-Remote Channel provided it follows th
## Audience
![GitLab customer illustration](/images/all-remote/gitlab-customer-path.jpg){: .medium.center}
![GitLab customer illustration](/images/all-remote/gitlab-customer-path.jpg)
The [GitLab.tv All-Remote Channel](https://www.youtube.com/playlist?list=PLFGfElNsQthY6t1i0UXYr0wFW3DuvWww6) informs business leaders and stakeholders about the various aspects of implementing and managing remote teams. For the purposes of this channel, we split the audience into two groups:
......@@ -46,7 +46,7 @@ The [GitLab.tv All-Remote Channel](https://www.youtube.com/playlist?list=PLFGfEl
## Content Types and Guidelines
![GitLab values illustration](/images/all-remote/gitlab-values-tanukis.jpg){: .medium.center}
![GitLab values illustration](/images/all-remote/gitlab-values-tanukis.jpg)
To keep the All-Remote Channel focused on its intended [audience](/handbook/ceo/office-of-the-ceo/workplace/#our-audience), please adhere to the following content guidelines and content types. Specifically, we are looking for content that spotlights:
......@@ -80,7 +80,7 @@ Uploading criteria:
### How-To Videos
![GitLab journey illustration](/images/all-remote/gitlab-journey-and-navigation.jpg){: .medium.center}
![GitLab journey illustration](/images/all-remote/gitlab-journey-and-navigation.jpg)
All-remote how-to videos will provide viewers with quick, actionable tips on remote work. When creating a how-to video, remember to keep the video focused on a single action and outcome. The [all-remote audience](/handbook/ceo/office-of-the-ceo/workplace/#our-audience) tends to prefer presentation-style videos, so keep this in mind as you prepare your content. If you find yourself explaining how to do multiple things, consider breaking up the video down into smaller videos, with each video covering one aspect. As a general rule of thumb, try to keep how-to videos to under 10 minutes.
......
......@@ -67,7 +67,7 @@ From "[Setting up GitLab CI/CD for Android projects](https://about.gitlab.com/bl
### Forrester CI Wave
![Forrester CI Wave](/images/home/forrester-ci-wave-graphic.svg){: .small.left}
![Forrester CI Wave](/images/home/forrester-ci-wave-graphic.svg)
- No vendor can survive today by only doing CI
- Vendors in the CI space have all evolved to include CD, as it is a natural extension of the capabilities of a CI system
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment