B2C.tel · tenant operations

Content studio

tenant isolatedrelease 6686ff7Public siteSuperadminStudio

Live tenant-scoped functionality

Tenant content records

Pages, posts, and categories for the current tenant only.

Admin tenant context: Artameta · artameta.com · active

ok

Visible records

6

Live Sanity records returned for this workstream.

page

4

Records with type page.

post

2

Records with type post.

Tenant

Artameta

Resolved from current admin host and Sanity site registry.

Live records

6 returned · values are scoped and secret-safe

Artameta product selection policy

post.artameta-com.artameta-com-product-selection

post · /artameta-com-product-selection

Site: Artameta

Functional action center

Content studio + Visual Editing

This module uses authenticated dashboard workflows and diagnostic envelopes instead of placeholder copy. It can read, create, moderate, or launch the correct provider surface depending on this workstream's guardrails.

ok

Real editor entry point

Studio and Visual Editing launcher

Loading live provider state…

Credential truth

Sanity runtime diagnostics

Run the diagnostic to verify read/write configuration without exposing tokens.

Tenant context: Artameta

Live records visible on this workstream: 6

← Back to admin dashboard

Tenant content operations

Content studio + Visual Editing

Operate the tenant website content model without leaving the admin control plane.

needs configuration

Purpose

This surface is for home pages, landing pages, posts, categories, services, navigation, redirects, media references, reusable page-builder blocks, drafts, previews, and publish readiness.

Capabilities

  • Home page and page-builder operations
  • Draft/preview/publish workflow visibility
  • Visual Editing launcher and Sanity Studio handoff
  • Content QA coverage for metadata, canonicals, schema, links, and blocks
  • Reusable sections and migration-generated editable blocks

Operational workflows

  • Review content inventory and missing Sanity configuration state.
  • Open Visual Editing or Studio for structured editing when credentials are configured.
  • Validate page-builder coverage before launch or migration cutover.
  • Track content QA issues as launch checklist items.

Guardrails

  • Sanity remains the content source of truth.
  • Missing credentials must be shown honestly instead of fake empty records.
  • Draft content must not publish without explicit editorial workflow.

API/schema contracts

These are technical contract references, not dashboard navigation. Protected APIs require authentication and may return JSON envelopes such as unauthenticated when opened directly.

/api/site-content/api/draft-mode/enable/api/draft-mode/disablepage/post/category/service schemas

Use the dashboard workstream pages for human workflows. Use these contracts only from authenticated clients, tests, cron jobs, or approved agent integrations.

Next implementation actions

  • Configure Sanity project ID/dataset in Vercel.
  • Add real content records or migration jobs.
  • Wire direct Studio/Presentation launch URLs once Sanity project metadata is available.