Convert all links to standard markdown

Author: dcramer

src/404.html

@@ -22,6 +22,6 @@ <h1>404</h1>
   <p><strong>Page not found :(</strong></p>
   <p>The requested page could not be found.</p>
   <p class="text-center">
-    <a href="{% link _documentation/home/index.md %}" class="btn btn-primary">Go back to the docs</a>
+    <a href="/" class="btn btn-primary">Go back to the docs</a>
   </p>
 </div>

src/_includes/components/platform_content.html

@@ -76,7 +76,7 @@
           -%}
           <a class="dropdown-item{% if __is_default %} active{% endif %}" id="{{ __uniq }}-{{ __slug }}-tab" data-platform="{{ __slug }}" data-toggle="platform" href="#{{ __uniq }}-{{ __slug }}" role="tab" aria-controls="{{ __uniq }}-{{ __slug }}" aria-selected="{% if __is_default %}true{% else %}false{% endif %}" data-not-dynamic>{{ __platform.name }}</a>
         {%- endfor -%}
-        <a class="dropdown-item" href="{% link _documentation/platforms/index.md %}" data-toggle="tooltip" data-placement="right" title="Click to see other platforms we support but that don't follow the unified&nbsp;API"><em>Platform not listed?</em></a>
+        <a class="dropdown-item" href="/platforms/" data-toggle="tooltip" data-placement="right" title="Click to see other platforms we support but that don't follow the unified&nbsp;API"><em>Platform not listed?</em></a>
       </div>
     </div>
   </div>

src/collections/_documentation/clients/go/config.md

@@ -52,7 +52,7 @@ raven.SetEnvironment("staging")
 
 Sets the release. Release names are just strings, but the Sentry SDK may detect some formats,
 and the format might render differently.
