ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Sanity exposes content through GROQ over an edge-cached CDN endpoint and a direct API. This architecture note covers the smallest viable read path, token trust boundaries, webhook revalidation, and failure modes for a web app using Content Lake.
Stop over-fetching CMS data. Learn how to use GROQ projections and dereferencing in Sanity to send only the necessary fields to your frontend, reducing latency and payload size.
Learn how to render Sanity Portable Text safely by aligning schema, GROQ projection, and a custom serializer to preserve links, annotations, and block semantics.
Portable Text stores rich content as JSON blocks. Render it in React using block-content-to-react and custom serializers instead of raw HTML.
Blog listings that fetch whole Sanity documents waste bandwidth and couple UI to unused fields. Use precise GROQ projections and parameterized named queries so pages fetch only what they render.
Learn why a GROQ query may return [] or null even when matching documents exist, and follow ordered checks to isolate syntax, schema, locale, or permission issues.
Guide to using Sanity Content Lake’s CDN‑backed GROQ endpoint with read‑only tokens for public SSR, covering query structure, image URL parameters, trust boundaries, checks, and failure modes.
A structured diagnostic guide for identifying and resolving slow GROQ queries, timeouts, and payload bloat in Sanity Content Lake using ordered checks and targeted fixes.
Decide between Sanity document references and Portable Text embeds for content relationships: a comparison table, trade-offs, schema code, and GROQ validation.
sanity
react