# Run your first documentation review

import { Card, CardGrid, LinkCard, Aside } from '@astrojs/starlight/components';

<Aside type="tip" title="New to EkLine?">
  Learn [how EkLine works](/reviewer/overview/) before diving into setup.
</Aside>

Each setup takes about 3 minutes. Most users catch 2-3 issues they didn't know existed on their first run.

### See EkLine in action

This short walkthrough shows the experience of using EkLine in your VS Code, Docs, and CI/CD pipelines.

<div style={{padding:'56.25% 0 0 0', position:'relative'}}>
  <iframe
    src="https://player.vimeo.com/video/1052736895?badge=0&autopause=0&player_id=0&app_id=58479"
    frameBorder="0"
    allow="autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share"
    referrerPolicy="strict-origin-when-cross-origin"
    style={{position:'absolute', top:0, left:0, width:'100%', height:'100%'}}
    title="EkLine Onboarding"
  />
</div>
<script src="https://player.vimeo.com/api/player.js"></script>

## Pick your setup

<CardGrid>
  <Card title="GitHub Action" icon="github">
    Checks run automatically on every PR.

    Best for teams using GitHub for docs.

    [Set up GitHub Action →](/reviewer/quickstart/github-action/)
  </Card>
  <Card title="GitLab CI" icon="setting">
    Review docs on every merge request.

    Best for teams using GitLab for docs.

    [Set up GitLab CI →](/reviewer/integrations/gitlab-integration/)
  </Card>
  <Card title="Bitbucket Pipelines" icon="setting">
    Review docs on every pull request.

    Best for teams using Bitbucket for docs.

    [Set up Bitbucket Pipelines →](/reviewer/integrations/bitbucket-integration/)
  </Card>
  <Card title="VS Code" icon="vscode">
    Real-time feedback as you write.

    Best for writers and individual contributors.

    [Set up VS Code →](/reviewer/quickstart/vscode/)
  </Card>
  <Card title="Google Docs" icon="document">
    For docs outside your repo.

    Best for specs, proposals, and wiki pages.

    [Set up Google Docs →](/reviewer/quickstart/google-docs/)
  </Card>
  <Card title="CLI" icon="seti:shell">
    Run checks from the command line.

    Best for local development and custom CI/CD pipelines.

    [Set up CLI →](/reviewer/quickstart/cli/)
  </Card>
</CardGrid>

---

## Not sure which to pick?

| Where do your docs live? | Use this |
|--------------------------|----------|
| GitHub repo | [GitHub Action](/reviewer/quickstart/github-action/) |
| GitLab repo | [GitLab CI](/reviewer/integrations/gitlab-integration/) |
| Bitbucket repo | [Bitbucket Pipelines](/reviewer/integrations/bitbucket-integration/) |
| Writing locally in VS Code | [VS Code](/reviewer/quickstart/vscode/) |
| Google Docs, Notion, or other tools | [Google Docs](/reviewer/quickstart/google-docs/) |
| Local development or custom CI/CD | [CLI](/reviewer/quickstart/cli/) |

<Aside type="tip">
Most teams use **GitHub Action** for CI/CD enforcement and **VS Code** for real-time feedback while writing. They work great together.
</Aside>

---

## After your first check

Once you've run your first review, explore these features:

<CardGrid>
  <Card title="Docs Agent" icon="rocket">
    Generate API docs and guides from your code using AI.

    [Learn more →](/agent/)
  </Card>
  <Card title="Rules" icon="setting">
    Configure style guides and terminology for your team.

    [Learn more →](https://ekline.io/guidelines/rules)
  </Card>
</CardGrid>

---

## Stuck?

Reply to your welcome email or contact support@ekline.io. We read every message.