SolidJS Parity Plan

Status as of March 28, 2026.

Goal

Bring the SolidJS frontend up to parity with the active Buttrbase admin/product surface, not every legacy React route accumulated over time.

Included in the Parity Target

• authenticated admin shell
• global product catalog, prices, and provider keys
• login and session-aware navigation
• help center
• wallet and billing
• teams and org lifecycle
• app and org analytics
• entitlement checks
• pricing checks
• analytics decision panels (pricing funnel, auth adoption, entitlement deny rate, governance/session signals)
• org security settings
• org SSO connection management
• org audit event listing and export

Explicitly Excluded from the First Pass

• old one-off legacy routes under /:appName/*
• deprecated marketing-era dashboard flows
• screens that still depend on unresolved legacy backend contracts

Frontend Structure

The Solid app should stay modular:

• auth/
• components/
• enterprise/
• workflows/
• lib/

Route Clusters

Solid parity should focus on these route clusters first:

• admin catalog and pricing
• enterprise org admin
• commerce and operational flows
• decisioning explorers and explain pages
• analytics pages inside the active dashboard console
• the active dashboard/admin console, not the old /:appName/* route tree

Async Guidance

• use async loading across route surfaces
• parallelize independent data fetching
• keep the decision APIs as the source of truth instead of reproducing stale client logic
• support export/download flows directly in the UI

Success Criteria

• the active admin/product workflows are reachable in Solid
• Solid uses the same live backend APIs as React
• analytics pages are no longer React-only
• optional analytics decision panels match React when backend panels data is available
• enterprise pages are no longer React-only
• the Solid app builds cleanly and can serve as a real admin console