Sanity Cms

Schema Architecture

17 schemas registered in studio/schemas/index.ts:

Singletons (page settings — one document each):

• siteSettings — Global site config (logo, social links, contact info, OG image)
• hero — Homepage hero section (title, subtitle, CTA, background image)
• homepageSettings — Homepage features, testimonials toggle
• aboutSettings — Doctor bio, credentials, timeline
• servicesPageSettings — Services index page config
• technologySettings — Technology page config
• dsdSettings — Digital Smile Design page config
• tourismSettings — Tourism page config (pricing, FAQ, VIP program)

Collections (multiple documents):

• service — Service documents (slug-based, used on Services page)
• testimonial — Patient testimonials
• teamMember — Clinic team members
• faq — Frequently asked questions
• tourismPricing — Tourism treatment pricing tiers
• beforeAfterCase — Gallery before/after cases with images
• youtubeVideo — YouTube video embeds with category filtering
• servicePillar — 4 SEO pillar pages (dental-implants, tmj-tmd-treatment, clear-aligners, full-arch-rehabilitation)
• page — Generic CMS pages (slug-based, Portable Text body)

[!CAUTION] gallerySettings and post do NOT exist as schemas despite being referenced in older documentation. Do not attempt to query these types.

CMS Hook Pattern

All CMS hooks live in src/hooks/useCmsData.ts. They follow this pattern:

export function useServicePillar(slug: string) {
  const [pillar, setPillar] = useState<ServicePillarData>(DEFAULTS[slug]);

  useEffect(() => {
    sanityClient.fetch(QUERY, { slug }).then((data) => {
      if (data) setPillar({ ...DEFAULTS[slug], ...data });
    });
  }, [slug]);

  return { pillar };
}

Key principle: Every CMS field uses ?? fallback to hardcoded defaults. The site never breaks if CMS is empty.

Available Hooks

GROQ Query Patterns

// Fetch a singleton (prefer known _id, fallback to any)
coalesce(*[_type == "hero" && _id == "hero"][0], *[_type == "hero"][0])

// Fetch a singleton (simple)
*[_type == "siteSettings"][0]

// Fetch a service pillar by slug
*[_type == "servicePillar" && slug.current == $slug][0]

// Fetch all blog posts
*[_type == "post" && defined(slug.current)] | order(_createdAt desc)

// Fetch slugs + types for prerendering
*[_type in ["post", "service"] && defined(slug.current)]{_type, "slug": slug.current}

[!CAUTION] order() does NOT support boolean desc. Using order(_id == "hero" desc) causes a 400 error. For "prefer this document" logic, always use coalesce() with two filtered queries.

Sanity → Netlify Webhook

A webhook named "Netlify Rebuild on Publish" is configured in the Sanity dashboard:

• Trigger: Create, Update, Delete
• URL: Netlify build hook URL
• Filter: All document types

This means: publish content in Sanity Studio → Netlify auto-rebuilds → live site updates.