Every file name you commit toDocumentation 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.
tutosrive/images-projects-srm-trg becomes a permanent segment of its jsDelivr CDN URL. Because these URLs are embedded in documentation, README files, and deployed applications, a poorly chosen name is extremely costly to change — updating it means creating a new URL and hunting down every reference. Consistent, descriptive naming also makes it possible for contributors to find the right file at a glance without downloading the whole repository. The conventions below are derived from the patterns already in use across the repository’s existing folders.
File naming rules
General format
- Use lowercase letters and hyphens as word separators in most cases.
- ✅
initvenv-tag-preview.png - ✅
chromolog-webpage.png - ❌
InitVenv Tag Preview.png(spaces not allowed) - ❌
chromolog webpage.png(spaces become%20in URLs)
- ✅
- Underscores are acceptable for logo files in the
modules/folder, where the existing convention uses them:- ✅
chromalog_logo.webp,sqlazo_logo.webp,chronolog_logo.webp - New contributions to other folders should still prefer hyphens.
- ✅
- Never use special characters such as
(,),&,#,@, or accented letters in file names — they must be percent-encoded in URLs and cause broken links.
Version suffixes
When an asset is tied to a specific release of a project, append the version with a-v prefix:
dev2forge/logos/:
Numbered screenshots
Sequential screenshots of a UI flow should use a numeric prefix followed by a short description of what the screen shows:dev2forge/bridgex/. For simpler series without descriptions, a bare number is also acceptable (as seen in img-pdftoword/v2.1.2-IMG/):
Preview images
Preview or showcase images that appear in a documentation page or storefront listing should follow this prefix pattern:dev2forge/pymd/bridge/ and dev2forge/pymd/bridgex/:
Logo files
Logo files should include both the project name and version so multiple logo versions can coexist in the same folder:Animated demo files
Animated GIFs demonstrating a feature or usage example should use a descriptive name that clearly conveys what the animation shows:File names are permanent segments of CDN URLs. Once a URL is published and referenced in documentation or production apps, renaming the file creates a dead link everywhere that URL appears. Choose your file name carefully before pushing — treat it as a permanent public API.
Directory structure rules
Group assets by project at the top level
Each top-level directory corresponds to one project or product. Do not mix assets from different projects in the same folder.Use versioned subdirectories for release-specific assets
When a project ships multiple versions with different screenshots, create a subdirectory per version using the patternv<version>-<type>/:
Use nested folders for sub-project variants
When one tool has distinct variants or build configurations, nest them under a shared parent:Supported file formats
| Format | Extension | Best for |
|---|---|---|
| PNG | .png | Screenshots, UI previews, images with transparency |
| WEBP | .webp | Logos, thumbnails — smaller file size than PNG/JPEG |
| SVG | .svg | Icons, logos — resolution-independent and scalable |
| GIF | .gif | Animated demos, feature walkthroughs |
| ICO | .ico | Windows application icons |
| JPG / JPEG | .jpg / .jpeg | Photos and complex imagery without transparency |
Prefer WEBP over PNG for logos and static illustrations — it typically achieves 25–35 % smaller file sizes, which reduces CDN bandwidth and speeds up page loads. Use SVG wherever the image is a vector graphic, since SVGs scale to any resolution without quality loss. Reserve GIF for animated demos only; static images should never be GIFs.
Real naming examples from the repository
The table below shows actual file names drawn from the repository alongside the patterns they follow:| File | Folder | Pattern applied |
|---|---|---|
dev2forge-logo.webp | dev2forge/ | <project>-logo.<ext> |
thumbanil-dev2forge.png | dev2forge/ | descriptive thumbnail name |
preview-eval-dev2forge.png | dev2forge/ | preview-<description>.<ext> |
bridgex-v0.1.0.webp | dev2forge/logos/ | <project>-v<version>.<ext> |
pdf2wordx-v2.1.2.svg | dev2forge/logos/ | <project>-v<version>.<ext> |
icon.ico | dev2forge/InitVenv/ | short descriptive name |
initvenv-tag-preview.png | dev2forge/InitVenv/ | <project>-<description>.png |
initvenv-explain-explorer1.png | dev2forge/InitVenv/ | <project>-<description><N>.png |
1-main-screen.png | dev2forge/bridgex/ | <N>-<description>.png |
preview-1-main.png | dev2forge/pymd/bridge/ | preview-<N>-<description>.png |
bridgex-logo-animated.webp | dev2forge/pymd/bridgex/ | <project>-logo-animated.<ext> |
pdf2wordx-v2.1.2-1.png | img-pdftoword/v2.1.2-IMG/ | <project>-v<version>-<N>.png |
testing-card-weather-V1.gif | NBAI/ | <action>-<feature>-<version>.gif |
chromalog_logo.webp | modules/ | <project>_logo.<ext> (modules convention) |
chromolog.gif | modules/ | <project>.<ext> (animated usage demo) |
sqlazo-webpage.png | modules/ | <project>-webpage.png |
01d.svg | NBAI/openweather/ | OpenWeather icon code convention |
404-yellow1.gif | others/ | <description><N>.gif |