links.arjun.tv/docs/end-user/use-cases/uc-12-site-publishing-deployment-lifecycle

UC-12: Site Publishing and Deployment Lifecycle

Role-gated control-plane steps are intentionally excluded from this public guide; use support escalation when those operations are required. Shared company context: Gharart.com Company Context Need operator help? Escalate through Troubleshooting and Support with request IDs and repro artifacts.

Developer Outcome

Ship site publishing and deployment lifecycle for Gharart.com with reproducible API steps, operational limits, and clear debugging playbooks.

Prerequisites

  • A valid handle and environment access for Gharart.com.
  • JWT and/or PAT credentials with required scope for this use case.
  • Access to logs, support escalation endpoints, and test workspace.

Gharart Scenario

Landing page redeploy with safe preview validation.

Persona: Web experience manager

Business goal: Publish updated storefront pages with preview gates and rollback-ready deployment history.

Step-by-Step Flow (UI + API)

  1. Open the relevant Gharart workflow in the dashboard and confirm actor role access.
  2. Execute route calls in sequence for this use case and capture response IDs.
  3. Validate expected state in UI and API after each step before moving forward.
  4. Record artifacts (request ID, run ID, deployment ID, slug, or token) for support handoff.

Primary API Routes

MethodPath
GET/profiles/{handle}/{proxy+}
GET/profiles/{handle}/index.html
GET/v2/handles/{handle}/site-deployments
GET/v2/handles/{handle}/site-deployments/{deploymentId}/preview
GET/v2/handles/{handle}/site-intel/{hostname}/snapshot
POST/v2/handles/{handle}/function-bindings
POST/v2/handles/{handle}/site-deployments
POST/v2/handles/{handle}/site-intel/{hostname}/crawl-runs
POST/v2/handles/{handle}/site-intel/{hostname}/replay-runs
PUT/v2/handles/{handle}/site-mode

Limits and Quotas

  • Respect per-route throttles and daily write limits before bulk operations.
  • Use idempotency-safe retries for write endpoints to avoid duplicate business actions.
  • Schedule high-volume workflows outside peak campaign windows where possible.

Where This Breaks

  • preview not rendering because deployment artifact missing
  • site-mode mismatch causing stale profile route
  • function binding not deployed with latest release

How Gharart Debugs It

  1. List site deployments and verify target deployment id
  2. Open preview endpoint before publish promotion
  3. Confirm profile route resolves expected deployment version

Escalation

Use end-user escalation path:

  • Submit POST /v2/support/report.
  • Include summary, details, and when available handle, sessionId, requestId, reproArtifact.

Audience boundaries:

  • POST /v2/operator/escalations is an internal operator workflow and not an end-user escalation action.
  • POST /v2/public/content-report is for public abuse moderation reports, not product incident escalation.