Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/tutosrive/images-projects-srm-trg/llms.txt

Use this file to discover all available pages before exploring further.

Contributing assets to the Dev Forge CDN repository makes your images, logos, and icons immediately accessible via jsDelivr — a free, fast, and globally distributed CDN — using a permanent, version-pinned URL. The repository tutosrive/images-projects-srm-trg acts as a static file store: every file you commit is served directly from GitHub through jsDelivr with no build step or deployment pipeline required. This guide walks you through cloning the repository, placing your file in the correct folder, updating the folder’s README.md index, and constructing a stable CDN URL once your commit lands.
Before you begin, make sure you have the following installed and configured:

​
Contribution steps

1

Clone the repository

Clone the repository locally:
git clone https://github.com/tutosrive/images-projects-srm-trg.git
cd images-projects-srm-trg
If you already have a local clone, make sure it is up to date before adding new files:
git pull origin main
2

Place your file in the correct directory

Assets are organized into top-level project folders. Choose the folder that matches the project your asset belongs to and drop your file there. If no suitable folder exists, create a new one following the same flat structure.
images-projects-srm-trg/
├── dev2forge/               # Dev Forge platform assets
│   ├── logos/               # Versioned project logos (.webp, .svg, .png)
│   ├── InitVenv/            # InitVenv tool screenshots & icons
│   ├── bridgex/             # BridgeX numbered screen captures
│   └── pymd/
│       ├── bridge/          # PyMD Bridge variant previews
│       ├── bridgex/         # PyMD BridgeX variant previews
│       └── previews-beta/   # Beta-stage preview images
├── NBAI/                    # NBAI app assets
│   ├── openweather/         # OpenWeather SVG condition icons
│   └── ships/svg/           # Ship SVG illustrations
├── modules/                 # Python module logos & usage GIFs
│   │                        # (ChromoLog, SQLazo, ChronoLogger)
├── img-pdftoword/           # pdf2wordx versioned screenshots
│   ├── v1.0-Alpha/
│   ├── v2.0.0-IMG/
│   ├── v2.0.1-IMG/
│   └── v2.1.2-IMG/
├── svg-icons-flags-cursor/  # UI icons, flag SVGs, cursors
│   ├── cursors/
│   ├── flags-svg/
│   └── icon/
├── esrm/                    # e-SRM assets
├── pdf2docx/                # pdf2docx sample images
├── sites/                   # Other site screenshots
│   └── ouo.io/
├── random_names.onderender.com/  # Random names site assets
└── others/                  # Miscellaneous & ferreandina-nosql images
    └── ferreandina-nosql/
        ├── branches/
        ├── categories/
        ├── products/
        ├── suppliers/
        └── workers/
Use descriptive, lowercase file names separated by hyphens (not spaces) so the resulting CDN URL is human-readable and easy to share. For example, prefer initvenv-explain-explorer1.png over screenshot_final_v2 COPY.png.
3

Update the README.md in the target folder

Every folder contains a README.md that serves as a human-readable index of its assets. Add a row for your new file following the three-column table format used across the repository:
| file | link | preview |
| --   |  --  | --      |
| your-asset-name.png | [Link](https://cdn.jsdelivr.net/gh/tutosrive/images-projects-srm-trg@<COMMIT_SHA>/path/to/your-asset-name.png) | ![img](https://cdn.jsdelivr.net/gh/tutosrive/images-projects-srm-trg@<COMMIT_SHA>/path/to/your-asset-name.png) |
Columns explained:
ColumnPurpose
fileThe file name as it appears in the folder
linkA clickable hyperlink to the jsDelivr CDN URL
previewAn inline ![img](…) tag so the table renders a thumbnail on GitHub
You can use @main as the ref while preparing your commit; once your commit is pushed you should update the ref to a pinned commit SHA (see step 5) so the link remains stable even if the file is later moved.
Some folders in the repository (such as dev2forge/README.md) use slightly different column headers like File Name, Link en GitHub, and Vista previa CDN. Match the header style that already exists in whichever folder you are editing — the three-column structure is what matters for consistency.
4

Commit and push your changes

Stage both your new asset and the updated README.md, then push to your branch:
git add .
git commit -m "feat: add <asset-name> to <project-folder>"
git push origin main
Replace <asset-name> with the actual file name and <project-folder> with the target directory, for example:
git commit -m "feat: add chromolog-v0.3.0.webp to dev2forge/logos"
Do not upload files that contain sensitive, private, or proprietary content — API keys, passwords, internal screenshots, personally identifiable information, or assets you do not own the rights to. Everything committed to this repository is publicly accessible via the CDN with no authentication required.
5

Get the commit SHA and construct your pinned CDN URL

After your commit lands on main, retrieve the full 40-character commit SHA from GitHub. You can find it in two ways:Option A — GitHub web UI:
  1. Open the repository on GitHub: https://github.com/tutosrive/images-projects-srm-trg
  2. Click Commits (above the file list)
  3. Locate your commit and click the copy icon next to the short SHA on the right
Option B — Git CLI:
git log --oneline -5
# Example output:
# dd775fc feat: add icon.ico to dev2forge/InitVenv
# d7a4b45 feat: add quote.jpg to dev2forge/InitVenv
Then retrieve the full SHA:
git rev-parse dd775fc
# dd775fc24cf6c63171b85694bd0b7d567f055676
Construct the pinned URL using the full SHA:
https://cdn.jsdelivr.net/gh/tutosrive/images-projects-srm-trg@<FULL_SHA>/<folder>/<file>
Real examples from the repository:
# InitVenv icon — pinned to a specific commit
https://cdn.jsdelivr.net/gh/tutosrive/images-projects-srm-trg@dd775fc24cf6c63171b85694bd0b7d567f055676/dev2forge/InitVenv/icon.ico

# InitVenv tag preview — pinned to another commit
https://cdn.jsdelivr.net/gh/tutosrive/images-projects-srm-trg@db610fff56de446492611132cc5dc85b3cade010/dev2forge/InitVenv/initvenv-tag-preview.png

# Dev Forge logo — referenced via @main (floating ref)
https://cdn.jsdelivr.net/gh/tutosrive/images-projects-srm-trg@main/dev2forge/dev2forge-logo.webp
Pin CDN URLs to a specific commit SHA whenever possible. A @main reference is convenient during development but will silently serve a different file if the asset is ever overwritten. Pinned SHAs are permanent and immune to future changes.

Build docs developers (and LLMs) love

Get started for freeTalk to us