Connor Yoh
2faa38c011
Drops the side-by-side card promo (EditorPlanPromo) in favour of two views
that mirror the subscribed PaygLeader/PaygMember dashboards visually. The
free view now feels like an extension of the paid view rather than a
different page, which makes turning on Processor feel like enabling a
switch rather than buying a product.
New billable framing (product call set 2026-06):
Free, always — anything clicked directly in the Stirling UI:
viewing, editing, merging, splitting, signing, watermarking,
compression, conversion, OCR via the interactive UI.
Counts toward 500/month free tier — and metered above that:
automation pipelines, AI tools, API calls.
Note: backend design doc + pricing schema don't reflect this yet — FE is
the source of truth in the meantime; backend will catch up.
Components:
PaygFreeLeader
- Mirrors PaygLeader: subtitle + role pill header, hero usage card
showing 62 / 500 free operations with progress bar + "Plenty left"
status, identical visual language to the subscribed view
- Below the hero: a gradient-bordered CTA card ("Turn on the Processor
plan") with three benefit bullets (Automation / AI / API access)
and footer row containing the CTA button + reassurance copy
- Bottom: side-by-side explainer cards — "Always free" vs "Counts
toward 500/month" — using the same colour tokens as the hero
- CTA opens the existing UpgradeModal
PaygFreeMember
- Same header + hero pattern but with team-member pill
- Replaces the CTA with a lock-icon note explaining the owner can
enable Processor
- Same bottom explainer cards but worded for the member viewpoint
("Always free for you" / "Shared with the team")
UpgradeModal copy rewrite:
- Promise card now reads "Everything in the Stirling UI stays free.
You only pay for what comes from automation pipelines, AI tools, and
API calls — the things that don't need a person clicking through
the UI."
- "Set your monthly spend ceiling" section text updated to
"Your first 500 automation / AI / API operations every month are free"
- "What we count toward billing" card now a bulleted list of the three
billable categories plus an italic line explicitly listing UI tools
that stay free
Dev preview slots reworked:
- Was: free / upgrade-modal / active-leader / active-member
- Now: free-leader / free-member / subscribed-leader / subscribed-member
- "Upgrade modal" slot removed — the modal now opens from inside
free-leader, which is the only real entry point
Deleted: EditorPlanPromo.tsx + .css (superseded by PaygFreeLeader).
Screenshots:
payg-flow-009-free-leader-v1.png (first cut — stacked header)
payg-flow-010-free-leader-v2.png (Mantine Group header, polished CTA)
payg-flow-011-free-member.png (member view, lock note instead of CTA)
payg-flow-012-modal-new-copy.png (modal with billable framing reworked)
Frontend
All frontend commands are run from the repository root using Task:
task frontend:dev— start Vite dev server (localhost:5173)task frontend:build— production buildtask frontend:test— run teststask frontend:test:watch— run tests in watch modetask frontend:lint— run ESLint + cycle detectiontask frontend:typecheck— run TypeScript type checkingtask frontend:check— run typecheck + lint + testtask frontend:install— install npm dependencies
For desktop app development, see the Tauri section below.
Layout
frontend/ is a workspace containing one or more apps. Today it holds the
PDF editor under frontend/editor/; new apps (the developer portal, etc.)
will sit alongside it as siblings. Shared tooling — package.json, node_modules,
.storybook/, ESLint, Prettier — lives at frontend/ so every app installs
once and lints with the same config.
Environment Variables
The editor's environment variables live in committed .env files at
frontend/editor/:
.env— used by all builds (core, proprietary, and as the base for desktop/SaaS).env.desktop— additional vars loaded in desktop (Tauri) mode.env.saas— additional vars loaded in SaaS mode
These files contain non-secret defaults and are checked into Git, so most dev work needs no further setup.
To override values locally (API keys, machine-specific settings), create an uncommitted sibling editor/.env.local / editor/.env.desktop.local / editor/.env.saas.local. Vite automatically layers these on top of the committed files.
Docker Setup
For Docker deployments and configuration, see the Docker README.
Tauri
All desktop tasks are available via Task. From the root of the repo:
Dev
task desktop:dev
This ensures the JLink runtime and backend JAR exist (skipping if already built), then starts Tauri in dev mode.
Build
task desktop:build
This does a full clean rebuild of the backend JAR and JLink runtime, then builds the Tauri app for production.
Platform-specific dev builds are also available:
task desktop:build:dev # No bundling
task desktop:build:dev:mac # macOS .app bundle
task desktop:build:dev:windows # Windows NSIS installer
task desktop:build:dev:linux # Linux AppImage
JLink Tasks
You can also run JLink steps individually:
task desktop:jlink # Build JAR + create JLink runtime
task desktop:jlink:jar # Build backend JAR only
task desktop:jlink:runtime # Create JLink custom JRE only
task desktop:jlink:clean # Remove JLink artifacts
Clean
task desktop:clean
Removes all desktop build artifacts including JLink runtime, bundled JARs, Cargo build, and dist/build directories.