> ## Documentation Index
> Fetch the complete documentation index at: https://learn.mintlify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Preview deployments

> Use a rendered preview to review changes that a Git diff cannot show.

export const Quiz = ({question, answers, correctFeedback, incorrectFeedback}) => {
  const [selected, setSelected] = React.useState(null);
  const [checked, setChecked] = React.useState(false);
  const quizId = React.useId();
  const isCorrect = checked && answers[selected]?.correct;
  const reset = () => {
    setSelected(null);
    setChecked(false);
  };
  return <div className={"quiz-container" + (checked ? " quiz-checked" : "")}>
      <Badge color="green">Quiz</Badge>
      <p className="quiz-question" id={quizId + "-question"}>{question}</p>
      <div className="quiz-options" role="radiogroup" aria-labelledby={quizId + "-question"} aria-disabled={checked}>
        {answers.map((answer, i) => <label key={i} className={["quiz-option", !checked && selected === i ? "quiz-option-selected" : "", checked && answer.correct ? "quiz-option-correct" : "", checked && selected === i && !answer.correct ? "quiz-option-incorrect" : ""].filter(Boolean).join(" ")}>
            <input type="radio" name={"quiz-" + quizId} checked={selected === i} onChange={() => !checked && setSelected(i)} disabled={checked} />
            <span className="quiz-radio" />
            <span className="quiz-option-label">{answer.text}</span>
          </label>)}
      </div>
      {checked && <div className={"quiz-feedback " + (isCorrect ? "quiz-feedback-correct" : "quiz-feedback-incorrect")} role="status" aria-live="polite" aria-atomic="true">
          <span className="quiz-feedback-icon">{isCorrect ? "✓" : "✗"}</span>
          {isCorrect ? correctFeedback : incorrectFeedback}
        </div>}
      <div className="quiz-actions">
        {!checked ? <button className="quiz-btn quiz-btn-check" type="button" onClick={() => selected !== null && setChecked(true)} disabled={selected === null}>
            Check answer
          </button> : <button className="quiz-btn quiz-btn-reset" type="button" onClick={reset}>
            Try again
          </button>}
      </div>
    </div>;
};

<iframe className="w-full aspect-video rounded-xl" src="https://www.youtube.com/embed/GYzXpmN_--8" title="Preview deployments" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowFullScreen />

A Git diff shows which lines changed. A preview shows what those changes do to the documentation site.

When the Mintlify GitHub app has access to your repository, pull requests receive a preview deployment of the proposed branch. New commits update the preview, so reviewers can follow the same link throughout the pull request.

## Find the preview

Open the pull request and look for the Mintlify preview in its conversation or checks. The deployment may still be building when the pull request first opens, so check its status if the link isn't ready yet.

If no preview appears:

1. Confirm that the pull request targets the configured deployment branch.
2. Check that the Mintlify GitHub app can access the repository.
3. Look at the deployment status in the Mintlify dashboard.

## Review what readers will experience

Start with every page changed by the pull request. For each one, check:

* The page renders without broken MDX or missing media
* The edited section makes sense with the paragraphs around it
* Links and interactive components behave as expected
* Headings and the table of contents describe the page clearly

Then check the effects beyond those pages. A small `docs.json` edit can move several pages, change a label, or remove something from navigation. Follow the relevant path through the sidebar instead of checking only the URL you were given.

For layout-heavy changes, resize the browser or check a mobile viewport. You don't need to test every screen size on every copy edit; focus the review on what the change could plausibly affect.

## Give reviewers a specific task

Share the preview with a short review request. For example:

> Please check the new authentication flow from **Create a token** through **Test the request**. In particular, does the choice between service and user tokens make sense before step one?

That is more useful than “Thoughts?” Reviewers know where to start and what kind of feedback you need.

Preview URLs are publicly accessible by default. Organizations can enable preview authentication, so confirm the access setting before sending a link outside your team. A reviewer who can open an authenticated preview may need a Mintlify organization account even if they don't use GitHub.

## Treat the preview and diff as a pair

The preview can reveal bad layout or navigation, but it won't show an unrelated file added to the commit or a secret removed before rendering. Review the Git diff for source changes and the preview for the reader experience.

<Quiz
  question="A pull request changes one page and reorganizes its navigation group. What should you inspect in the preview?"
  answers={[
{ text: "The changed page and the affected path through the navigation", correct: true },
{ text: "Only the paragraph highlighted in the Git diff", correct: false },
{ text: "Only the site's home page", correct: false },
{ text: "Nothing if the automated checks pass", correct: false },
]}
  correctFeedback="Right. Review the edited page in context and follow the navigation affected by the structural change."
  incorrectFeedback="The preview is most useful for checking rendered and structural effects. Inspect the changed page and the navigation path the pull request modifies."
/>

Next up: [Collaborating with your team](/courses/git-github/collaborating-with-your-team) — make reviews useful and handle overlapping work without losing changes.