DigiRivet
← Back to catalogue
Sanity / Commercial platforms

Dynamic content management for static sites.

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.

Sanity

Example use case

Publish a post in StudioWebhook triggers a buildAstro fetches content and deploys
Selected recordExample use case
01Publish a post in Studio
02Webhook triggers a build
03Astro fetches content and deploys
Illustrative interface · Example content

Does this sound like your team?

  • 01Updating your static blog requires code changes and developer involvement.
  • 02You need custom content models, SEO fields and publishing workflows.
  • 03Your Astro site needs a CMS connection, draft previews and automated builds.

What can you do?

Structured content models

Define post, author, category, image and SEO schemas that match your website components.

Astro and API integration

Query content with GROQ. Fetch at build time for static pages or at request time for server-rendered pages.

Webhook-triggered publishing

Trigger your hosting platform’s build hook when content is published. Static pages reflect changes after the build and deployment finish.

Draft previews

With suitable server and preview configuration, review drafts on your website before publishing.

DigiRivet

How can DigiRivet help?

The work below is separate from the platform’s standard features. Scope is agreed during discovery and the proposal.

Content schemas and Studio setup

We model posts, authors, categories and SEO fields and configure the workspace for your team.

Astro integration and previews

We develop GROQ queries, content components and image handling, and configure previews for your hosting setup.

Webhooks and publishing automation

We connect publishing events to build hooks and configure webhook verification, access permissions and deployment checks.

Example use case

Sanity

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.

  1. 01Publish a post in Studio
  2. 02Webhook triggers a build
  3. 03Astro fetches content and deploys

Illustrative workflow · Not an actual product screen or client project.

How we work together

  1. 01

    Define the need

    Discuss goals, users and your current setup.

  2. 02

    Prepare the platform

    Agree scope, then configure and tailor the installation.

  3. 03

    Start using it

    Complete checks and training, then agree ongoing support.

Edition and service scope

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.

Common questions

Does new content appear immediately on a static site?

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.

Is the subscription included?

Platform subscriptions and provider fees are assessed separately from DigiRivet configuration and integration services.

Are all features in every plan?

Features, integrations and usage limits depend on the selected provider package. Scope is checked before a proposal.

Are you an official partner?

This page does not claim an official partnership or reseller status. Service scope is defined for each project.

Find the right setup for your needs.

Tell us about your team, current tools and the work you want to improve. We can assess the platform and scope together.

← Back to catalogue