-For more information have a look at [the releases documentation]({% link _documentation/workflow/releases/index.md %}).
+For more information have a look at [the releases documentation](/workflow/releases/).
 
 ```go
 raven.SetRelease("h3ll0w0rld")

src/collections/_documentation/data-management/advanced-datascrubbing.md

@@ -4,7 +4,7 @@ sidebar_order: 4
 keywords: ["pii", "gdpr", "personally identifiable data", "compliance"]
 ---
 
-In addition to using [`beforeSend`]({% link _documentation/data-management/sensitive-data.md %}#custom-event-processing-in-the-sdk) in your SDK or our [server-side data scrubbing features]({% link _documentation/data-management/sensitive-data.md %}#server-side-scrubbing) to redact sensitive data, we are currently beta-testing ways to give you more granular control over server-side data scrubbing of your events. Additional functionality includes:
+In addition to using [`beforeSend`](/data-management/sensitive-data/#custom-event-processing-in-the-sdk) in your SDK or our [server-side data scrubbing features](/data-management/sensitive-data/#server-side-scrubbing) to redact sensitive data, we are currently beta-testing ways to give you more granular control over server-side data scrubbing of your events. Additional functionality includes:
 
 * Define custom regular expressions to match on sensitive data
 * Detailed tuning on which parts of an event to scrub
@@ -164,7 +164,7 @@ Select known parts of the schema using the following:
 * `$logentry` matches the `logentry` attribute of an event.
 * `$thread` matches a single thread instance in `{"threads": {"values": [...]}}`
 * `$breadcrumb` matches a single breadcrumb in `{"breadcrumbs": {"values": [...]}}`
-* `$span` matches a [trace span]({% link _documentation/performance/distributed-tracing.md %}#traces-transactions-and-spans)
+* `$span` matches a [trace span](/performance/distributed-tracing/#traces-transactions-and-spans)
 * `$sdk` matches the SDK context in `{"sdk": ...}`
 
 ### Escaping Special Characters

src/collections/_documentation/data-management/event-grouping/server-side-fingerprinting.md

@@ -4,7 +4,7 @@ sidebar_order: 1
 ---
 
 Server-side fingerprinting is also configured with a config similar to
-[grouping enhancements]({% link _documentation/data-management/event-grouping/grouping-enhancements.md %}),
+[grouping enhancements](/data-management/event-grouping/grouping-enhancements/),
 but the syntax is slightly different. The matchers are the same
 but instead of flipping flags, a fingerprint is assigned that overrides the
 default grouping entirely.
@@ -24,7 +24,7 @@ The matchers are:
 - `value`: matches on an exception value
 - `message`: matches on a log message
 
-The matchers also include the following from Custom Grouping Enhancements. See [grouping enhancements]({% link _documentation/data-management/event-grouping/grouping-enhancements.md %}#rules) for more info on how they work:
+The matchers also include the following from Custom Grouping Enhancements. See [grouping enhancements](/data-management/event-grouping/grouping-enhancements/#rules) for more info on how they work:
 
 - `family`
 - `path`
@@ -59,4 +59,4 @@ family:native function:malloc -> memory-allocation-error
 
 # group all allocation errors by the package (dylib, executable) that caused them
 function:*alloc* -> {{ package }}
-{% endraw %}```
+{% endraw %}```

src/collections/_documentation/data-management/sensitive-data.md

@@ -132,7 +132,7 @@ As mentioned earlier, configure scrubbing within SDK if possible so that sensiti
 
 ### Advanced server-side data scrubbing
 
-We are currently betatesting additional features around server-side data scrubbing. For more information see [_Advanced Data Scrubbing_]({% link _documentation/data-management/advanced-datascrubbing.md %}).
+We are currently betatesting additional features around server-side data scrubbing. For more information see [_Advanced Data Scrubbing_](/data-management/advanced-datascrubbing/).
 
 ## Restricting Emails
 

src/collections/_documentation/enriching-error-data/breadcrumbs.md

@@ -67,4 +67,4 @@ hint.  The function can modify the breadcrumb or decide to discard it entirely:
 
 {% include components/platform_content.html content_dir='before-breadcrumb' %}
 
-For information about what can be done with the hint see [_Filtering Events_]({% link _documentation/error-reporting/configuration/filtering.md %}#before-breadcrumb).
+For information about what can be done with the hint see [_Filtering Events_](/error-reporting/configuration/filtering/#before-breadcrumb).

src/collections/_documentation/enriching-error-data/error-tracing.md

@@ -6,7 +6,7 @@ sidebar_order: 5
 With error tracing, you can correlate errors from multiple services and uncover a significant story surrounding a break. Using a unique identifier allows you to trace an error and pinpoint the service and code behaving unexpectedly. 
 
 ## Error Tracing and Sentry Configuration
-The following steps demonstrate a potential use-case that involves an example web application with a JavaScript front-end and a Node.js server. The examples assume that both services are already configured with Sentry's [JavaScript SDK]({% link _documentation/platforms/javascript/index.md %}).
+The following steps demonstrate a potential use-case that involves an example web application with a JavaScript front-end and a Node.js server. The examples assume that both services are already configured with Sentry's [JavaScript SDK](/platforms/javascript/).
 
 #### Step 1: Generate a unique transaction ID
 Generate a unique transaction identifier and set as a Sentry tag in the service issuing the request. This unique identifier could be a transaction ID or a session ID created when the web application first loads. Set this value as a Sentry tag using the Sentry SDK. Below, the example uses a `transactionId` as a unique identifier:

src/collections/_documentation/enriching-error-data/scopes.md

@@ -16,8 +16,8 @@ blank scope are created on it.  That hub is then associated with the current
 thread and will internally hold a stack of scopes.
 
 The scope will hold useful information that should be sent along with the
-event.  For instance [contexts]({% link _documentation/enriching-error-data/additional-data.md %}) or
-[breadcrumbs]({% link _documentation/enriching-error-data/breadcrumbs.md %}) are stored on
+event.  For instance [contexts](/enriching-error-data/additional-data/) or
+[breadcrumbs](/enriching-error-data/breadcrumbs/) are stored on
 the scope.  When a scope is pushed, it inherits all data from the parent scope
 and when it pops all modifications are reverted.
 
@@ -32,7 +32,7 @@ of the box.  The hub you are unlikely to be interacting with directly unless you
 are writing an integration or you want to create or destroy scopes.  Scopes on the
 other hand are more user facing.  You can at any point in time call
 `configure-scope` to modify data stored on the scope.  This is for instance
-used to [modify the context]({% link _documentation/enriching-error-data/additional-data.md %}).
+used to [modify the context](/enriching-error-data/additional-data/).
 
 {% capture __alert_content -%}
 If you are very curious about how this thread locality thing works here are the
@@ -65,7 +65,7 @@ This can also be applied when unsetting a user at logout:
 {% include components/platform_content.html content_dir='unset-user' %}
 
 To learn what useful information can be associated with scopes see
-[the context documentation]({% link _documentation/enriching-error-data/additional-data.md %}).
+[the context documentation](/enriching-error-data/additional-data/).
 
 ## Local Scopes
 

src/collections/_documentation/error-reporting/capturing.md

@@ -11,7 +11,7 @@ issue group or be added to an already existing one based on Sentry's grouping
 algorithm.  Separately to capturing you can also record "breadcrumbs" that lead
 up to an event.  Breadcrumbs are different in that they will not create an event
 in Sentry but will be buffered until the next event is sent.  For more information
-have a look at [the breadcrumbs documentation]({% link _documentation/enriching-error-data/breadcrumbs.md %}).
+have a look at [the breadcrumbs documentation](/enriching-error-data/breadcrumbs/).
 
 ## Capturing Errors / Exceptions
 
@@ -38,9 +38,6 @@ into.  For more information about that consult the API documentation of the SDK.
 
 ## Next Steps
 
-* Need to add extra data to your events? Have a look at [our context
-  documentation]({% link _documentation/enriching-error-data/additional-data.md %}).
+* Need to add extra data to your events? Have a look at [our context documentation](/enriching-error-data/additional-data/).
 
-* Captured too much data? Have a look at [filtering]({% link
-  _documentation/error-reporting/configuration/filtering.md %}) to remove spam
-  or sensitive information from your events.
+* Captured too much data? Have a look at [filtering](/error-reporting/configuration/filtering/) to remove spam or sensitive information from your events.

src/collections/_documentation/error-reporting/configuration/before-breadcrumb-hint/javascript.md

@@ -15,4 +15,4 @@ Sentry.init({
 });
 ```
 
-For information about which hints are available see [hints in JavaScript]({% link _documentation/platforms/javascript/index.md %}#hints).
+For information about which hints are available see [hints in JavaScript](/platforms/javascript/#hints).

src/collections/_documentation/error-reporting/configuration/before-breadcrumb-hint/python.md

@@ -9,4 +9,4 @@ def before_breadcrumb(crumb, hint):
 sentry_sdk.init(before_breadcrumb=before_breadcrumb)
 ```
 
-For information about which hints are available see [hints in Python]({% link _documentation/platforms/python/index.md %}#hints).
+For information about which hints are available see [hints in Python](/platforms/python/#hints).

src/collections/_documentation/error-reporting/configuration/before-send-hint/javascript.md

@@ -12,4 +12,4 @@ init({
 });
 ```
 
-For information about which hints are available see [hints in JavaScript]({% link _documentation/platforms/javascript/index.md %}#hints).
+For information about which hints are available see [hints in JavaScript](/platforms/javascript/#hints).

src/collections/_documentation/error-reporting/configuration/before-send-hint/python.md

@@ -11,4 +11,4 @@ def before_send(event, hint):
 sentry_sdk.init(before_send=before_send)
 ```
 
-For information about which hints are available see [hints in Python]({% link _documentation/platforms/python/index.md %}#hints).
+For information about which hints are available see [hints in Python](/platforms/python/#hints).

src/collections/_documentation/error-reporting/configuration/config-intro/php.md

@@ -8,7 +8,7 @@ Sentry\init([
 ```
 
 {% capture __alert %}
-Some of the options listed below that are marked as _not available_ may be available in another form; see [PHP specific documentation]({% link _documentation/workflow/releases/index.md %}).
+Some of the options listed below that are marked as _not available_ may be available in another form; see [PHP specific documentation](/workflow/releases/).
 {% endcapture %}
 
 {% include components/alert.html

src/collections/_documentation/error-reporting/configuration/index.md

@@ -42,7 +42,7 @@ if you have the chance it's a better idea to manually set it.  That way it's gua
 in sync with your deploy integrations or source map uploads.
 
 Release names are just strings but some formats are detected by Sentry and might be rendered
-differently.  For more information have a look at [the releases documentation]({% link _documentation/workflow/releases/index.md %}).
+differently.  For more information have a look at [the releases documentation](/workflow/releases/).
 
 By default the SDK will try to read this value from the `SENTRY_RELEASE` environment
 variable (in the browser SDK, this will be read off of the `window.SENTRY_RELEASE` if

src/collections/_documentation/error-reporting/getting-started-next-steps/csharp.md

@@ -1 +1 @@
--  [_integrating with the .NET ecosystem_]({% link _documentation/platforms/dotnet/index.md %})
+-  [_integrating with the .NET ecosystem_](/platforms/dotnet/)

src/collections/_documentation/error-reporting/getting-started-next-steps/go.md

@@ -1 +1 @@
--  [_integrating with the Go ecosystem_]({% link _documentation/platforms/go/index.md %})
+-  [_integrating with the Go ecosystem_](/platforms/go/)

src/collections/_documentation/error-reporting/getting-started-next-steps/javascript.md

@@ -1 +1 @@
--  [_integrating with the JavaScript ecosystem_]({% link _documentation/platforms/javascript/index.md %})
+-  [_integrating with the JavaScript ecosystem_](/platforms/javascript/)

src/collections/_documentation/error-reporting/getting-started-next-steps/native.md

@@ -1,3 +1,3 @@
--  [_adding Google Breakpad_]({% link _documentation/platforms/native/index.md %}#google-breakpad)
--  [_adding Google Crashpad_]({% link _documentation/platforms/native/index.md %}#google-crashpad)
--  [_integrating with Unreal Engine 4_]({%- link _documentation/platforms/native/ue4.md -%})
+-  [_adding Google Breakpad_](/platforms/native/#google-breakpad)
+-  [_adding Google Crashpad_](/platforms/native/#google-crashpad)
+-  [_integrating with Unreal Engine 4_](/platforms/native/ue4/)

src/collections/_documentation/error-reporting/getting-started-next-steps/php.md

@@ -1 +1 @@
--  [_integrating with the PHP ecosystem_]({% link _documentation/platforms/php/index.md %})
+-  [_integrating with the PHP ecosystem_](/platforms/php/)

src/collections/_documentation/error-reporting/getting-started-next-steps/python.md

@@ -1 +1 @@
--  [_integrating with the Python ecosystem_]({% link _documentation/platforms/python/index.md %})
+-  [_integrating with the Python ecosystem_](/platforms/python/)

src/collections/_documentation/error-reporting/getting-started-next-steps/rust.md

@@ -1 +1 @@
--  [_integrating with the Rust ecosystem_]({% link _documentation/platforms/rust/index.md %})
+-  [_integrating with the Rust ecosystem_](/platforms/rust/)

src/collections/_documentation/performance/getting-started.md

@@ -7,10 +7,10 @@ Performance monitoring helps developers measure Apdex, Throughput, and trace slo
 
 Learn more about performance monitoring in:
 
-- [Homepage]({% link _documentation/performance/performance-homepage.md %}): displays a high-level report of application health, including problematic transactions and both Apdex and Throughput graphs
-- [Distributed Tracing]({% link _documentation/performance/distributed-tracing.md %}): diagnose problems and view interactions across your software systems
-- [Metrics]({% link _documentation/performance/performance-metrics.md %}): provides insight into user experience of your application based on custom thresholds
-- [Discover]({% link _documentation/performance/discover/index.md %}): view data across environments with pre-built queries. Customers subscribed to the Team or Business plan can use Discover to view comprehensive information sent to Sentry.
+- [Homepage](/performance/performance-homepage/): displays a high-level report of application health, including problematic transactions and both Apdex and Throughput graphs
+- [Distributed Tracing](/performance/distributed-tracing/): diagnose problems and view interactions across your software systems
+- [Metrics](/performance/performance-metrics/): provides insight into user experience of your application based on custom thresholds
+- [Discover](/performance/discover/): view data across environments with pre-built queries. Customers subscribed to the Team or Business plan can use Discover to view comprehensive information sent to Sentry.
 
 ## Install
 
@@ -20,15 +20,15 @@ Learn more about performance monitoring in:
 
 Sentry provides several tools to explore your application's performance data and uncover problems.
 
-The **Performance homepage** is our center for monitoring how your application is doing. Here, you can view a list of all your endpoints and transactions and view a summary of any transaction in your application. Learn more about the [Homepage]({% link _documentation/performance/performance-homepage.md %}).
+The **Performance homepage** is our center for monitoring how your application is doing. Here, you can view a list of all your endpoints and transactions and view a summary of any transaction in your application. Learn more about the [Homepage](/performance/performance-homepage/).
 
 [{% asset performance/performance-homepage-main-example.png alt="Example of Performance in Product UI" %}]({% asset performance/performance-homepage-main-example.png @path %})
 
-**Discover** is our custom business intelligence query builder that can help you answer questions about your data and analyze metrics. Learn more about [Discover]({% link _documentation/performance/discover/index.md %}).
+**Discover** is our custom business intelligence query builder that can help you answer questions about your data and analyze metrics. Learn more about [Discover](/performance/discover/).
 
 [{% asset performance/discover-main-page-example.png alt="Discover page" %}]({% asset performance/discover-main-page-example.png @path %})
 
 
-**Transaction Details** lets you examine an individual transaction event in detail. Here spans are visualized to help you identify slow HTTP requests, slow database queries, and other bottlenecks. You can also jump to other transactions within the trace, and identify associated errors. Learn more about [Distributed Tracing]({% link _documentation/performance/distributed-tracing.md %}) and the [Transaction Details page]({% link _documentation/performance/distributed-tracing.md %}#transaction-detail-viewpage).
+**Transaction Details** lets you examine an individual transaction event in detail. Here spans are visualized to help you identify slow HTTP requests, slow database queries, and other bottlenecks. You can also jump to other transactions within the trace, and identify associated errors. Learn more about [Distributed Tracing](/performance/distributed-tracing/) and the [Transaction Details page](/performance/distributed-tracing/#transaction-detail-viewpage).
 
-[{% asset performance/transaction-detail-main-example.png alt="Discover page" %}]({% asset performance/transaction-detail-main-example.png @path %})
+[{% asset performance/transaction-detail-main-example.png alt="Discover page" %}]({% asset performance/transaction-detail-main-example.png @path %})

src/collections/_documentation/platforms/dotnet/entityframework.md

@@ -29,7 +29,7 @@ This package extends `Sentry` main SDK. That means that besides the EF features,
 * Queries as breadcrumbs
 * Validation errors
 
-All queries executed are added as breadcrumbs and are sent with any event which happens on the same [scope]({% link _documentation/enriching-error-data/scopes.md %}). Besides that, validation errors are also included as `Extra`.
+All queries executed are added as breadcrumbs and are sent with any event which happens on the same [scope](/enriching-error-data/scopes/). Besides that, validation errors are also included as `Extra`.
 
 
 ## Configuration