Portals and CMS: responsive slots, lazy loading, and derivative WebP passes hit JPEG twice—sign off in the editor, not only locally
`cms-visio-jpg` covers article heroes, doc-library cards, and help-center figures. Content columns apply `max-width` scaling plus `srcset`, so a single giant JPEG from legacy .vsd may become unreadable on phones. Size separately for list vs body slots or configure focal crops; compare sRGB originals to WebP/AVIF derivatives for color and sharpening drift, and test light/dark themes on staging.
CMS workflow: read template slot widths and DPR, upload pilots, validate lazy-load placeholders and hi-res layers in published styling
- Confirm `picture`/`srcset` rules with frontend, compute `@1x/@2x` needs, and export distinct cover vs inline JPEGs—do not upload a 4000px master expecting CSS to fix everything.
- Open articles on staging, scroll to trigger lazy loading, throttle networks to see blur-up duration; if LCP suffers, trim bytes and simplify art before chasing more pixels.
- Store alt text plus linked .vsd revision ids in the media library; bump object keys with date fragments when replacing art so CDN caches invalidate predictably.
VSD to JPG (CMS) FAQ: responsive slots, srcset, lazy load, theme skins, transcode drift
Figures look sharp on desktop but soft on phones—insufficient width or `object-fit` cropping?
Measure rendered box pixels in devtools vs source JPEG; if boxes are narrower than needed, export to the slot width and verify `object-fit` is not clipping corner badges.
CDN WebP shifts brand colors slightly—ICC issue or encoder tuning?
Sample hex values from source JPEG vs derivative under sRGB workflows; if only derivatives drift, tune encoder quality/sharpening; if sources drift, fix Visio export.
Editors auto-generate social share crops from inline art—how do we stop 1.91:1 mangles?
Model separate `og:image` assets with hand-tuned crops; never auto-chop technical figures meant for wide layouts.
Dark theme makes white JPEGs glare but newsletters still need light skins—maintain two?
Bind different media per theme field rather than one URL for both; or standardize on neutral gray JPEGs that survive both skins and document which feed uses which.
Search still shows old thumbnails after media swaps—cache busting?
Bump query strings or object keys and request search re-crawl; log replacement timestamps and hashes so you know public indexes lagged editorial truth.