resolves merge conflicts

timbastin · timbastin · commit 947bd3d65cbf · 2026-08-05T12:57:58.000+02:00
diff --git a/next-env.d.ts b/next-env.d.ts
@@ -1,7 +1,7 @@
 /// <reference types="next" />
 /// <reference types="next/image-types/global" />
-import "./.next/dev/types/routes.d.ts";
-import "./.next/dev/types/root-params.d.ts";
+import "./.next/types/routes.d.ts";
+import "./.next/types/root-params.d.ts";
 
 // NOTE: This file should not be edited
 // see https://nextjs.org/docs/pages/api-reference/config/typescript for more information.
diff --git a/src/assets/advisory-affected-packages.png b/src/assets/advisory-affected-packages.png
diff --git a/src/assets/advisory-cvss-calculator.png b/src/assets/advisory-cvss-calculator.png
diff --git a/src/assets/advisory-detail-draft.png b/src/assets/advisory-detail-draft.png
diff --git a/src/assets/advisory-dialog-metadata.png b/src/assets/advisory-dialog-metadata.png
diff --git a/src/assets/advisory-list-page.png b/src/assets/advisory-list-page.png
diff --git a/src/pages/how-to-guides/compliance/attestation-policies.mdx b/src/pages/how-to-guides/compliance/attestation-policies.mdx
@@ -50,13 +50,13 @@ Attestation policies are:
 
 Navigate to **Organization** → **Compliance**
 
-![Organization Compliance Dashboard](../../../assets/org-compliance-dashboard.png)
+![Organization Compliance Dashboard](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/compliance-posture-organization.png)
 
 ### Project-Level Compliance View
 
 Navigate to **Organization** → **Project** → **Compliance**
 
-![Project Compliance Dashboard](../../../assets/project-compliance-dashboard.png)
+![Project Compliance Dashboard](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/compliance-posture-group.png)
 
 <Callout type="info">
     Enabling a policy at the project level tells DevGuard to evaluate that
@@ -70,7 +70,7 @@ Inspect detailed compliance control evaluations for a specific repository versio
 
 Navigate to **Organization** → **Project** → **Repository** → **Compliance**
 
-![Repository Compliance Dashboard](../../../assets/repo-compliance-dashboard.png)
+![Repository Compliance Dashboard](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/compliance-posture-repository.png)
 
 ## Navigate to Attestation Policies
 
