PermitLens
Every permit. One place.
Documentation

Getting Started

Understand how the Astro marketing site and Next.js product app fit together in the PermitLens monorepo.

Getting Started

PermitLens is split on purpose:

  • permitlens.com for the public-facing marketing, pricing, and docs experience
  • app.permitlens.com for the logged-in contractor workspace

Why it is split

The site and the app solve different problems.

  • The site needs fast content iteration, clear copy, docs, and a clean first impression.
  • The app needs stateful navigation, organization access, billing, and data-heavy operational workflows.

Current implementation

This repo ships with:

  • an Astro marketing site for brand, pricing, docs, and demo flow
  • a Next.js SaaS app shell for the logged-in product
  • shared design tokens so both surfaces feel like one company
  • shared domain types and sample data for consistency across the repo
  • env-gated scaffolds for auth, billing, and data infrastructure

How to think about rollout

Do not treat the split as overhead.

Treat it as discipline.

The site should explain the product clearly. The app should do the work. Mixing those two concerns usually makes both surfaces worse.

Start You are at the beginning.

Use this page to anchor the rollout story before moving deeper into configuration detail.

Next Seat Management Model

The first commercial version is built around organization-level subscriptions and seat-aware access control.