Vercel

For a site Vercel builds from Git. If the blog pages are rendered on request (Next.js without static export, server components with fetch), see Server-rendered instead: you need no hook.

Set it up

1. Add the two values. Vercel → the project → Settings → Environment Variables:
   • JOOGOOS_FEED_URL = the feed address, for Production (and Preview if you want).
   • JOOGOOS_FEED_KEY = the key, marked Sensitive.
2. Read the feed during the build (same code as Netlify). In Next.js with static pages: generateStaticParams from entries, and the page reads the entry by its slug.
3. Make a deploy hook. Settings → Git → Deploy Hooks: name Joogoos, branch main, Create Hook. Copy the address, like https://api.vercel.com/v1/integrations/deploy/prj_…/….
4. Give it to the owner, who pastes it in Joogoos: Business → SEO → Where they are published → Build hook → Save.
5. Redeploy once so the build reads the new variables.

Next.js example (static)

app/blog/[slug]/page.tsx

const feed = async () => (await fetch(process.env.JOOGOOS_FEED_URL!, {
  headers: { authorization: `Bearer ${process.env.JOOGOOS_FEED_KEY}` },
  cache: 'force-cache',
})).json();

export async function generateStaticParams() {
  return (await feed()).entries.map((e: { slug: string }) => ({ slug: e.slug }));
}

Render entry.body with any Markdown renderer (headings from H2, lists, links, bold, italics, quotes).