From db08170fb258fa61d37a99c515c58e4abb350a8d Mon Sep 17 00:00:00 2001
From: Prashant Sridharan <914007+CoolAssPuppy@users.noreply.github.com>
Date: Thu, 28 May 2026 06:52:54 +0100
Subject: [PATCH] Fixed the og image (#46443)

## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.

YES

## What kind of change does this PR introduce?

Fixed the imgThumb link in the post so that it is image only, ensuring
it won't be cropped in the blog main page.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Updated blog thumbnail/OG image configuration for improved preview
display when sharing.
* Revised survey content: the "Primary Database" chapter and its stat
label now reference Postgres instead of Supabase.

<!-- review_stack_entry_start -->

[![Review Change
Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/46443?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack)

<!-- review_stack_entry_end -->
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---
 ...g-your-supabase-projects-from-npm-supply-chain-attacks.mdx | 2 +-
 apps/www/data/surveys/state-of-startups-2026.tsx              | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/apps/www/_blog/2026-05-26-protecting-your-supabase-projects-from-npm-supply-chain-attacks.mdx b/apps/www/_blog/2026-05-26-protecting-your-supabase-projects-from-npm-supply-chain-attacks.mdx
index bf0577221e4..59922bbd219 100644
--- a/apps/www/_blog/2026-05-26-protecting-your-supabase-projects-from-npm-supply-chain-attacks.mdx
+++ b/apps/www/_blog/2026-05-26-protecting-your-supabase-projects-from-npm-supply-chain-attacks.mdx
@@ -4,7 +4,7 @@ description: 'How Supabase is responding to npm supply chain attacks and practic
 author: katerina_skroumpelou
 date: '2026-05-26'
 imgSocial: 'https://zhfonblqamxferhoguzj.supabase.co/functions/v1/generate-og?template=platform&layout=icon-text&copy=Protecting+projects+from%0A%5Bnpm+supply+chain+attacks%5D&icon=supabase.svg'
-imgThumb: 'https://zhfonblqamxferhoguzj.supabase.co/functions/v1/generate-og?template=platform&layout=icon-text&copy=Protecting+projects+from%0A%5Bnpm+supply+chain+attacks%5D&icon=supabase.svg'
+imgThumb: 'https://zhfonblqamxferhoguzj.supabase.co/functions/v1/generate-og?template=ruler&layout=icon-only&copy=Protecting+projects+from%0A%5Bnpm+supply+chain+attacks%5D&icon=supabase.svg'
 categories:
   - security
 tags:
diff --git a/apps/www/data/surveys/state-of-startups-2026.tsx b/apps/www/data/surveys/state-of-startups-2026.tsx
index 283d42ed694..a0fc405216b 100644
--- a/apps/www/data/surveys/state-of-startups-2026.tsx
+++ b/apps/www/data/surveys/state-of-startups-2026.tsx
@@ -366,11 +366,11 @@ const stateOfStartupsData = {
         {
           title: 'Primary Database',
           description:
-            'Supabase went from 76% to 82%. Every legacy NoSQL option lost share: MongoDB dropped 5%, MySQL 3%, Firebase 2%. Neon, DynamoDB, and Convex appeared as options for the first time and took small but measurable shares.',
+            'Postgres went from 76% to 82%. Every legacy NoSQL option lost share: MongoDB dropped 5%, MySQL 3%, Firebase 2%. Neon, DynamoDB, and Convex appeared as options for the first time and took small but measurable shares.',
           stats: [
             {
               percent: 82,
-              label: 'Startups using Supabase as a database',
+              label: 'Startups using Postgres as a database',
               source: { column: 'databases', aggregation: 'multi', target: 'Supabase' },
             },
             { percent: 60, label: 'Startups with Node.js in their backend stack' },