Change image imports to use @site for portability

Author: crandmck

docs/getting-started/index.mdx

@@ -2,11 +2,9 @@
 title: Getting started with Content Credentials
 ---
 
-import c2pa_terms from '../../static/img/c2pa-terms.png';
-import cai_open_source from '../../static/img/cai-open-source.jpg';
-import cai_os_tools_table from '../../static/img/cai-os-tools-table.png';
-import cai_levels from '../../static/img/cai-levels.png';
-import cr_pin from '../../static/img/cr-pin.png';
+import c2pa_terms from '@site/static/img/c2pa-terms.png';
+import cai_levels from '@site/static/img/cai-levels.png';
+import cr_pin from '@site/static/img/cr-pin.png';
 
 This is a technical introduction to the Content Authenticity Initiative (CAI) open-source SDK that provides initial context and an overview of the technical aspects of implementing CAI solutions.
 
@@ -89,9 +87,9 @@ In practice, to use a certificate with the CAI SDK, follow this process:
 For more information on getting and using certificates, see [Signing and certificates](signing/index.md).
 :::
 
-### Verify trust list
+### Interim trust list
 
-import verify_unknown_source from '../../static/img/verify-cc-unknown-source.png';
+import verify_unknown_source from '@site/static/img/verify-cc-unknown-source.png';
 
 The C2PA [Verify tool](https://verify.contentauthenticity.org) uses a list of _known certificates_ (sometimes referred to as a "trust list") to determine whether a Content Credential was issued by a known source. Currently, it uses the [interim trust list](verify-known-cert-list) but it will be updated soon to use the official [C2PA trust list](conformance.mdx#c2pa-trust-lists).
 

docs/getting-started/trust-list.mdx

@@ -3,7 +3,7 @@ id: verify-known-cert-list
 title: The interim trust list
 ---
 
-import verify_unknown_source from '../../static/img/verify-cc-unknown-source.png';
+import verify_unknown_source from '@site/static/img/verify-cc-unknown-source.png';
 
 :::warning Warning
 The process described on this page is deprecated. The C2PA has released its official trust lists, and Verify will be updated to use them soon. See [Deprecation timeline](#deprecation-timeline) for more information.

docs/getting-started/verify.mdx

@@ -3,7 +3,7 @@ id: verify
 title: Using the Verify tool
 ---
 
-import verify_site from '../../static/img/verify.png';
+import verify_site from '@site/static/img/verify.png';
 
 The C2PA **[Verify tool](https://verify.contentauthenticity.org)** (often referred to as simply "Verify") is useful both for consumers and for CAI application developers.
 
@@ -71,7 +71,7 @@ Once you've uploaded an asset or entered an asset URL, if the asset:
 - Does not have an associated manifest store, Verify displays the message **No Content Credential**.
 - Does have an associated manifest store, Verify displays information from it in the three vertical panels, for example as shown below.
 
-import verify_sections from '../../static/img/verify-sections.png';
+import verify_sections from '@site/static/img/verify-sections.png';
 
 <img src={verify_sections} style={{ width: '800px', marginBottom: '20px' }} />
 
@@ -149,7 +149,7 @@ import verify_sections from '../../static/img/verify-sections.png';
 
 ### Title and signing information
 
-import verify_title_date from '../../static/img/verify-title-date.png';
+import verify_title_date from '@site/static/img/verify-title-date.png';
 
 <img
   src={verify_title_date}
@@ -176,7 +176,7 @@ For example, suppose you downloaded a file from Adobe Stock and renamed it `my_s
 
 If the Content Credential was signed by a certificate that is NOT on the [known certificate list](verify-known-cert-list), such as one of the SDK's [test certificates](signing/test-certs.md), then Verify displays "Unrecognized" at the top of this section with this notice:
 
-import verify_unknown_source from '../../static/img/verify-cc-unknown-source.png';
+import verify_unknown_source from '@site/static/img/verify-cc-unknown-source.png';
 
 <img
   src={verify_unknown_source}
@@ -205,7 +205,7 @@ If the issuer string is too long, then the date might be truncated or not shown
 
 If the manifest has [validation errors](manifest/reading/validation.md), then Verify displays this notice:
 
-import verify_validation_error from '../../static/img/verify-validation-error.png';
+import verify_validation_error from '@site/static/img/verify-validation-error.png';
 
 <img
   src={verify_validation_error}
@@ -263,7 +263,7 @@ The **Process** section displays information about the process used to create th
 
 For example:
 
-import verify_process from '../../static/img/verify-process.png';
+import verify_process from '@site/static/img/verify-process.png';
 
 <img src={verify_process} style={{ width: '600px' }} />
 
@@ -329,7 +329,7 @@ The **Actions** subsection lists [actions](https://opensource.contentauthenticit
 
 #### AI-generated content
 
-import verify_process_ai from '../../static/img/verify-process-ai.png';
+import verify_process_ai from '@site/static/img/verify-process-ai.png';
 
 <img src={verify_process_ai} style={{ width: '250px' }} />
 
@@ -343,7 +343,7 @@ This section displays the same information as described in [Title and singing in
 
 If the active manifest includes [Exif metadata assertions](../manifest/writing/assertions-actions.md#cawg-metadata-assertions), then an additional **Camera capture details** section shows information about the device used to create the asset, as illustrated below:
 
-import verify_exif from '../../static/img/verify-exif.png';
+import verify_exif from '@site/static/img/verify-exif.png';
 
 <img src={verify_exif} style={{ width: '500px' }} />
 

docs/introduction.mdx

@@ -3,8 +3,8 @@ id: introduction
 title: CAI open source SDK
 ---
 
-import cr_pin from '../static/img/cr-pin.png';
-import cai_open_source from '../static/img/cai-open-source.jpg';
+import cr_pin from '@site/static/img/cr-pin.png';
+import cai_open_source from '@site/static/img/cai-open-source.jpg';
 
 You're strongly encouraged to read this introduction and [Getting started](getting-started/index.mdx) for some basic background and context, before you dive right into development. [Working with manifests](manifest/understanding.md) also has some useful information, regardless of which language and library you use.
 
@@ -51,7 +51,7 @@ An embedded application can use the Rust FFI (foreign function interface) to cal
 
 ## Which tool is right for you?
 
-import green_check from '../static/img/green_check.png';
+import green_check from '@site/static/img/green_check.png';
 
 <table>
   <thead>