Structured content models
Define post, author, category, image and SEO schemas that match your website components.
Manage blog posts, news and page content for your Astro site in Sanity Studio. Content Lake API integration and webhook-triggered builds separate content publishing from code changes.
Example use case
Define post, author, category, image and SEO schemas that match your website components.
Query content with GROQ. Fetch at build time for static pages or at request time for server-rendered pages.
Trigger your hosting platform’s build hook when content is published. Static pages reflect changes after the build and deployment finish.
With suitable server and preview configuration, review drafts on your website before publishing.
DigiRivet
The work below is separate from the platform’s standard features. Scope is agreed during discovery and the proposal.
We model posts, authors, categories and SEO fields and configure the workspace for your team.
We develop GROQ queries, content components and image handling, and configure previews for your hosting setup.
We connect publishing events to build hooks and configure webhook verification, access permissions and deployment checks.
Example use case
An editor prepares a post and SEO fields in Sanity Studio. Publishing triggers a site build through a webhook. Astro retrieves current content via the API; the post appears once the build and deployment finish.
Illustrative workflow · Not an actual product screen or client project.
Discuss goals, users and your current setup.
Agree scope, then configure and tailor the installation.
Complete checks and training, then agree ongoing support.
Sanity Studio being open source does not mean the entire platform is free or self-hostable. Content Lake offers free and paid plans. Features, usage limits and provider fees depend on the selected plan; DigiRivet configuration and integration services are scoped separately.
Static pages require a new build and deployment. A Sanity webhook can trigger this automatically; changes appear once the process completes. Server-rendered pages can fetch content per request, with freshness also depending on caching policy.
Platform subscriptions and provider fees are assessed separately from DigiRivet configuration and integration services.
Features, integrations and usage limits depend on the selected provider package. Scope is checked before a proposal.
This page does not claim an official partnership or reseller status. Service scope is defined for each project.
Tell us about your team, current tools and the work you want to improve. We can assess the platform and scope together.