Media Delivery Infrastructure — Scope Explainer

What it means & why it matters

What SessDev includes

• next/image components wired across the codebase so every image goes through the optimization pipeline instead of being served raw.
• CDN binding for the image origin: requests served from the edge, with cache headers tuned per asset class.
• Automatic srcset / sizes generation per breakpoint so a phone never downloads a 4K hero image.
• Modern-format negotiation: AVIF and WebP served when supported, with graceful fallback to JPEG / PNG for legacy clients.
• Lazy loading enabled by default below the fold; above-the-fold images marked priority so LCP is not delayed.
• Low-quality image placeholders (LQIP / blurDataURL) on key components so the layout does not jump while the real image streams in.
• Alt-text enforced at the component / CMS-field level: an image without alt fails type-check or fails the build, not silently ships.
• Responsive wrappers for embedded video (YouTube, Vimeo, MP4) with privacy-friendly defaults and aspect-ratio locking.
• 1 end-to-end validation pass: Core Web Vitals checked on representative pages, alt-text coverage audited, format negotiation verified.

What is excluded

• Photography, photo direction, on-site shoots, retouching or photo editing.
• Video production, scripting, shooting, editing, color grading, motion graphics or post-production.
• Illustration, icon-set design, custom artwork or any original visual creation.
• Alt-text copywriting strategy, descriptive caption authoring or SEO-tuned image descriptions; SessDev enforces the field, the client supplies the words.
• Stock-image licensing, model releases, music licensing, font-in-image licensing or any rights clearance.
• Mood boards, art direction, brand-image curation or visual-identity development.
• Color grading, advanced retouching, background removal at scale, compositing or any pixel-level work beyond automated transforms.
• Sourcing assets from stock libraries, agencies or marketplaces on behalf of the client.
• Standalone digital-asset-management systems beyond the CMS or vendor folder structure.
• Custom video encoding pipelines, HLS / DASH streaming, DRM or live-broadcast infrastructure.
• Post-launch image audits, ongoing weight optimization, periodic re-encoding or alt-text refresh cycles.

Risks if this is mis-configured

• Core Web Vitals regression

  An unoptimized 2 MB hero image quietly inflates LCP from 1.2 s to 4 s. Google demotes the page; the team blames 'SEO drift' when the real cause is one image bypassing the pipeline. Without monitoring, this lands in production unnoticed.

• Licensing exposure

  Using stock images without a valid license, embedding fonts inside graphics, or shipping AI-generated images without provenance creates real legal exposure. SessDev enforces the delivery layer; license validity is the client's responsibility.

• Hotlink abuse

  If the origin is not protected, third-party sites can hotlink your images. Your CDN bill grows while their site is the one converting on your bandwidth.

• Format support drift

  Browser support for AVIF and WebP evolves; CDN vendors deprecate transform options without warning. Without periodic audits, a working build silently regresses to JPEG for everyone and the image weight doubles.

• Missing alt-text

  Images without alt-text fail accessibility audits (WCAG 1.1.1), hurt SEO image indexing and break the experience for screen-reader users. Type-level enforcement prevents the build from regressing; turning that enforcement off is a documented decision.

• CDN bill shock

  A traffic spike or a viral page can multiply image bandwidth by 10x. Free-tier ceilings are hit silently and either the site throttles or the invoice jumps. Care plans monitor quotas; without them the first signal is an unexpected charge.

• Stale asset versions

  If a CMS-uploaded image is cached aggressively at the CDN without versioning, updating the image in the CMS does not refresh it on the live site for hours or days. Editors lose trust in the pipeline within one incident.

Related scope items

• content_injectionThe media you supply is integrated through the delivery layer the same way text is integrated through the content layer.
• cms_blog_setupImages uploaded through the CMS flow through this delivery pipeline automatically.
• technical_seoImage sitemaps, alt-text coverage and LCP performance directly feed the technical SEO layer.
• brand_asset_injectionLogos and brand-controlled visuals are injected as media but governed by the brand-asset clause.
• multilingual_archLocale-aware media (region-specific imagery) is supported by the pipeline but not produced by SessDev.
• analytics_integrationAnalytics measures which media drives engagement; the delivery layer does not include reporting on its own.

Frequently asked questions

Does SessDev provide the images and video?

No. SessDev integrates the media you supply (or your creative agency supplies). Photography, videography, illustration and stock sourcing are creative-services work and sit outside the build.

Do you handle image and font licensing?

No. Licensing — stock photos, model releases, music, fonts embedded in graphics — is the client's responsibility. SessDev does not validate license chains and does not assume legal liability for unlicensed media.

Is video included?

Responsive wrappers for embedded video (YouTube, Vimeo, MP4) are included. Video production, custom encoding pipelines, live streaming or DRM are out of scope.

Which image formats do you support?

AVIF and WebP are served when the browser supports them, with automatic fallback to JPEG / PNG. SVG is supported for vector assets. Heavier formats (RAW, HEIC, TIFF) are converted at upload time, not served directly.

Can our team update images later without a developer?

Yes, if a CMS is in scope: editors upload through the CMS and the delivery pipeline picks up the new asset automatically. Without a CMS, image updates flow through your normal deploy process.