chore: replace img component with Image

apps/docs/content/dotnet/how-to/build-pipeline.mdx

@@ -2,6 +2,7 @@
 title: Configure .NET build & deploy pipeline
 ---
 
+import Image from '/src/components/Image';
 import data from '@site/static/data.json';
 import UnorderedCodeList from '@site/src/components/UnorderedCodeList';
 
@@ -219,11 +220,11 @@ Some packages or tools can take a long time to install. Therefore, Zerops caches
 To invalidate the Zerops build cache go to your service detail in Zerops GUI, choose **Service dashboard & runtime containers** from the left menu and click on the **Open pipeline detail** button. Then click on the **Invalidate build cache** icon.
 
 <p align="center">
-  <img
-    src="/img/screenshots/runtime_clear_build_cache.png"
-    alt="image"
-    width="100%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/runtime_clear_build_cache.png"
+    darkImage="/img/screenshots/runtime_clear_build_cache.png"
+    alt="Runtime Clear Build Cache"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 

apps/docs/content/dotnet/how-to/build-process.mdx

@@ -1,15 +1,15 @@
 ---
 title: .NET build process
 ---
-
+import Image from '/src/components/Image';
 import data from '@site/static/data.json';
 
 <p align="center">
-  <img
-    src="/img/screenshots/build_deploy_pipeline-step2.png"
-    alt="image"
-    width="100%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/build_deploy_pipeline-step2.png"
+    darkImage="/img/screenshots/build_deploy_pipeline-step2.png"
+    alt="Build Deploy pipeline"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 

apps/docs/content/dotnet/how-to/customize-runtime.mdx

@@ -2,12 +2,14 @@
 title: Customise .NET runtime environment
 ---
 
+import Image from '/src/components/Image';
+
 <p align="center">
-  <img
-    src="/img/screenshots/build_deploy_pipeline_custom_runtime.png"
-    alt="image"
-    width="100%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/build_deploy_pipeline_custom_runtime.png"
+    darkImage="/img/screenshots/build_deploy_pipeline_custom_runtime.png"
+    alt="Build Deploy pipeline"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 

apps/docs/content/dotnet/how-to/deploy-process.mdx

@@ -2,12 +2,14 @@
 title: .NET deploy process
 ---
 
+import Image from '/src/components/Image';
+
 <p align="center">
-  <img
-    src="/img/screenshots/build_deploy_pipeline-step3.png"
-    alt="image"
-    width="100%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/build_deploy_pipeline-step3.png"
+    darkImage="/img/screenshots/build_deploy_pipeline-step3.png"
+    alt="Build Deploy pipeline"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 
@@ -83,11 +85,11 @@ Zerops keeps 10 last versions of your application in the internal storage.
 The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.
 
 <p align="center">
-  <img
-    src="/img/screenshots/pipeline_history.png"
-    alt="image"
-    width="100%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/pipeline_history.png"
+    darkImage="/img/screenshots/pipeline_history.png"
+    alt="Pipeline History"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 

apps/docs/content/dotnet/how-to/env-variables.mdx

@@ -2,6 +2,8 @@
 title: How to set and use environment variables in .NET service
 ---
 
+import Image from '/src/components/Image';
+
 Environment variables help you run your application in different environments. They allow you to isolate all specific environment aspects from your application code and keep your app encapsulated. You can create several projects in Zerops that represent different environments (development, stage, production) or even each developer can have a project with its own environment.
 
 In Zerops you do not have to create a `.env` file manually. Zerops handles the environment variables for you.
