Refactor: scripts, skeletons and production mode

Author: DavidBabinec

README.md

@@ -34,6 +34,14 @@ The first visit creates the site and admin account.
 
 `bun run dev` defaults to SQLite at `.tmp/dev.db`. Set `DATABASE_URL=postgres://...` to use Postgres instead.
 
+To try the app locally in production mode (built admin SPA from `./dist`, no Vite, no `--watch`, same SQLite dev DB):
+
+```sh
+bun run start
+```
+
+Builds the admin SPA, then starts the server on `http://localhost:3001`. If port 3001 is already held by a dev server (or a previous `bun run start`), you'll be prompted whether to kill the holder and take over. `bun run dev` uses the same prompt for ports 3001 and 5173.
+
 ## Production Deployment
 
 The default self-host install is **SQLite + one container** — recommended for most users (single sites, hobby and small-business installs, single-author or small editorial teams). No `.env` file required:

bun.lock

@@ -11,6 +11,7 @@ import {
   Card,
   Heading,
   Select,
+  SkeletonBlock,
   Sparkline,
   Stack,
   Text,
@@ -108,18 +109,11 @@ function AnalyticsDashboard() {
         <Alert tone="danger" title="Failed to load analytics">{error}</Alert>
       )}
 
-      {/* Skeleton while loading for the first time */}
-      {loading && !stats && (
-        <Stack direction="row" gap={12}>
-          {[0, 1, 2, 3].map(i => (
-            <div key={i} style={{ flex: 1 }}>
-              <Card padding={16} bordered>
-                <Text variant="muted" size="sm">Loading…</Text>
-              </Card>
-            </div>
-          ))}
-        </Stack>
-      )}
+      {/* Skeleton while loading for the first time. Uses the host's
+          shared `<SkeletonBlock>` so the analytics plugin's loading
+          state reads identically to every other loading region in the
+          editor (same three-bar shape, same shimmer cadence). */}
+      {loading && !stats && <SkeletonBlock minHeight={240} ariaLabel="Loading analytics" />}
 
       {stats && (
         <Stack gap={24}>