Netlify

For a site Netlify builds from a Git repository (Astro, Next.js static export, Eleventy, Hugo with a fetch step, Gatsby…).

Set it up

Add the two values. Netlify → the site → Site configuration → Environment variables → Add a variable:
- JOOGOOS_FEED_URL = the feed address from the owner’s message.
- JOOGOOS_FEED_KEY = the key, with Contains secret values ticked. Scope: Builds.
Read the feed during the build, and render the pages (see the code below). Build once with ?sample=1 added to the address to see the sample article, then remove it.
Make a build hook. Site configuration → Build & deploy → Continuous deployment → Build hooks → Add build hook. Name it Joogoos, branch main (or your production branch). Copy the address, like https://api.netlify.com/build_hooks/64f….
Give it to the owner. They paste it in Joogoos: Business → SEO → Where they are published → Build hook → Save.
Deploy once so the build reads the new variables. The card in Joogoos turns green.

Read the feed at build time

// e.g. src/lib/joogoos.js — Node 18+, any framework
export async function joogoosFeed() {
  const res = await fetch(process.env.JOOGOOS_FEED_URL, {
    headers: { authorization: `Bearer ${process.env.JOOGOOS_FEED_KEY}` },
  });
  if (!res.ok) throw new Error(`Joogoos feed answered ${res.status}`);
  return res.json(); // { site, entries, redirects, gone }
}

Render one page per entry at entry.path, a list at the blog path, and add them to the sitemap. Netlify’s _redirects can carry feed.redirects (/from /to 301) and feed.gone (/path /410.html 410) if you write that file during the build.

When it is working

Publish an article in Joogoos: Netlify starts a deploy about 30 seconds later (Joogoos groups several publishes into one ring). Netlify answers the hook with 200, which Joogoos records.