Merge pull request #2029 from elementary-data/update-snippet-syntax

Update snippet syntax

Author: NoyaOffer

docs/_snippets/cloud/integrations/cards-groups/cloud-integrations-cards.mdx

@@ -3,4 +3,8 @@ title: "Platform features"
 icon: "browsers"
 ---
 
-<Snippet file="cloud/features.mdx" />
+import Features from '/snippets/cloud/features.mdx';
+
+
+
+<Features />

docs/_snippets/dwh/bigquery/cli_service_account.mdx

@@ -2,7 +2,11 @@
 title: "Alert rules"
 ---
 
-<Snippet file="/_snippets/cloud/cloud-feature-tag.mdx" />
+import CloudFeatureTag from '/snippets/cloud/cloud-feature-tag.mdx';
+
+
+
+<CloudFeatureTag />
 
 **Alert Rules** help you control where alerts are sent and when they are triggered, so you can stay focused on the incidents that matter most. In Elementary Cloud, each rule combines **filters** (what to alert on) and **destinations** (where to send the alert).
 

docs/_snippets/dwh/bigquery/cloud_service_account.mdx

@@ -3,6 +3,11 @@ title: Alerts and Incidents Overview
 sidebarTitle: Alerts & incidents overview
 ---
 
+import AlertTypes from '/snippets/cloud/features/alerts-and-incidents/alert-types.mdx';
+import AlertsDestinationCards from '/snippets/cloud/integrations/cards-groups/alerts-destination-cards.mdx';
+
+
+
 Alerts and incidents in Elementary are designed to shorten your time to response and time to resolution when data issues occur.
 
 - **Alert -** Notification about an event that indicates a data issue.
@@ -51,8 +56,8 @@ you will be able to track all open and historical incidents, and get metrics on
 
 ## Alert types
 
-<Snippet file="cloud/features/alerts-and-incidents/alert-types.mdx" />
+<AlertTypes />
 
 ## Supported alert integrations
 
-<Snippet file="cloud/integrations/cards-groups/alerts-destination-cards.mdx" />
+<AlertsDestinationCards />

docs/_snippets/faq/question-schema.mdx

@@ -3,7 +3,11 @@ title: Incident Management
 sidebarTitle: Incident management
 ---
 
-<Snippet file="cloud/cloud-feature-tag.mdx" />
+import CloudFeatureTag from '/snippets/cloud/cloud-feature-tag.mdx';
+
+
+
+<CloudFeatureTag />
 
 The `Incidents` page is designed to enable your team to stay on top of open incidents and collaborate on resolving them.
 The page gives a comprehensive overview of all current and previous incidents, where users can view the status, prioritize, assign and resolve incidents.

docs/cloud/features.mdx

@@ -3,7 +3,11 @@ title: Incidents in Elementary
 sidebarTitle: Incidents
 ---
 
-<Snippet file="cloud/cloud-feature-tag.mdx" />
+import CloudFeatureTag from '/snippets/cloud/cloud-feature-tag.mdx';
+
+
+
+<CloudFeatureTag />
 
 One of the challenges data teams face is tracking and understand and collaborate on the status of data issues.
 Tests fail daily, pipelines are executed frequently, alerts are sent to different channels.

docs/cloud/features/alerts-and-incidents/alert-rules.mdx

@@ -2,6 +2,11 @@
 title: "Owners and subscribers"
 ---
 
+import Owner from '/snippets/alerts/owner.mdx';
+import Subscribers from '/snippets/alerts/subscribers.mdx';
+
+
+
 We highly recommend configuring owners and subscribers for your models and/or tests.
 An owner is the person responsible for the model, and subscribers are the people who are interested in getting the alerts on the model or test.
 Owners and subscribers will be mentioned (tagged) in the Slack alerts. Also their name will appear in the alerts and the UI.
@@ -12,8 +17,8 @@ configuring owners and subscribers:
 Owners can be easily added or edited in the Catalog screen. [Learn more about managing your assets' metadata.](/cloud/features/data-governance/manage-metadata)
 
 #### Configuting owners in code:
-<Snippet file="alerts/owner.mdx" />
+<Owner />
 
 ### Subscribers
 
-<Snippet file="alerts/subscribers.mdx" />
+<Subscribers />