Docs
Images
Where every image on VendorFinder lives, how to name it, and how content refers to it.
Every image the site uses lives in one version-controlled folder, public/images/, with one subfolder per purpose. Nothing is stored next to content files, so adding, replacing, or auditing images always happens in the same place.
| Folder | What goes there | Referenced from | Served at |
|---|---|---|---|
public/images/articles/ |
Article portraits and in-article images | portrait: frontmatter and  in article bodies |
/images/articles/… |
public/images/authors/ |
Author and maker photos | photo: in content/authors/*.md |
/images/authors/… |
public/images/organizations/ |
Company logos | logo: in content/organizations/*.md |
/images/organizations/… |
public/images/products/ |
Product logos, screenshots, and video posters | logo: and screenshots: in content/products/*.md |
/images/products/… |
public/images/services/ |
Service logos | logo: in content/services/*.md |
/images/services/… |
public/images/brand/ |
Default share image (og-default.png, with its og-default.svg source) and the default avatar |
src/config/site.config.ts |
/images/brand/… |
public/images/readme/ |
Illustrations for the repository README | README.md |
not linked from the site |
The favicon SVG and the per-article share images are generated at build time. The raster favicons (public/favicon.ico and apple-touch-icon.png, icon-192.png, icon-512.png in public/images/brand/) come from the same drawing: run pnpm favicons after changing it in src/lib/brand-mark.ts.
Referring to images
Content always uses the bare filename; the site adds the folder automatically.
---
portrait: "Digital-Platforms-Reshape-Sports-Fandom.webp" # → public/images/articles/
photo: "jane-smith.jpg" # → public/images/authors/
logo: "acme-corp.svg" # → public/images/organizations/
---
 <!-- → public/images/articles/ -->
Each content type looks in its own folder, so the same field name can point to different places: logo: "acme.svg" in a company file resolves to /images/organizations/acme.svg, in a product file to /images/products/acme.svg, and in a service file to /images/services/acme.svg. Product screenshots (src, and poster for video slides) resolve to /images/products/ too.
A full URL (https://…) or a root path (/images/…) also works and is used as-is.
Naming and formats
- Filenames are case-sensitive on the live server.
My-Image.webpandmy-image.webpare different files — match the frontmatter exactly. - Use hyphens, no spaces:
cold-chain-sensors.webp. - Prefer WebP for photos and illustrations, SVG for logos and diagrams with flat colour.
- Article portraits are shown at 1200×630 and cropped to fill; supply at least 1600 px wide.
- Author photos are shown square; supply at least 640×640.
- Keep files under ~500 KB. Images are served exactly as stored — there is no automatic resizing.
Adding or replacing an image
- Put the file in the right subfolder of
public/images/. - Reference it by filename in the content file.
- Commit the image together with the content change, so the history shows which article introduced it.
To replace an image, overwrite the file with the same name. To remove one, first search the content for its filename so nothing is left pointing at it.