rebase

.github/workflows/hugo.yaml

@@ -36,8 +36,6 @@ jobs:
     steps:
       - name: Checkout the repo
         uses: actions/checkout@v2   
-      - name: download dependecies
-        run : ./scripts/sync-data.sh
       - name: Install Node.js dependencies
         run: npm i
       - name: Install Dart Sass

.gitignore

@@ -10,7 +10,7 @@
 /public
 /node_modules
 
-/data/public
+
 
 # Ignore code quality output
 markdownlint-cli2-codequality.json

.gitlab/CODEOWNERS

@@ -120,7 +120,7 @@
 /content/handbook/engineering/development/dev/create/ @dsatcher
 /content/handbook/engineering/development/dev/create/code-creation/ @mnohr
 /content/handbook/engineering/development/dev/create/editor-extensions.md @dashaadu @kisha.mavryck
-/content/handbook/engineering/development/dev/create/ide/ @oregand
+/content/handbook/engineering/development/dev/create/ide/ @adebayo_a
 /content/handbook/engineering/development/dev/manage/ @wortschi @m_gill @mksionek
 /content/handbook/engineering/development/dev/manage/foundations/ @samdbeckham @tauriedavis
 /content/handbook/engineering/development/dev/manage/import-and-integrate/ @wortschi

content/handbook/business-technology/data-team/how-we-work/new-data-source.md

@@ -169,7 +169,7 @@ When the execution could not continue due to the need of external intervention,
 
 ## Red Data
 
