Content Lifecycle

// startPublish and stopPublish are built-in fields on every content type.
// Editors set them in the CMS - no custom property definition needed.

// startPublish - the item goes live on this date (status → Published)
// stopPublish  - the item expires on this date  (status → Expired → removed from Graph)

// In the Graph schema - these are on _IContent._metadata:
query GetPageWithSchedule {
  LandingPage(limit: 5) {
    items {
      _metadata {
        published    # date the current version was last published
        changed      # date the content was last saved (any state)
        url { default }
      }
    }
  }
}

// Note: Graph does not expose startPublish or stopPublish in queries -
// they are CMS-side scheduling fields, not indexed delivery fields.
// The effect is that items simply appear or disappear from Graph results.

// Graph only returns Published items. Other states are invisible.
//
// This means:
//   - A Scheduled item won't appear in queries until its startPublish date
//   - Calling notFound() is correct for Approved-but-not-yet-published items
//     (they don't exist in Graph yet - the URL returning 404 is expected)
//   - An Expired item disappears from results after stopPublish without any app code
//
// You do NOT need to filter by status in your queries - Graph handles it.
// Published = visible. Everything else = invisible.

// ✅ This is all you need - no status filter required:
query GetPage($url: String!) {
  _Content(where: { _metadata: { url: { default: { eq: $url } } } }) {
    items { ... }
  }
}

// ❌ This would be wrong - "status" is not a Graph filter field:
_Content(where: { _metadata: { status: { eq: "Published" } } })   // doesn't exist

// Webhook events tied to the content lifecycle
// Register these endpoints in CMS Settings → Events

// CMS publish webhook (POST /api/publish):
// Fires when any content item is published - status → Published.
// Use this to invalidate ISR caches immediately on publish.
revalidatePath("/", "layout");
revalidateTag("navigation");
revalidateTag("banner");

// Graph webhook (POST /api/webhooks):
// Fires when Graph finishes indexing a change (slightly after the CMS publish).
// Use this for fine-grained revalidation when you know which path changed.
// Payload types:
//   "bulk.completed"  - Graph sync finished (all changes indexed)
//   "doc.updated"     - a single item was updated in Graph's index
//   "doc.expired"     - an item reached its stopPublish date and was removed

// Responding to doc.expired:
if (body.type === "doc.expired") {
  const url = body.data?.url;
  if (url) revalidatePath(url);     // bust the ISR cache for the expired URL
  revalidatePath("/", "layout");    // in case it appeared in listing pages
}

// Approval workflow automation - webhook on status change
//
// Register a webhook in CMS Settings → Events → "Content Status Changed".
// Useful for: Slack notifications, CI step triggers, downstream sync.

// POST /api/content-status-changed
// Body: { contentKey, url, status, locale, updatedBy }

export async function POST(request: NextRequest) {
  const { contentKey, url, status, updatedBy } = await request.json();

  if (status === "InReview") {
    // Notify reviewers in Slack
    await notifySlack({
      text: `📝 ${updatedBy} submitted ${url} for review`,
      channel: "#content-review",
    });
  }

  if (status === "Published") {
    // Trigger a downstream sync (e.g. push to a CDN edge config)
    await triggerEdgeSync({ contentKey, url });
  }

  return NextResponse.json({ received: true });
}