fix(blog): use unoptimized tag for image assets

[waleedlatif1]

Summary

• use unoptimized tag for image assets

Type of Change

• Bug fix

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
docs	Skipped		Dec 15, 2025 5:28am

[greptile-apps]

Greptile Overview

Greptile Summary

This PR adds the unoptimized prop to all Next.js Image components used in the blog/studio pages. This bypasses Next.js's built-in image optimization API for blog assets.

• Added unoptimized to blog post header images, related post cards, author avatars, blog listing images, and MDX inline images
• Follows existing patterns in the codebase where unoptimized is already used for user avatars, brand logos, and other images
• Blog images are stored locally in /public/studio/ and are already optimized PNG files

Confidence Score: 5/5

• This PR is safe to merge - simple prop additions with no logic changes or security implications.
• The change is minimal and consistent: adding unoptimized boolean prop to Image components. No business logic changes, no new dependencies, and follows existing codebase patterns.
• No files require special attention.

Important Files Changed

File Analysis

Filename	Score	Overview
apps/sim/app/(landing)/studio/[slug]/page.tsx	5/5	Added unoptimized prop to main blog post image and related posts images, bypassing Next.js image optimization.
apps/sim/app/(landing)/studio/authors/[id]/page.tsx	5/5	Added unoptimized prop to author avatar and post card images.
apps/sim/app/(landing)/studio/page.tsx	5/5	Added unoptimized prop to blog listing page post images.
apps/sim/lib/blog/mdx.tsx	5/5	Added unoptimized prop to MDX image component for inline blog images.

Sequence Diagram

sequenceDiagram
    participant Browser
    participant NextJS as Next.js Server
    participant Public as Public Folder

    Browser->>NextJS: Request blog page
    NextJS->>Public: Fetch image (unoptimized)
    Public-->>NextJS: Return original image
    NextJS-->>Browser: Serve image directly (no optimization)

Loading

[greptile-apps]

_{4 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}