SHOWCASE: add versioned index file

Author: chargome

docs/platforms/javascript/common/usage/index__v7.119.0.mdx

@@ -0,0 +1,34 @@
+---
+title: Capturing Errors and Events
+description: "Learn how to use the SDK to manually capture errors and other events."
+sidebar_order: 4
+---
+!!Versioned index file!!
+
+
+Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
+
+<Note>
+
+Key terms:
+
+- An _event_ is one instance of sending data to Sentry. Generally, this data is an error or exception.
+- An _issue_ is a grouping of similar events.
+- The reporting of an event is called _capturing_.
+  When an event is captured, it’s sent to Sentry.
+
+</Note>
+
+The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
+
+While capturing an event, you can also record the breadcrumbs that lead up to that event. Breadcrumbs are different from events: they will not create an event in Sentry, but will be buffered until the next event is sent. Learn more about breadcrumbs in our <PlatformLink to="/enriching-events/breadcrumbs/">Breadcrumbs documentation</PlatformLink>.
+
+## Capturing Errors
+
+<PlatformContent includePath="capture-error" />
+
+## Capturing Messages
+
+Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.
+
+<PlatformContent includePath="capture-message" />