---
title: Build, Deploy & Analyze Overview
sidebarTitle: Build & Deploy Overview
description: >-
  How docs go from git push to live site: the CLI, the build pipeline, hosting
  and custom domains, and the analytics that come with every page.
---

> **For AI agents:** the complete documentation index is at [llms.txt](/docs/llms.txt). Append `.md` to any page URL for its markdown version.

You push to GitHub (or run `jamdesk deploy`), Jamdesk builds the site, and the changes go live. That's the loop. The pages in this section cover each part of it: the CLI you'll use daily, what happens during a build, where your site is served from, and the analytics Jamdesk collects on every page without any extra scripts.

<Tip>
  **Build failing?** [Build Troubleshooting](/builds/troubleshooting) matches common error messages to causes and fixes.
</Tip>

## CLI

The open-source CLI previews docs locally, validates configuration, checks for broken links, and deploys.

<Columns cols={2}>
  <Card title="CLI Overview" icon="terminal" href="/cli/overview">
    Install the CLI and learn the core commands
  </Card>
  <Card title="Authentication" icon="key" href="/cli/authentication">
    Log in, token storage, and session management
  </Card>
  <Card title="CLI Deploy" icon="upload" href="/cli/deploy">
    How `jamdesk deploy` packages, uploads, and builds your docs
  </Card>
  <Card title="Fix Broken Links" icon="link-slash" href="/cli/fix-broken-links">
    `jamdesk fix` resolves broken internal links, previewing changes first
  </Card>
</Columns>

## Build Workflow

<Columns cols={3}>
  <Card title="Deployment Workflow" icon="arrows-spin" href="/development/deployment">
    GitHub pushes, CLI deploys, status tracking, and manual rebuilds
  </Card>
  <Card title="Triggering Builds" icon="play" href="/builds/triggering">
    Automatic on push, manual from the dashboard, plus debouncing and queues
  </Card>
  <Card title="Monitoring Builds" icon="wave-pulse" href="/builds/monitoring">
    Real-time progress, build phases, and structured logs
  </Card>
  <Card title="Fix with AI" icon="wand-magic-sparkles" href="/builds/fix-with-ai">
    Review and apply AI-suggested fixes from the build dashboard
  </Card>
  <Card title="Automatic Image Conversion" icon="file-image" href="/builds/image-optimization">
    PNG and JPG to WebP conversion at build time
  </Card>
  <Card title="PDF Export" icon="file-pdf" href="/builds/pdf-export">
    Export your whole site as a single PDF
  </Card>
</Columns>

## Hosting & Domains

Your site starts at `yourproject.jamdesk.app`. When you're ready, serve it from your own domain or from a `/docs` path on your existing site.

<Columns cols={3}>
  <Card title="Deployment Overview" icon="globe" href="/deploy/overview">
    Subdomain, custom domain, or subpath: compare the hosting options
  </Card>
  <Card title="Build & Deploy Lifecycle" icon="timeline" href="/deploy/lifecycle">
    The full pipeline from git push to live site
  </Card>
  <Card title="Custom Domains" icon="link" href="/deploy/custom-domains">
    DNS setup to serve docs from your own domain with SSL
  </Card>
  <Card title="Custom Domain Only" icon="ban" href="/deploy/custom-domain-only">
    Stop the Jamdesk subdomain from answering directly
  </Card>
  <Card title="Jamdesk Subdomains" icon="signs-post" href="/deploy/subdomains">
    Naming rules and how to change your default subdomain
  </Card>
  <Card title="Subpath Hosting" icon="folder-open" href="/deploy/subpath-hosting">
    Host at `yoursite.com/docs` instead of a separate subdomain
  </Card>
</Columns>

## Platform Guides

Tested configurations for proxying `/docs` through your existing infrastructure.

<Columns cols={2}>
  <Card title="AWS Route 53 & CloudFront" icon="aws" href="/deploy/aws">
    Distribution setup and origin configuration
  </Card>
  <Card title="Cloudflare Workers" icon="cloud" href="/deploy/cloudflare">
    Worker setup and routing for `/docs` traffic
  </Card>
  <Card title="Reverse Proxy" icon="server" href="/deploy/reverse-proxy">
    nginx, Apache, Caddy, Traefik, or HAProxy
  </Card>
  <Card title="Vercel" icon="triangle" href="/deploy/vercel">
    A `vercel.json` rewrite with the `jd_proxy` marker
  </Card>
</Columns>

## Analytics & Monitoring

<Columns cols={2}>
  <Card title="Analytics Overview" icon="gauge-high" href="/setup/analytics-overview">
    Page views, traffic sources, and search queries with no external scripts
  </Card>
  <Card title="Project Analytics" icon="chart-line" href="/setup/project-analytics">
    Visitor behavior for your site, privacy-focused
  </Card>
  <Card title="Search Analytics" icon="magnifying-glass-chart" href="/setup/search-analytics">
    What readers search for, and the content gaps it reveals
  </Card>
  <Card title="Mobile App" icon="mobile" href="/development/mobile-app">
    Build status and analytics on the go, with push notifications
  </Card>
</Columns>