Building for Scale

Scheduled for January 20, 2026 - This post demonstrates scheduled publishing.

As your content library grows, jam-gen scales with you. Here’s how we handle enterprise-level deployments.

Incremental Builds

For sites with thousands of pages, full rebuilds are impractical. Our incremental build system only regenerates changed content:

✓ 3 pages changed
✓ 2,847 pages cached
✓ Build completed in 4.2s

Content Sharding

Split your content across multiple repositories:

# jam-gen.config.yaml
content:
  sources:
    - repo: github.com/org/blog-content
      path: /blog
    - repo: github.com/org/docs-content  
      path: /docs
    - repo: github.com/org/marketing-content
      path: /landing

Edge Deployment

Deploy to the edge with our adapters:

• Cloudflare Pages
• Vercel Edge
• AWS CloudFront
• Fastly Compute

Monorepo Support

jam-gen works seamlessly in monorepos:

monorepo/
├── apps/
│   ├── marketing-site/
│   ├── docs-site/
│   └── blog/
├── packages/
│   └── shared-components/
└── content/
    └── (shared content)

Enterprise Features

• SSO Integration - Connect to your identity provider
• Audit Logging - Track all content changes
• Role-based Access - Control who can publish
• Preview Environments - Test before going live