Reorganize admin workflow and persist episode discussion questions

README.md

@@ -54,15 +54,20 @@ Admin auth:
 
 - Set `ADMIN_PASSWORD` on the server/container to protect `/admin` and admin stats/maintenance endpoints.
 - Without `ADMIN_PASSWORD`, admin login is disabled until configured.
+- Optional: set `CACHE_PURGE_WEBHOOK_URL` to enable one-click cache purge from Admin Operations.
+- Optional: set `DEPLOY_WEBHOOK_URL` to enable one-click deploy trigger from Admin Operations.
+- Optional: set `BUILD_COMMIT`, `BUILD_NUMBER`, and `DEPLOYED_AT` to display deployment status in Admin.
 
 The app will be available at `http://localhost:4173`.
 
 Persistent admin saves:
 
 - Admin updates are written to `data/admin-content.json`.
+- Admin drafts are written to `data/admin-content-draft.json`.
 - Built-in page hit stats are written to `data/hit-stats.json`.
 - Detailed visitor analytics are written to `data/visitor-stats.json`.
 - Backup snapshots are written to `data/backups/`.
+- Uploaded admin assets are stored in `data/uploads/` and served at `/uploads/*`.
 - `docker-compose.yml` mounts `./data` into the container at `/app/data`.
 - This keeps all admin-managed data after container restarts/rebuilds/updates.
 
@@ -75,18 +80,20 @@ Persistent admin saves:
 
 ## Routes
 
-- Portfolio home: `/`
-- Project details: `/projects/:slug`
+- Site home: `/`
+- Start Here: `/start-here`
+- Questions: `/questions`
+- Privacy: `/privacy`
+- Terms: `/terms`
 - Admin editor: `/admin`
+- Admin draft preview: `/preview`
 
 ## Admin editing
 
-- Open `/admin` to edit project card and featured-page content.
-- Use **Global Settings** to update theme, home headers, and quick tips.
-- Use **Project Settings** to update project-specific fields and README URL.
-- Use **Create new entry** to add a new project directly from Admin.
-- Enter a URL and click **Scan URL metadata** to auto-fill title, summary, domain, category, and icon when available.
-- Click **Save project** to apply updates instantly.
+- Open `/admin` to edit homepage content, links, archived studies, Q&A moderation, and analytics.
+- Use **Operations** to manage SEO metadata, sitemap paths, legal page text, redirect rules, and podcast highlights.
+- Use **Operations** to upload/delete hosted image assets for use in content and social cards.
+- Use **Save Draft**, **Preview Draft**, and **Publish Draft** for a safer publish workflow.
 - Saved edits are written to `data/admin-content.json` through the API server.
 - Built-in stats in `/admin` include page hits plus visitor details (IP, country/state/county/city, returning visitors, and recent visitor log).
 - Site Stats in `/admin` includes a Bible Questions inbox sourced from contact form submissions marked as Bible Question.
@@ -94,19 +101,11 @@ Persistent admin saves:
 - Admin now includes maintenance actions: **Export JSON**, **Backup Now**, **Prune Old Data**, and **Clear Analytics**.
 - Admin also supports restoring from a backup snapshot from `/admin`.
 - The server creates startup + daily backup snapshots and retains recent backups automatically.
-- Use the **Theme** dropdown to switch between Sandstone, Ocean, Midnight, Forest, and Sunset.
-- Use **Remove project** to delete the selected project from your local Admin data.
-- Use **Reset project** or **Reset all** to restore defaults from `src/data/projects.ts`.
-
-Scan notes:
-
-- URL scanning is best-effort and depends on site accessibility.
-- Some sites block direct scanning; Admin falls back to a proxy scan path when possible.
-- Always review scanned fields before saving.
+- Operations can trigger optional **Purge Cache** and **Trigger Deploy** webhooks.
 
 Deployment note:
 
-- To keep Admin saves working on the internet, deploy with the Node API (`server.js`) and writable server storage for `data/admin-content.json`.
+- To keep Admin saves working on the internet, deploy with the Node API (`server.js`) and writable server storage for `data/`.
 
 Titus study download gate: