mirror of https://github.com/Stirling-Tools/Stirling-PDF.git synced 2026-09-03 05:10:16 +03:00

Files

T

ConnorYoh d3638d786d Portal home: cut the mock blocks, wire the rest to real data (#6931 )

## What this changes

Cleaning up the portal home page. Most of what was under the plan card
was mock — it hit endpoints that don't exist on any backend, so on SaaS
it just showed a wall of "—" and "Nothing here yet". I removed the fake
stuff and wired the bits worth keeping to real data.

**Scrapped (all mock, no backend anywhere — self-hosted included):**
- The "No usage yet" usage chart
- The KPI strip (Docs/30d, Pipelines, Agents active, Eval pass rate)
- The "Build a pipeline in seconds" fork wizard (fake build animation,
deploy was a TODO)
- The Sources/Pipelines/Agents product cards
- The "Popular use cases" marketing cards
- Enterprise region health
- The "Try a PDF operation" runner

Deleted their component/api/mock/MSW/story files too, plus the now-dead
i18n keys and CSS.

**Wired to real data (finished, not removed):**
- The plan strip and the sidebar footer now show the **real** 30-day
processed-PDF count from `/api/v1/usage/fleet-stats` (was a mock KPI).
Shows "—" honestly when the backend can't compute it, never a fake
number.
- **Recent activity** now reads the **real audit log** — the same
endpoint the Infrastructure → Audit tab uses.

**Result:** one simple layout for all tiers — plan strip → recent
activity + quick actions → "What runs on your PDFs" (the real policy
summary). Every block is backed by data that actually exists.

Net: **−3,221 / +89 lines**, 17 files removed.

## Testing
typecheck (all variants), full test suite (1211), saas + proprietary
builds, lint, format, storybook build, toml-sort — all green. The
`unusedTranslations` test guarantees no orphaned i18n keys were left
behind.

2026-07-09 11:58:32 +00:00

.claude/agents

playwright (#6025 )

2026-04-27 11:35:50 +01:00

.storybook

Add portal user management and access control (#6913 )

2026-07-09 10:29:26 +00:00

editor

Portal home: cut the mock blocks, wire the rest to real data (#6931 )

2026-07-09 11:58:32 +00:00

scripts

Consolidate buttons and related components (#6787 )

2026-07-07 16:06:56 +00:00

shared/components

Consolidate buttons and related components (#6787 )

2026-07-07 16:06:56 +00:00

.gitignore

Portal procurement: real pricing/trial/quote spine + linked-gated checkout (vertical slice) (#6861 )

2026-07-07 12:02:02 +00:00

.prettierignore

Restructure Portal code to be inside Editor (#6857 )

2026-07-03 13:20:02 +00:00

.prettierrc

Prettier 2: Electric Boogaloo (#6113 )

2026-04-17 09:50:16 +00:00

eslint.config.mjs

Add portal user management and access control (#6913 )

2026-07-09 10:29:26 +00:00

package-lock.json

Add bidirectional API types to frontend (#6867 )

2026-07-07 07:47:07 +00:00

package.json

Convert to consistently use JS modules (#6854 )

2026-07-07 11:11:24 +00:00

README.md

Restructure/frontend editor (#6404 )

2026-05-22 13:40:34 +01:00

README.md

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 build
task frontend:test — run tests
task frontend:test:watch — run tests in watch mode
task frontend:lint — run ESLint + cycle detection
task frontend:typecheck — run TypeScript type checking
task frontend:check — run typecheck + lint + test
task 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.