{
  "id": "03",
  "content": [
    {
      "type": "heading",
      "text": "Staging, Content Freeze and QA Windows"
    },
    {
      "type": "text",
      "html": "A staging environment gives the team a place to test without affecting visitors. It should be close enough to production that results are meaningful."
    },
    {
      "type": "text",
      "html": "A content freeze prevents last-minute edits from destabilizing the launch. It does not mean nothing can change; it means changes must be intentional and reviewed."
    },
    {
      "type": "text",
      "html": "QA windows give people time to check content, links, forms, responsiveness, accessibility basics, tracking, redirects, and browser behavior."
    },
    {
      "type": "callout",
      "style": "info",
      "html": "<strong>Practice:</strong> Define a freeze time and a QA checklist. Any late change should have an owner, reason, and retest note."
    }
  ],
  "quiz": {
    "questions": [
      {
        "id": "q1",
        "type": "single",
        "text": "What is staging for?",
        "options": [
          {
            "id": "a",
            "text": "Testing before visitors see changes"
          },
          {
            "id": "b",
            "text": "Replacing production forever"
          },
          {
            "id": "c",
            "text": "Hiding all content"
          }
        ],
        "correct": [
          "a"
        ]
      },
      {
        "id": "q2",
        "type": "single",
        "text": "What does a content freeze create?",
        "options": [
          {
            "id": "a",
            "text": "Control over last-minute changes"
          },
          {
            "id": "b",
            "text": "A ban on fixing critical issues"
          },
          {
            "id": "c",
            "text": "Automatic SEO"
          }
        ],
        "correct": [
          "a"
        ]
      }
    ]
  }
}