Fix broken internal anchors

.gitlab/CODEOWNERS

@@ -135,7 +135,7 @@
 /doc/api/invitations.md @aqualls
 /doc/api/experiments.md @aqualls 
 /doc/development/experiment_guide/ @aqualls
-/doc/development/snowplow.md @aqualls
+/doc/development/snowplow/ @aqualls
 /doc/development/usage_ping/ @aqualls
 /doc/user/admin_area/license.md @aqualls
 

.gitlab/issue_templates/Experimentation.md

@@ -18,7 +18,7 @@
 # Tracking Details
 
 - [json schema](https://gitlab.com/gitlab-org/iglu/-/blob/master/public/schemas/com.gitlab/gitlab_experiment/jsonschema/0-3-0) used in `gitlab-experiment` tracking.
-- see [taxonomy](https://docs.gitlab.com/ee/development/snowplow.html#structured-event-taxonomy) for a guide.
+- see [taxonomy](https://docs.gitlab.com/ee/development/snowplow/index.html#structured-event-taxonomy) for a guide.
 
 | activity | category | action | label | context | property | value |
 | -------- | -------- | ------ | ----- | ------- | -------- | ----- |

doc/development/README.md

@@ -263,7 +263,7 @@ See [database guidelines](database/index.md).
 
 - [Product Intelligence guide](https://about.gitlab.com/handbook/product/product-intelligence-guide/)
 - [Usage Ping guide](usage_ping/index.md)
-- [Snowplow guide](snowplow.md)
+- [Snowplow guide](snowplow/index.md)
 
 ## Experiment guide
 

doc/development/experiment_guide/gitlab_experiment.md

@@ -367,7 +367,7 @@ about contexts now.
 We can assume we run the experiment in one or a few places, but
 track events potentially in many places. The tracking call remains the same, with
 the arguments you would normally use when
-[tracking events using snowplow](../snowplow.md). The easiest example
+[tracking events using snowplow](../snowplow/index.md). The easiest example
 of tracking an event in Ruby would be:
 
 ```ruby

doc/development/product_analytics/snowplow.md

@@ -2,7 +2,7 @@
 redirect_to: '../snowplow.md'
 ---
 
-This document was moved to [another location](../snowplow.md).
+This document was moved to [another location](../snowplow/index.md).
 
 <!-- This redirect file can be deleted after April 1, 2021. -->
 <!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page -->

doc/development/usage_ping/index.md

@@ -13,7 +13,7 @@ This guide describes Usage Ping's purpose and how it's implemented.
 For more information about Product Intelligence, see:
 
 - [Product Intelligence Guide](https://about.gitlab.com/handbook/product/product-intelligence-guide/)
-- [Snowplow Guide](../snowplow.md)
+- [Snowplow Guide](../snowplow/index.md)
 
 More links:
 

doc/development/usage_ping/product_intelligence_review.md

@@ -14,7 +14,7 @@ general best practices for code reviews, refer to our [code review guide](../cod
 ## Resources for Product Intelligence reviewers
 
 - [Usage Ping Guide](index.md)
-- [Snowplow Guide](../snowplow.md)
+- [Snowplow Guide](../snowplow/index.md)
 - [Metrics Dictionary](metrics_dictionary.md)
 
 ## Review process
@@ -51,7 +51,7 @@ Product Intelligence files.
 ##### When adding or modifiying Snowplow events
 
 - For frontend events, when relevant, add a screenshot of the event in
-  the [testing tool](../snowplow.md#developing-and-testing-snowplow) used.
+  the [testing tool](../snowplow/index.md#developing-and-testing-snowplow) used.
 - For backend events, when relevant, add the output of the Snowplow Micro
   good events `GET http://localhost:9090/micro/good` (it might be a good idea
   to reset with `GET http://localhost:9090/micro/reset` first).
@@ -80,8 +80,8 @@ Any of the Product Intelligence engineers can be assigned for the Product Intell
   - Check the Redis slot.
   - Check if a [feature flag is needed](index.md#recommendations).
 - For tracking with Snowplow:
-  - Check that the [event taxonomy](../snowplow.md#structured-event-taxonomy) is correct.
-  - Check the [usage recomendations](../snowplow.md#usage-recommendations).
+  - Check that the [event taxonomy](../snowplow/index.md#structured-event-taxonomy) is correct.
+  - Check the [usage recomendations](../snowplow/index.md#usage-recommendations).
 - Metrics YAML definitions:
   - Check the metric `description`.
   - Check the metrics `key_path`.

doc/user/admin_area/settings/index.md

@@ -38,7 +38,7 @@ Access the default page for admin area settings by navigating to **Admin Area >
 | [PlantUML](../../../administration/integration/plantuml.md) | Allow rendering of PlantUML diagrams in documents. |
 | [Slack application](../../../user/project/integrations/gitlab_slack_application.md#configuration) **(FREE SAAS)** | Slack integration allows you to interact with GitLab via slash commands in a chat window. This option is only available on GitLab.com, though it may be [available for self-managed instances in the future](https://gitlab.com/gitlab-org/gitlab/-/issues/28164). |
 | [Third party offers](third_party_offers.md) | Control the display of third party offers. |
-| [Snowplow](../../../development/snowplow.md) | Configure the Snowplow integration. |
+| [Snowplow](../../../development/snowplow/index.md) | Configure the Snowplow integration. |
 | [Google GKE](../../project/clusters/add_gke_clusters.md) | Google GKE integration allows you to provision GKE clusters from GitLab. |
 | [Amazon EKS](../../project/clusters/add_eks_clusters.md) | Amazon EKS integration allows you to provision EKS clusters from GitLab. |