Dev/ncrocfer/improve doc

.github/workflows/build-deploy.yml

@@ -46,6 +46,7 @@ jobs:
           url: '${{ secrets.API_BASE_URL }}/sites/${{ vars.SITE }}/build'
           method: 'POST'
           customHeaders: '{"Authorization": "Bearer ${{ secrets.API_TOKEN }}"}'
+          timeout: 60000 # 1 minute
 
       - name: Check build status
         if: ${{ fromJson(steps.build.outputs.response).status != 0 }}
@@ -76,4 +77,3 @@ jobs:
           echo "✅ Build and deployment completed successfully!"
           echo "Build output: ${{ fromJson(steps.build.outputs.response).output }}"
           echo "Deploy output: ${{ fromJson(steps.deploy.outputs.response).output }}"
-

docs/troubleshooting.md

@@ -3,37 +3,6 @@
 !!!info
     This page contains some advice about common errors and problems encountered by OpenCVE users.
 
-## Why some CVEs are not linked to Vendors or Products?
-
-In some cases, you may notice that a CVE description references a specific product, yet the **Affected Vendors & Products** section remains empty. This is due to how OpenCVE processes and populates its database.
-
-For instance the description of the [CVE-2023-26603](https://app.opencve.io/cve/CVE-2023-26603) mentions the **Jumpcloud** project in its description, without being linked to any vendor or product:
-
-![Troubleshooting CVE-2023-26603](images/troubleshooting/cve-2023-26603.png){.center style="width:100%"}
-
-To understand this behavior, it's important to learn how OpenCVE manages the vendors and products lifecycle:
-
-- When a CVE is published, OpenCVE analyzes the CVE data and extracts any [Common Platform Enumerations (CPEs)](https://nvd.nist.gov/products/cpe) it contains.
-- These CPEs serve as the primary source from which vendors and products are identified and linked to the CVE.
-- Once linked, users can subscribe to these specific vendors and products to monitor relevant vulnerabilities.
-
-If a CVE lacks associated CPEs, then no vendor or product will be linked to it, even if the description references a product by name. This design ensures that only CVEs with explicit CPEs, and therefore confirmed vendor/product links, are tracked in OpenCVE.
-
-## Why am I seeing `404 Not Found` on some Subscriptions?
-
-OpenCVE v2 functions differently from v1 regarding how **Common Platform Enumerations (CPEs)** are managed.
-
-In v1, we began by downloading the [full CPE dictionary](https://nvd.nist.gov/products/cpe) from the [National Vulnerability Database (NVD)](https://nvd.nist.gov/). This dictionary includes numerous CPEs, some of which are not associated with any specific CVEs.
-
-In v2, we’ve taken a more streamlined approach. Rather than initially downloading the entire CPE dictionary, we analyze each CVE individually and extract relevant CPEs. Vendors and products are then derived directly from these CVEs, ensuring that each one is associated with at least one CVE in our database.
-
-This means that, while OpenCVE v2 may list fewer vendors and products, it guarantees that each one is linked to a CVE. This approach enhances both practicality and efficiency.
-
-If data from an OpenCVE v1 instance has been migrated to a v2 instance (using the `./manage.py import_from_v1` command), all the subscriptions are migrated, including vendors and products that may no longer exist in v2.
-
-In this case the solution is to use the `./manage.py fix_missing_vendors` command, so all the missing vendors and products will be created in DB and 404 errors will disappear.
-
-
 ## Why Am I Not Receiving Emails?
 
 If you encounter issues receiving emails, you can follow [this guide](guides/smtp_configuration.md) to learn how to configure and debug your email settings effectively.

mkdocs.yml

@@ -11,6 +11,10 @@ theme:
   palette:
     accent: blue
 
+plugins:
+   - glightbox:
+       zoomable: false
+
 extra_css:
   - css/extra.css
 

requirements.txt

@@ -1,2 +1,3 @@
 mkdocs==1.5.3
 mkdocs-material==9.5.1
+mkdocs-glightbox==0.5.2