Visible records
0
Live Sanity records returned for this workstream.
Live tenant-scoped functionality
Tenant services
Service documents and local-business content scoped to this tenant.
Admin tenant context: RUG · rug.news · active
Tenant
RUG
Resolved from current admin host and Sanity site registry.
Open canonical Studio ↗Edit the tenant records in Sanity Studio.Configured Studio host ↗External Studio host. Check the functional action center status before relying on it for editor work.Open public site ↗View the public tenant website.Open superadmin registry ↗Review cross-network tenant configuration on the canonical command center.
Live records
0 returned · values are scoped and secret-safe
No live records returned for this workstream. This is a true empty state only when the status is empty; otherwise follow the diagnostics above.
Functional action center
Services and local business layer
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.
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: RUG
Live records visible on this workstream: 0
Tenant service operations
Services and local business layer
Operate service pages, pricing/CTA strategy, service areas, and local business metadata.
Purpose
This surface manages service content, related posts/products/services, local schema fields, booking/contact calls-to-action, and service-area content quality.
Capabilities
- Service page inventory
- Service area and local-business schema readiness
- Pricing/contact CTA governance
- Related content/product linking
- Service SEO and metadata checks
Operational workflows
- Review service documents from the public content contract.
- Add/adjust service page-builder blocks in Sanity.
- Validate local business metadata and schema.
- Connect services to related product/post clusters.
Guardrails
- Service claims must be accurate and editable.
- Schema cannot invent unsupported services, pricing, or locations.
- SEO recommendations must separate measured and inferred signals.
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?type=serviceservice schemaUse 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 credentials.
- Add service-specific editor UI after auth flows are completed.
- Add booking/contact CTA analytics once GA4 is connected.