diff --git a/src/pages/how-to-guides/compliance/audit-logs.mdx b/src/pages/how-to-guides/compliance/audit-logs.mdx
@@ -42,7 +42,7 @@ For organization-wide compliance tracking, see [Compliance Dashboards](/how-to-g
 1. Navigate to **Organization** → **Overview**
 2. Select Artifact on the left side.
 
-![Download PDF-Report](../../../assets/downloading-pdf-report.png)
+![Download PDF-Report](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/asset-overview.png)
 
 {/* [PDF Example](https://main.devguard.org/l3montree-cybersecurity/projects/devguard/assets/devguard/refs/main/vulnerability-report.pdf?artifact=pkg%3Aoci%2Fdevguard%3Frepository_url%3Dghcr.io%2Fl3montree-dev%2Fdevguard)
 */}
diff --git a/src/pages/how-to-guides/compliance/export-sbom.mdx b/src/pages/how-to-guides/compliance/export-sbom.mdx
@@ -36,19 +36,19 @@ Access SBOM download interface:
 
 1. Navigate to **Repository** → **Dependencies**
 2. Click **Download SBOM** button
-   ![SBOM Overview Download](../../../assets/sbom-overview-download.png)
+   ![SBOM Overview Download](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/download-sbom-document.png)
 
 **Method 2: From Dependency View**
 
 1. Navigate to **Repository** → **Dependencies**
 2. Click **Download SBOM** button
-   ![Download from Dependency View](../../../assets/dependencies-graph-sbom-download.png)
+   ![Download from Dependency View](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/dependency-insights-overview.png)
 
 ## Download SBOM Document
 
 Export your component inventory:
 
-![Select your SBOM format and options](../../../assets/sbom-download-menu.png)
+![Select your SBOM format and options](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/download-sbom-document.png)
 
 for more information on what an SBOM contains, see the [Supplementary SBOMs](/explanations/supplementary-sboms) section.
 
diff --git a/src/pages/how-to-guides/dependency-management/view-dependency-tree.mdx b/src/pages/how-to-guides/dependency-management/view-dependency-tree.mdx
@@ -58,7 +58,7 @@ By default, the graph shows only vulnerable dependencies:
 Click on Organization → Project → Repository → Dependencies → Graph
 
 
-![Dependency Tree](../../../assets/open-dependency-graph.png)
+![Dependency Tree](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/dependency-insights-overview.png)
 
 1. Toggle **Display all dependencies** switch in the top-right
 2. The graph expands to show every dependency, including safe ones
@@ -67,7 +67,7 @@ Click on Organization → Project → Repository → Dependencies → Graph
    - Identifying transitive dependency chains
    - Finding dependency conflicts or redundancies
 
-![Dependency Tree](../../../assets/dependency-tree-all-dep.png)
+![Dependency Tree](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/dependency-insights-graph.png)
 
 <Callout type="info">
   Displaying all dependencies can create large graphs. For projects with hundreds of dependencies, consider filtering by artifact first.
diff --git a/src/pages/how-to-guides/vex/export-vex.mdx b/src/pages/how-to-guides/vex/export-vex.mdx
@@ -25,6 +25,9 @@ that always reflects the current state.
 ## Download a VEX document
 
 1. Navigate to **Dependency Risks → VEX Rules**.
+
+![Download Vex Button](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/dependency-insights-overview.png)
+
 2. Click **Share your VEX**.
 3. Select the **Branch / Tag** and the **Artifact** — VEX is always published per reference and per artifact.
 4. Choose **Download in JSON-Format** or **Download in XML-Format**.
@@ -41,6 +44,9 @@ posture, publish the endpoints instead.
 
 1. Open **Repository Settings**.
 2. Enable **Enable public access to vulnerability data**.
+
+![Share VEX Endpoint](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/public-access.png)
+
 3. Select the **Branch / Tag** and **Artifact** to publish.
 4. Expand **Public SBOM / VEX / CSAF URLs** and copy the URL you need:
 
diff --git a/src/pages/how-to-guides/vulnerability-management/create-security-advisories.mdx b/src/pages/how-to-guides/vulnerability-management/create-security-advisories.mdx
@@ -76,40 +76,13 @@ Navigate to your repository and open the **Security Advisory** entry in the asse
 
 This opens the advisory list for the current repository and ref. The list is organized into **Draft**, **Public** and **Withdrawn** tabs, and — as an admin — you get a **Create Security Advisory** button in the top-right corner. Each row shows the advisory title and its CVSS severity.
 
-![Security advisory list page showing the Draft, Public and Withdrawn tabs and the Create button](../../../assets/advisory-list-page.png)
+![Security advisory list page showing the Draft, Public and Withdrawn tabs and the Create button](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/security-advisory-overview.png)
 
 ## Create a Security Advisory
 
 Click **Create Security Advisory** to open the creation dialog. The dialog guides you through three steps.
 
-### Step 1 — Describe the vulnerability
-
-On the first step you enter the core metadata of the advisory:
-
-- **Title** *(required)* — a concise summary of the issue.
-- **Description** *(required)* — the full write-up in Markdown. A `### Summary` / `### Details` structure works well.
-- **Vector string** — the CVSS vector (for example `CVSS:4.0/AV:N/AC:L/...`). If you don't know it by heart, use the built-in calculator in the next step.
-
-![Security advisory creation dialog with title, description, severity and vector fields](../../../assets/vex-rule-mark-false-positive-from-path.png)
-
-### Step 2 — Calculate the CVSS vector (optional)
-
-If you need help scoring the vulnerability, open the **Calculate vector string** helper. You can switch between **CVSS 3.1** and **CVSS 4.0**, pick a value for each metric, and DevGuard shows the resulting base score and severity live. Applying the calculation writes the vector back into the form and derives the severity automatically.
-
-![CVSS calculator inside the advisory dialog with a version toggle and live base score](../../../assets/advisory-cvss-calculator.png)
-
-### Step 3 — Add the affected packages
-
-Finally, list the packages affected by the advisory (up to ten). For each package you provide:
-
-- **Ecosystem** — for example `go`, `npm` or `pypi`.
-- **Package name** — the package identifier.
-- **Affected versions** — the version where the vulnerability was introduced.
-- **Patched version** — the version that fixes it.
-
-DevGuard turns these into standardized version ranges (`vers:` notation) in the published document and adds a *vendor fix* remediation pointing at the patched version.
-
-![Affected packages step of the advisory dialog with ecosystem, package name and version range fields](../../../assets/advisory-affected-packages.png)
+![Affected packages step of the advisory dialog with ecosystem, package name and version range fields](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/security-advisory-creation.png)
 
 Click **Create Draft Advisory** to save. The new advisory appears under the **Draft** tab.
 
@@ -127,7 +100,7 @@ A draft shows a **Draft** badge and three admin actions:
 - **Publish Draft** — makes the advisory public. After confirmation it is served through the CSAF feed and can no longer be edited.
 - **Delete Draft** — permanently removes the draft.
 
-![Security advisory detail page for a draft, showing the Change, Publish and Delete actions](../../../assets/advisory-detail-draft.png)
+![Security advisory detail page for a draft, showing the Change, Publish and Delete actions](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/security-advisory-detailed.png)
 
 <Callout type="warning">
   Publishing is irreversible in the sense that a public advisory can no longer be edited — you can only **withdraw** it. Double-check the title, description, severity and affected packages before you confirm.
diff --git a/src/pages/how-to-guides/vulnerability-management/csaf-common-security-advisory-framework.mdx b/src/pages/how-to-guides/vulnerability-management/csaf-common-security-advisory-framework.mdx
@@ -24,6 +24,8 @@ To start publishing CSAF reports for your assets, follow these steps:
 2. Go to the **Vulnerability Management** section
 3. Enable **"Enable public access to vulnerability data"**
 
+![Enable Public Access to Vulnerability Data](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/public-access.png)
+
 Once enabled, your organization will be registered as a CSAF provider and your vulnerability data will be available through standardized CSAF endpoints.
 
 ## Accessing CSAF Data
diff --git a/src/pages/how-to-guides/vulnerability-management/customize-risk-scores.mdx b/src/pages/how-to-guides/vulnerability-management/customize-risk-scores.mdx
@@ -46,7 +46,7 @@ CIA requirements define how a vulnerability's impact should be assessed for your
    - **Availability**: Low, Medium, or High (Default: High)
 4. Click **Save**
 
-![Select CIA Requirements](../../../assets/cia-requirements-gui.png)
+![Select CIA Requirements](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/security-requirements-settings.png)
 
 <Callout type="info">
   CIA requirements apply to all existing and future vulnerability assessments for this asset.
@@ -64,7 +64,7 @@ Create tickets automatically when vulnerabilities exceed your risk thresholds:
    - Tickets auto-create for vulnerabilities with CVSS ≥ this value
 4. Set **Risk Threshold** (0-10, default: 8.0)
    - Tickets auto-create for vulnerabilities with environmental risk score ≥ this value
-![Select Risk Reporting Range](../../../assets/risk-based-ticket-thresholds-gui.png)
+![Select Risk Reporting Range](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/reporting-range-settings.png)
 
 5. Click **Save**
 
@@ -79,14 +79,14 @@ Changes apply immediately to new vulnerabilities.
 Inform DevGuard if your asset is reachable from the internet:
 
 ### Via Web UI
-![Select Reachable from Internet](../../../assets/reachable-from-the-internet-asset-gui.png)
+![Select Reachable from Internet](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/security-requirements-settings.png)
 
 In **Asset Settings**, toggle **Reachable from Internet** to contextualize risk assessments.
 
 ## Configure Vulnerability Auto-Reopen
 
 Automatically reopen accepted vulnerabilities after a period to re-evaluate fixes:
-![Select Vulnerability Auto-Reopen Period](../../../assets/vulnerability-auto-reopen-gui.png)
+![Select Vulnerability Auto-Reopen Period](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/auto-reopen-settings.png)
 
 
 ### Via Web UI
diff --git a/src/pages/how-to-guides/vulnerability-management/track-fix-progress.mdx b/src/pages/how-to-guides/vulnerability-management/track-fix-progress.mdx
@@ -80,7 +80,7 @@ DevGuard uses a **Mitigation** model to track remediation efforts with the follo
 
 Monitor fix progress across your project:
 
-![Overview of asset](../../../assets/overall-dashboard-overview-gui.png)
+![Overview of asset](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/asset-overview.png)
 
 
 1. **Dashboard Overview**: View total vulnerabilities by state
@@ -89,7 +89,7 @@ Monitor fix progress across your project:
    - Accepted or transferred items
 
 
-![avg response time for vulnerabilities](../../../assets/avg-response-remediation-time.png)
+![avg response time for vulnerabilities](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/asset-overview-v2.png)
 2. **Trend Tracking**: Historical data shows:
    - Days to fix by severity level
    - Fix rate over time
@@ -166,7 +166,7 @@ For heightened security posture:
 - Maintain independence from upstream risk assessments
 - Useful for zero-trust supply chain environments
 
-![Paranoid mode](../../../assets/paranoid-mode-gui.png)
+![Paranoid mode](https://raw.githubusercontent.com/l3montree-dev/devguard-web/refs/heads/main/e2e/docs-screenshots/paranoid-mode-settings.png)
 
 
 ## Monitoring Fix Velocity