-Red data is not allowed to be stored in our Data Platform (Snowflake). Therefore we will not bring in/connect new data sources that are listed in the [tech stack](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) with `data_classification: Red` unless there is a mission critical business reason. There is an exception process available which will enable us to evaluate the needs on a case-by-case basis and this process will require approval from BT/Data VP-level, Security and Privacy. Evaluating the business reason and obtaining approvals are part of the triage process and are governed via the new data source [template](https://gitlab.com/gitlab-data/analytics/-/issues/new?issuable_template=[New%20Request]%20New%20Data%20Source).
+Red data (according to the GitLab [Data Classification Policy](/handbook/security/data-classification-standard/#data-classification-levels) is not allowed to be stored in our Data Platform (Snowflake). Therefore we will not bring in/connect new data sources that are listed in the [tech stack](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) with `data_classification: Red` unless there is a mission critical business reason. There is an exception process available which will enable us to evaluate the needs on a case-by-case basis and this process will require approval from BT/Data VP-level, Security and Privacy. Evaluating the business reason and obtaining approvals are part of the triage process and are governed via the new data source [template](https://gitlab.com/gitlab-data/analytics/-/issues/new?issuable_template=[New%20Request]%20New%20Data%20Source).
 
 **Note:** The exception process must be fulfilled to either **connect** a system with Red data and/or to **extract** Red data (fields) from that system.  However, the business case to extract Red data (fields) under the exception process will necessitate a higher standard of review than a business case that only requires connecting a Red data system without extraction of Red data (fields).  Where extraction of Red data (fields) is approved under the exception process, masking will be applied in the Data Platform (Snowflake) as described in the proceeding section.
 

content/handbook/business-technology/enterprise-applications/finsys-access-requests.md

@@ -20,7 +20,7 @@ This applies to the following systems:
 - Adaptive Insights
 - Avalara
 - Coupa
-- Expensify
+- Navan
 - NetSuite
 - Stripe
 - Zuora Billing
@@ -69,7 +69,7 @@ On top of the [GitLab Access Request](/handbook/business-technology/end-user-ser
 |                   | - Read-only company access                     |                   |
 |                   | - No access                    |                   |
 | Coupa | | Note: Requestors/buyers will always only get ***Custom User*** role. Elevated access requires Procurement approval.|
-| Expensify | AR should explicitly state the **Exact** role they are requesting access to **AND** which policies. | There are a lot of policies within Expensify. Typically the only ARs the team will get are for Expensify Admins. Team members are automatically provisioned.|
+| Navan | AR should explicitly state the **Exact** role they are requesting access to **AND** which policies. | There are a lot of policies within Navan. Typically the only ARs the team will get are for Navan Admins. Team members are automatically provisioned.|
 |           | |Since most of the ARs are for finance system admins, they will usually need access to all the policies in which case the team does not have to list out all the policies in the AR.|
 | NetSuite |AR should explicitly state the **Exact** NetSuite role that they are requesting before the Business Owner approves the AR. ||
 |Stripe | AR should explicitly state the **Exact** role they are requesting access to **AND** which Stripe Accounts:| Roles are not customizable.|  

content/handbook/business-technology/enterprise-applications/guides/finance-guides/bhrfinanceautomation.md

@@ -4,11 +4,11 @@ draft: true
 aliases: "/handbook/business-technology/enterprise-applications/guides/finance-guides/bhrfinanceautomation.html"
 ---
 
-- The integration is powered around the Policy Matrix, which determines how the employee’s user record in Expensify and NetSuite should be set up.
-   - Based on an Employee’s Location, Department and Currency, that will determine which NetSuite Subsidiary to assign them to and which Expensify Policy to add them to.
+- The integration is powered around the Policy Matrix, which determines how the employee’s user record in Navan and NetSuite should be set up.
+   - Based on an Employee’s Location, Department and Currency, that will determine which NetSuite Subsidiary to assign them to and which Navan Policy to add them to.
 - The integration is triggered by any new or updated employees in BambooHR.
-   - This could result in a job being run even if there isn’t a necessary change to the employee’s NetSuite or Expensify record, which is fine. It’s better that than missing an update.
-- Every ***Five*** minutes, the integration takes the new and updates employees and updates NetSuite and Expensify in that order.
+   - This could result in a job being run even if there isn’t a necessary change to the employee’s NetSuite or Navan record, which is fine. It’s better that than missing an update.
+- Every ***Five*** minutes, the integration takes the new and updates employees and updates NetSuite and Navan in that order.
 It will first validate that all the necessary data is there on the Employee record.
    - Necessary Data: Name, Email, Manager, Location, Currency, Department.
    - If any of that data is missing, job will stop and it will throw an error.
@@ -17,10 +17,10 @@ It will first validate that all the necessary data is there on the Employee reco
        - Will update Name, Email, Currency, Department and BHR ID
    - If Employee’s Subsidiary changes, a new vendor will be created and nothing will happen to the old vendor record.
       - Accounts Payable team will need to deactivate manually.
-- Once NetSuite is complete, it will then move onto Expensify.
-   - Based on an Employee’s Location, Department and Currency, that will determine which NetSuite Subsidiary to assign them to and which Expensify Policy to add them to.
-    - It will also evaluate the Employee’s manager details to determine if they need to also be added to the Expensify policy in order to approve their reportee’s expense reports.
-- If it is able to successfully action in NetSuite and Expensify then it will return a success, otherwise it will retry twice, if it still fails it will proceed to generate an error (see next section)
+- Once NetSuite is complete, it will then move onto Navan.
+   - Based on an Employee’s Location, Department and Currency, that will determine which NetSuite Subsidiary to assign them to and which Navan Policy to add them to.
+    - It will also evaluate the Employee’s manager details to determine if they need to also be added to the Navan policy in order to approve their reportee’s expense reports.
+- If it is able to successfully action in NetSuite and Navan then it will return a success, otherwise it will retry twice, if it still fails it will proceed to generate an error (see next section)
 
 # Error Handling:
 
@@ -34,8 +34,8 @@ It will first validate that all the necessary data is there on the Employee reco
 ### **BambooHR: Location Creation/Changes**
 
    - If the business decides to rename/repurpose an existing Location in BHR, the HR team should cc FinanceOps in the ticket, so the integration can be updated accordingly.
-      - If they don’t, the risk is a delay in updating and adding employees to Expensify and NetSuite, but they will be captured in the daily error log and actioned then.
+      - If they don’t, the risk is a delay in updating and adding employees to Navan and NetSuite, but they will be captured in the daily error log and actioned then.
 
-### **Expensify Policy Creation/Changes:**
+### **Navan Policy Creation/Changes:**
 
  Courtney Cote to notify the EntApps: FinSys team in their tickets, by CC’ing FinanceOps, so the integration can be updated accordingly. This is a proactive measure, so if it doesn’t happen then we’ll encounter more errors than usual.

content/handbook/communication/_index.md

@@ -1151,7 +1151,7 @@ There is a lot of information pertaining to Slack, as it is a critical part of G
 1. Everyone can contribute, and while opinions are important to provide perspective, we value [proposals](/handbook/values/#make-a-proposal) and [iteration](/handbook/values/#iteration). If the subject is of value to the wider community, consider commenting on an existing issue or opening a new [merge request](#start-with-a-merge-request) instead.
 1. Use the `:white_check_mark:` emoji or similar to indicate an inquiry has been answered. Anyone can add the emoji. If you're not sure, then feel free to leave it up to the person who asked. An emoji indicator is particularly helpful in channels where lots of questions are posted, such as `#questions`, and `#git-help`.
 1. In general, you can think of emoji reactions as equivalent to body-language responses we use in real-life conversations, such as nodding your head as encouragement when a verbal (or in Slack, written) response might be too much. However, please be aware that use and understanding of emoji, like body-language, is not universal. Others may not communicate via those means the same way that you do, particularly those who are Autistic or otherwise neurodivergent. If in doubt, you can use text to clarify.
-1. In public channels, [threads](https://get.slack.help/hc/en-us/articles/115000769927-Message-threads) are valuable for keeping conversations together. If you want to respond to a question or comment in a channel, please start a thread instead of responding below them in the channel. This helps to keep the discussion in one place where it is easy to follow, and reduces noise as each message in a thread does not result in an unread message for everyone in the channel.
+1. In both public and private channels, [threads](https://get.slack.help/hc/en-us/articles/115000769927-Message-threads) are valuable for keeping conversations together. If you want to respond to a question or comment in a channel, please start a thread instead of responding below them in the channel. This helps to keep the discussion in one place where it is easy to follow, and reduces noise as each message in a thread does not result in an unread message for everyone in the channel.
 1. Unless you're in an active chat, don't break up a topic into multiple messages as each one will result in a notification which can be disruptive. Use [threads](https://get.slack.help/hc/en-us/articles/115000769927-Message-threads) if you want to provide extra info to the question/comment you posted.
 1. If you are having a hard time keeping up with messages, you can update your preferences to have Slack email you all notifications. To change the setting, go to `Preferences > Notifications > When I'm not active on desktop...` and "send me email notifications."
 1. If you agree in a message to start a video call (typically by asking "Call?") the person that didn't leave the last comment starts the call. So either respond to the "Call?" request with a video link or say "Yes" and let the other person start it. Do not say "Yes" and start a call 5 seconds later since it is likely you'll both be creating a video call link at the same time.
@@ -1270,11 +1270,11 @@ For additional questions, please address in the [issue](https://gitlab.com/gitla
 
 To use the "Slack Down!" group chat on Zoom:
 
-1. In the Zoom desktop app go to the *Contacts* tab
+1. In the Zoom desktop app go to the `Team Chat` tab
 1. Click `+`
-1. Click "Join a Channel"
-1. Search "Slack down!"
-1. Click "Join"
+1. Click `Join a Channel`
+1. Search `Slack down!`
+1. Click `Join``
 
 Once service is restored, go back to Slack.
 

content/handbook/communication/chat.md

@@ -23,7 +23,7 @@ The alphabetically sorted starter list below spotlights a few of GitLab's many S
 | `#company-fyi`                       | Official company announcements, restricted permission levels to ensure high-signal; all GitLab team members are automatically added to this channel.                                                      |
 | `#whats-happening-at-gitlab`         | Open to all team members for unofficial updates which are important and/or useful to **most or all** of GitLab, including reminders, events, project updates, etc.; all GitLab team members are automatically added to this channel. |
 | `#diversity_inclusion_and_belonging` | Stay up to date on GitLab’s latest [Diversity, Inclusion and Belonging](/handbook/company/culture/inclusion/) initiatives and share feedback and thoughts about how we can make our environment even more inclusive.                          |
-| `#expense-reporting-inquiries`       | For questions pertaining to [expenses](/handbook/spending-company-money/) (e.g. Expensify).                                                                                                                                          |
+| `#expense-reporting-inquiries`       | For questions pertaining to [expenses](/handbook/spending-company-money/) (e.g. Navan).                                                                                                                                          |
 | `#git-help`                          | Specific questions about using Git in the terminal.                                                                                                                                                                                  |
 | `#is-this-known`                     | Get help in finding existing issues for existing problems.                                                                                                                                                                           |
 | `#it_help`                           | Create a Help Request in this channel should you have any IT general questions or trouble with setup (e.g. 2FA, accounts, etc.).                                                                                                     |                                                                             |

content/handbook/communication/confidentiality-levels.md

@@ -45,6 +45,7 @@ The following items are internal:
 1. Changes to GitLab.com free tier limits such as storage, data transfer, user limits or compute minutes are not public as they are similar to Pricing and Packaging as discussed below in limited access.
 1. Specific details about our hiring processes such as our scoring rubrics & criteria are not public as we want to ensure candidates provide an accurate overview of their experience and do not falsify their responses to meet our criteria. [High-level interview plans are public and documented in each job family](/handbook/hiring/job-families/#job-family-template-1).
 1. GitLab's [strategy](/handbook/company/strategy), [Yearlies](/handbook/company/yearlies/), and [OKRs](/handbook/company/okrs/) are internal-only. GitLab goal setting is intentional ambitious. External folks, without context, could make misinterpretations about the company’s financial health and strategic plans, so sharing this information may have [an unintended and undesirable effects](/handbook/legal/safe-framework/#effect).
+1. Discussion, designs, and code that are subject to the [Discovery phase](https://handbook.gitlab.com/handbook/legal/patent-program/#discussion-of-inventions-and-improvements-to-inventions) of a patent application. Prior to filing the application all product and protype development should take place outside of public repositories.
 
 ### Limited access
 

content/handbook/company/working-groups/product-accessibility.md

@@ -38,7 +38,7 @@ This Working Group has the following goals:
 | Criteria                                                                                      | Start Date | Completed Date | Progress | DRI             |
 | --------------------------------------------------------------------------------------------- | ---------- | -------------- | -------- | --------------- |
 | [Add axe-core checks to feature specs](https://gitlab.com/groups/gitlab-org/-/epics/11126)    | 15-08-2023 |                | 20%      | `@psjakubowska` |
-| [Add axe-core checks to components specs](https://gitlab.com/groups/gitlab-org/-/epics/11127) |            |                | 33%      | `@rchanila`     |
+| [Add axe-core checks to components specs](https://gitlab.com/groups/gitlab-org/-/epics/11127) | 16-04-2024 |                | 45%      | `@rchanila`     |
 | Address accessibility violations                                                              |            |                | 0%       | `@you?`         |
 | Validate existing accessibility issues                                                        |            |                | 0%       | `@you?`         |
 

content/handbook/customer-success/csm/segment/cse/webinar-calendar.md

@@ -24,14 +24,6 @@ If you know someone who might be interested in attending, feel free to share the
 
 ### AMER Time Zone Webinars & Labs
 
-
-### Jira to GitLab: Helping you transition to planning with GitLab
-##### April 16th, 2024 at 9:00-10:00AM PT / 12:00-1:00PM ET
-
-GitLab offers robust team planning capabilities that work directly with the DevOps lifecycle. Keeping teams in a single application offers operational and financial advantages. Many customers inquire about what a transition would look like from Jira Software to GitLab to team planning. This webinar will start to outline the differences in functionality and advantages gained by using GitLab. 
-
-[<button class="btn btn-primary" type="button">Register</button>](https://gitlab.zoom.us/webinar/register/WN_Y7sn8gWvQeixZ2hI3ZYVbg#/registration)
-
 #### Hands-on Lab: Security and Compliance in GitLab
 ##### April 17th, 2024 at 9:00-11:00AM PT / 12:00-2:00PM ET
 
@@ -65,13 +57,6 @@ Join us for the AI in DevSecOps webinar where we will explore Artificial Intelli
 
 ### EMEA Time Zone Webinars & Labs
 
-### Jira to GitLab: Helping you transition to planning with GitLab
-##### April 16th, 2024 at 9:00-10:00AM UTC / 11:00AM-12:00PM CET
-
-GitLab offers robust team planning capabilities that work directly with the DevOps lifecycle. Keeping teams in a single application offers operational and financial advantages. Many customers inquire about what a transition would look like from Jira Software to GitLab to team planning. This webinar will start to outline the differences in functionality and advantages gained by using GitLab. 
-
-[<button class="btn btn-primary" type="button">Register</button>](https://gitlab.zoom.us/webinar/register/WN_FtT-Df2ERHG6mQKs16EzeQ#/registration)
-
 #### Hands-on Lab: Security and Compliance in GitLab
 ##### April 17th, 2024 at 9:00-11:00AM UTC / 11:00AM-1:00PM CET