@@ -27,11 +29,11 @@ You can [reference](/dotnet/how-to/env-variables#reference-a-local-variable-in-a
 Use secret variables to store passwords, tokens and other sensitive information that shouldn't be part of your repository and listed in zerops.yml.
 
 <p align="center">
-  <img
-    src="/img/screenshots/secret_env.png"
-    alt="image"
-    width="100%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/secret_env.png"
+    darkImage="/img/screenshots/secret_env.png"
+    alt="Secrete ENVs"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 
@@ -135,11 +137,11 @@ Zerops creates several helper variables when a .NET service is created, e.g. `ho
 Generated env variables are listed on the **Environment variables** page. Scroll to the **Generated variables** section.
 
 <p align="center">
-  <img
-    src="/img/screenshots/nodejs_generated_variables.png"
-    alt="image"
-    width="100%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/nodejs_generated_variables.png"
+    darkImage="/img/screenshots/nodejs_generated_variables.png"
+    alt="Node.js Generated Variables"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 

apps/docs/content/dotnet/how-to/scaling.mdx

@@ -26,11 +26,11 @@ Each application you deploy starts with the minimum hardware resources: **CPU**
 Zerops has a preference for vertical scaling because it's faster and more precise. If the vertical auto scaling hits the defined maximum a new container is started automatically. When your application doesn't need so much power and all containers are vertically scaled down, Zerops will gradually remove whole containers.
 
 <p align="center">
-  <img
-    src="/img/screenshots/scaling2.png"
-    alt="image"
-    width="100%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/scaling2.png"
+    darkImage="/img/screenshots/scaling2.png"
+    alt="Scaling Resources"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 
@@ -128,11 +128,11 @@ Check if your application is ready to be run in multiple containers.
 If you've experienced problems with not enough power when your application starts, increase the default Start CPU core count. Alternatively switch the [CPU mode](#shared-vs-dedicated-cpu) to dedicated to allocate the stable CPU power to your application.
 
 <p align="center">
-  <img
-    src="/img/screenshots/scaling5.png"
-    alt="image"
-    width="80%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/scaling5.png"
+    darkImage="/img/screenshots/scaling5.png"
+    alt="Scaling"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 
@@ -151,11 +151,11 @@ But if your application need a more memory faster or if you have experienced pro
 3. or setting the minimum free RAM in % of the RAM assigned to the container
 
 <p align="center">
-  <img
-    src="/img/screenshots/scaling6.png"
-    alt="image"
-    width="80%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/scaling6.png"
+    darkImage="/img/screenshots/scaling6.png"
+    alt="Scaling"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 

apps/docs/content/features/env-variables.mdx

@@ -1,6 +1,7 @@
 ---
 title: Environment variables
 ---
+import Image from '/src/components/Image';
 
 Environment variables help you run your application in different environments. They allow you to isolate all specific environment aspects from your application code and keep your app encapsulated. You can create several [projects](/features/infrastructure#project) in Zerops that represent different environments (development, stage, production) or even each developer can have a project with its own environment.
 
@@ -27,11 +28,11 @@ You can reference another variable of the same service or even a variable of ano
 Use secret variables to store passwords, tokens and other sensitive information that shouldn't be part of your repository and listed in zerops.yml.
 
 <p align="center">
-  <img
-    src="/img/screenshots/runtime_secret_variables.png"
-    alt="image"
-    width="100%"
-    height="auto"
+    <Image
+    lightImage="/img/screenshots/runtime_secret_variables.png"
+    darkImage="/img/screenshots/runtime_secret_variables.png"
+    alt="Runtime Secret Variables"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 

apps/docs/content/features/pipeline.mdx

@@ -167,11 +167,11 @@ Learn more about what is included in the default build environment:
 ## Deploy phase
 
 <p align="center">
-  <img
-    src="/img/screenshots/build_deploy_pipeline-step3.png"
-    alt="image"
-    width="100%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/build_deploy_pipeline-step3.png"
+    darkImage="/img/screenshots/build_deploy_pipeline-step3.png"
+    alt="Build Deploy Pipeline"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 
@@ -256,11 +256,11 @@ Learn more about what is included in the default runtime environment:
 - [Java](/java/how-to/customize-runtime)
 
 <p align="center">
-  <img
-    src="/img/screenshots/build_deploy_pipeline_custom_runtime.png"
-    alt="image"
-    width="100%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/build_deploy_pipeline_custom_runtime.png"
+    darkImage="/img/screenshots/build_deploy_pipeline_custom_runtime.png"
+    alt="Build Deploy Pipeline"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 
@@ -327,11 +327,11 @@ You can change the deploy pipeline when you need to. Just simply modify the `zer
 When you know that the running build is not correct and you want to cancel it, you can do it in Zerops GUI. Go to the service detail, open the list of running processes and click on the **Open pipeline detail** button. Then click on the **Cancel build** button.
 
 <p align="center">
-  <img
-    src="/img/screenshots/nodejs_cancel_running_build.png"
-    alt="image"
-    width="100%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/nodejs_cancel_running_build.png"
+    darkImage="/img/screenshots/nodejs_cancel_running_build.png"
+    alt="Running build"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>
 
@@ -346,11 +346,11 @@ Zerops keeps 10 last versions of your application in the internal storage.
 The list of application versions is available in Zerops GUI. Go to the service detail and choose **Service dashboard & runtime containers** from the left menu. The active version is highlighted, show all archived version by clicking on the button below.
 
 <p align="center">
-  <img
-    src="/img/screenshots/pipeline_history.png"
-    alt="image"
-    width="100%"
-    height="auto"
+  <Image
+    lightImage="/img/screenshots/pipeline_history.png"
+    darkImage="/img/screenshots/pipeline_history.png"
+    alt="Pipeline history"
+    style={{ width: '95%', height: 'auto' }}
   />
 </p>