Merge pull request #42 from nocodb/images-breaking

Author: DarkPhoenix2704

content/docs/engineering/builds-and-releases.mdx

@@ -20,10 +20,10 @@ Below is an overview of how to make these builds and what happens behind the sce
 - Click [NocoDB release action](https://github.com/nocodb/nocodb/actions/workflows/release-nocodb.yml)
 - You should see the below screen
 
-  ![image](https://user-images.githubusercontent.com/35857179/167240353-a02f690f-c865-4ade-8645-64382405c9ea.png)
+  ![NocoDB Release Workflow](/img/v2/engineering/release-workflow.png)
 - Change `Use workflow from` to `Branch: master`. If you choose the wrong branch, the workflow will be ended.
 
-  ![image](https://user-images.githubusercontent.com/35857179/167240383-dda05f76-8323-4f4a-b3e7-9db886dbd68d.png)
+  ![Release Branch Selection](/img/v2/engineering/release-branch-selection.png)
 - Then there would be two cases - you can either leave target tag and pervious tag blank or manually input some values
 
 - Target Tag means the target deployment version, while Previous Tag means the latest version as of now. Previous Tag is used for Release Note only - showing the file / commit differences between two tags.
@@ -90,7 +90,7 @@ Open issues marked with label `Status: Fixed` and `Status: Resolved` will be clo
 
 Example:
 
-![image](https://user-images.githubusercontent.com/35857179/167241574-f8f7061f-c689-444a-b761-0a727974c53f.png)
+![Close Issues Example](/img/v2/engineering/close-issues-example.png)
 
 #### publish-docs
 
@@ -120,10 +120,10 @@ NocoDB has github actions which creates docker and binaries for each PR! And the
 
 Example shown below
 - Go to a PR and click on the comment.
-<img width="1111" alt="Screenshot 2023-01-23 at 15 46 36" src="https://user-images.githubusercontent.com/5435402/214083736-80062398-3712-430f-9865-86b110090c91.png" />
+![PR Comment Timely Build](/img/v2/engineering/pr-comment-timely-build.png)
 
 - Click on the link to copy the docker image and run it locally.
-<img width="1231" alt="Screenshot 2023-01-23 at 15 46 55" src="https://user-images.githubusercontent.com/5435402/214083755-945d9485-2b9e-4739-8408-068bdf4a84b7.png" />
+![Docker Copy Command](/img/v2/engineering/docker-copy-command.png)
 
 
 This is to
@@ -138,7 +138,7 @@ When a non-draft Pull Request is created, reopened or synchronized, a timely bui
 
 The docker images will be built and pushed to Docker Hub (See [nocodb/nocodb-timely](https://hub.docker.com/r/nocodb/nocodb-timely/tags) for the full list). Once the image is ready, GitHub bot will add a comment with the command in the pull request. The tag would be `<NOCODB_CURRENT_VERSION>-pr-<PR_NUMBER>-<YYYYMMDD>-<HHMM>`.
 
-![image](https://user-images.githubusercontent.com/35857179/175012097-240dab05-da93-4c4e-87c1-1c36fb1350bd.png)
+![Timely Build Comment](/img/v2/engineering/timely-build-comment.png)
 
 ## Executables or Binaries
 
@@ -155,7 +155,7 @@ Currently, we only support the following targets:
 
 Once the executables are ready, GitHub bot will add a comment with the commands in the pull request.
 
-![image](https://user-images.githubusercontent.com/35857179/175012070-f5f3e7b8-6dc5-4d1c-9f7e-654bc5039521.png)
+![Executables Comment](/img/v2/engineering/executables-comment.png)
 
 NocoDB creates Docker and Binaries for each PR.
 

content/docs/engineering/development-setup.mdx

@@ -46,7 +46,7 @@ CI-CD will be triggered on moving a PR from draft state to `Ready for review` st
 
 For Playwright tests, screenshots are captured on the tests. These will provide vital clues for debugging possible issues observed in CI-CD. To access screenshots, Open link associated with CI-CD run & click on `Artifacts`
 
-![Screenshot 2022-09-29 at 12 43 37 PM](https://user-images.githubusercontent.com/86527202/192965070-dc04b952-70fb-4197-b4bd-ca7eda066e60.png)
+![CI-CD Artifacts](/img/v2/engineering/ci-cd-artifacts.png)
 
 
 

content/docs/engineering/translation.mdx

@@ -19,22 +19,22 @@ tags: ['Engineering']
 - Setup [Crowdin](https://crowdin.com) account
 - Join [NocoDB](https://crowdin.com/project/nocodb) project
 
-![Screenshot 2022-09-08 at 10 26 23 PM](https://user-images.githubusercontent.com/86527202/189181511-51b8671e-bee8-45d5-8216-a4a031bc6309.png)
+![Crowdin Join Project](/img/v2/engineering/crowdin-join-project.png)
 
 - Click the language that you wish to contribute
 
-![Screenshot 2022-09-08 at 10 29 56 PM](https://user-images.githubusercontent.com/86527202/189182132-0eed7d5a-eaa1-43e1-929d-688f375763c1.png)
+![Crowdin Select Language](/img/v2/engineering/crowdin-select-language.png)
 
 - Click the `Translate` button; this opens up `Crowdin Online Editor`
 
-![Screenshot 2022-09-08 at 10 32 17 PM](https://user-images.githubusercontent.com/86527202/189182450-999124e8-566c-40af-9d3c-731a11c1b6aa.png)
+![Crowdin Translate Button](/img/v2/engineering/crowdin-translate-button.png)
 
 - Select string in `English` on the left-hand menu bar [1]
 - Propose changes [2]
 - Save [3]
 Note: Crowdin provides translation recommendation's as in [4]. Click directly if it's apt
 
-![Screenshot 2022-09-08 at 10 37 38 PM](https://user-images.githubusercontent.com/86527202/189184278-69d688ed-4e5a-4d5a-b629-9f6d10d79346.png)
+![Crowdin Online Editor](/img/v2/engineering/crowdin-online-editor.png)
 
 A GitHub Pull Request will be automatically triggered (periodicity- 6 hours). We will follow up on remaining integration work items.
 
@@ -57,10 +57,10 @@ Refer following articles to get additional details about Crowdin Portal usage
 - Select target language, `Update`
 - Update array in `tests/playwright/tests/language.spec.ts`  
 
-![Screenshot 2022-09-08 at 10 52 59 PM](https://user-images.githubusercontent.com/86527202/189186570-5c1c7cad-6d3f-4937-ab4d-fa7ebe022cb1.png)
+![Crowdin Language Settings](/img/v2/engineering/crowdin-language-settings-1.png)
 
 
-![Screenshot 2022-09-08 at 10 54 04 PM](https://user-images.githubusercontent.com/86527202/189186632-0b9f5f55-0550-4d8f-a8ae-7e9b9076774e.png)
+![Crowdin Language Update](/img/v2/engineering/crowdin-language-settings-2.png)
 
 
 ## String Categories

content/docs/fields/field-types/formula/formula.mdx

@@ -25,7 +25,7 @@ keywords: ['Fields', 'Field types', 'Formula', 'Create formula field']
 
 <Callout type="info">
 Unlike other field types, formula cells cannot be modified by double-clicking since the value is generated based on the formula.
-<img width="253" alt="image" src="https://user-images.githubusercontent.com/35857179/189109486-4d41f2b7-0a19-46ef-8bb4-a8d1aabd3592.png" />
+![Formula Cell Read-only](/img/v2/fields/formula-cell-readonly.png)
 
 </Callout>
 

content/self-hosting/installation/digital-ocean.mdx

@@ -10,26 +10,26 @@ Follow these steps to deploy NocoDB on DigitalOcean using their App Platform.
 
 1. On the DigitalOcean homepage, click on the Create icon and select "Apps (Deploy your code)".
 
-    [![DigitalOcean Create App](https://user-images.githubusercontent.com/86527202/154790558-f8fe5580-5a58-412c-9c2e-145587712bf2.png)](https://user-images.githubusercontent.com/86527202/154790558-f8fe5580-5a58-412c-9c2e-145587712bf2.png)
+    ![DigitalOcean Create App](/img/v2/installations/digitalocean-create-app.png)
 2. Choose "Docker Hub" as the source.
 
-    [![DigitalOcean Docker Hub](https://user-images.githubusercontent.com/86527202/154790563-b5b6d5b4-0bdc-4718-8cea-0a7ee52f283b.png)](https://user-images.githubusercontent.com/86527202/154790563-b5b6d5b4-0bdc-4718-8cea-0a7ee52f283b.png)
+    ![DigitalOcean Docker Hub](/img/v2/installations/digitalocean-docker-hub.png)
 
 3. Set the source repository as nocodb/nocodb. You can optionally specify a release tag if you want a specific NocoDB version.
 
-   [![DigitalOcean Docker Hub](https://user-images.githubusercontent.com/86527202/154790564-1dcb5e33-3a57-471a-a44c-835a410a0cb7.png)](https://user-images.githubusercontent.com/86527202/154790564-1dcb5e33-3a57-471a-a44c-835a410a0cb7.png)
+   ![DigitalOcean Set Repository](/img/v2/installations/digitalocean-set-repository.png)
 
 4. Configure any additional settings as needed.
 
-   [![DigitalOcean Docker Hub](https://user-images.githubusercontent.com/86527202/154790565-c0234b2e-ad50-4042-90b6-4f8798f1d585.png)](https://user-images.githubusercontent.com/86527202/154790565-c0234b2e-ad50-4042-90b6-4f8798f1d585.png)
+   ![DigitalOcean Configure Settings](/img/v2/installations/digitalocean-configure-settings.png)
 
 5. Name your web service and select the nearest region for cloud hosting.
 
-   [![DigitalOcean Docker Hub](https://user-images.githubusercontent.com/86527202/154790567-a6e65e4e-9aa0-4edb-998e-da8803ad6e23.png)](https://user-images.githubusercontent.com/86527202/154790567-a6e65e4e-9aa0-4edb-998e-da8803ad6e23.png)
+   ![DigitalOcean Name Service](/img/v2/installations/digitalocean-name-service.png)
 
 6. Choose your preferred hosting plan and click on "Launch Basic App".
 
-   [![DigitalOcean Docker Hub](https://user-images.githubusercontent.com/86527202/154790570-62044713-5cca-4d06-82ec-f3cc257218a1.png)](https://user-images.githubusercontent.com/86527202/154790570-62044713-5cca-4d06-82ec-f3cc257218a1.png)
+   ![DigitalOcean Hosting Plan](/img/v2/installations/digitalocean-hosting-plan.png)
 
     Your application will be built, and the URL will be live shortly. The URL will look something like https://your-app-name.ondigitalocean.app/.
 

content/self-hosting/installation/other-installations.mdx

@@ -16,19 +16,19 @@ Cloudron provides an easy way to install and manage NocoDB.
 1. Log in to your Cloudron dashboard.
 2. Navigate to the App Store.
 
-   ![https://user-images.githubusercontent.com/35857179/194700146-aae90503-a8fd-4bc5-8397-39f0bc279606.png](https://user-images.githubusercontent.com/35857179/194700146-aae90503-a8fd-4bc5-8397-39f0bc279606.png)
+   ![Cloudron App Store](/img/v2/installations/cloudron-app-store.png)
 3. Search for NocoDB
 
-    ![https://user-images.githubusercontent.com/35857179/194700181-b5303919-70b8-4cf8-bebe-7e75aca601f3.png](https://user-images.githubusercontent.com/35857179/194700181-b5303919-70b8-4cf8-bebe-7e75aca601f3.png)
+    ![Cloudron Search NocoDB](/img/v2/installations/cloudron-search-nocodb.png)
 4. Click on the NocoDB app, then click "Install".
 
-    ![https://user-images.githubusercontent.com/35857179/194700192-d702f5c2-2afa-45c5-9823-4ebe9e141b01.png](https://user-images.githubusercontent.com/35857179/194700192-d702f5c2-2afa-45c5-9823-4ebe9e141b01.png)
+    ![Cloudron Install](/img/v2/installations/cloudron-install.png)
 5. Configure NocoDB settings as needed.
 
-    ![https://user-images.githubusercontent.com/35857179/194700230-c35e934f-bd93-4948-8f31-935483b30571.png](https://user-images.githubusercontent.com/35857179/194700230-c35e934f-bd93-4948-8f31-935483b30571.png)
+    ![Cloudron Configure](/img/v2/installations/cloudron-configure.png)
 5. Once installed, go to "My Apps" and launch NocoDB.
 
-    ![https://user-images.githubusercontent.com/35857179/194700464-50098cb1-bf94-42bb-a63a-cc0aad671913.png](https://user-images.githubusercontent.com/35857179/194700464-50098cb1-bf94-42bb-a63a-cc0aad671913.png)
+    ![Cloudron My Apps](/img/v2/installations/cloudron-my-apps.png)
 
 #### Important Notes
 - Ensure your Cloudron server meets the minimum requirements for running NocoDB.
@@ -42,14 +42,14 @@ Cloudron provides an easy way to install and manage NocoDB.
 1. Log in to your CapRover dashboard.
 2. Go to "Apps" and click on "One-Click Apps/Databases".
 
-    ![https://user-images.githubusercontent.com/35857179/194701420-7fe5c396-a488-456c-98de-6f2ee1151fc5.png](https://user-images.githubusercontent.com/35857179/194701420-7fe5c396-a488-456c-98de-6f2ee1151fc5.png)
+    ![CapRover One-Click Apps](/img/v2/installations/caprover-one-click-apps.png)
 3. Search for NocoDB and click on it.
 
-    ![https://user-images.githubusercontent.com/35857179/194701537-63e7efc5-013b-4ca9-8659-56e9d536e7d0.png](https://user-images.githubusercontent.com/35857179/194701537-63e7efc5-013b-4ca9-8659-56e9d536e7d0.png)
+    ![CapRover Search NocoDB](/img/v2/installations/caprover-search-nocodb.png)
 4. Click on NocoDB to start the configuration process.
 5. Configure NocoDB settings as needed and click "Deploy".
 
-    ![https://user-images.githubusercontent.com/35857179/194701576-19519df5-2aa4-435d-8fc6-7bc684b9cfe1.png](https://user-images.githubusercontent.com/35857179/194701576-19519df5-2aa4-435d-8fc6-7bc684b9cfe1.png)
+    ![CapRover Deploy](/img/v2/installations/caprover-deploy.png)
 6. Once deployed, you can access NocoDB from the provided URL.
 
 #### Important Notes
@@ -65,11 +65,11 @@ Cloudron provides an easy way to install and manage NocoDB.
 1. Go to Railway Templates.
 2. Search for "NocoDB" in the templates list.
 
-    ![https://user-images.githubusercontent.com/35857179/194702833-1bea22ee-6dfa-4024-ac27-e33fe56e5500.png](https://user-images.githubusercontent.com/35857179/194702833-1bea22ee-6dfa-4024-ac27-e33fe56e5500.png)
+    ![Railway Templates](/img/v2/installations/railway-templates.png)
 3. Click on the NocoDB template, then click "Deploy".
 4. Configure your NocoDB settings as needed.
 
-    ![https://user-images.githubusercontent.com/35857179/194702960-149393fe-b00f-4d84-9e54-22cb7616ba44.png](https://user-images.githubusercontent.com/35857179/194702960-149393fe-b00f-4d84-9e54-22cb7616ba44.png)
+    ![Railway Configure](/img/v2/installations/railway-configure.png)
 5. Railway will automatically deploy your NocoDB instance.
 
 #### Important Notes