Implement file upload in Contact Form using Uppy

Author: webstackdev

.env.example

@@ -46,6 +46,7 @@ CRON_SECRET="<cron_secret_here>"
 
 # Environment variable
 PUBLIC_GOOGLE_MAPS_API_KEY="<api_key_here>"
+PUBLIC_GOOGLE_MAP_ID="<map_id>"
 
 ##
 # SMTP remailer

.vscode/dev-server-cli.mjs

@@ -8,7 +8,7 @@ import yargs from 'yargs/yargs'
 import { hideBin } from 'yargs/helpers'
 
 const pidFile = `${tempDir}/debug-server-hmDAr917.pid`
-const port = 3000
+const port = 4321
 
 /**
  * Ensure we do not start a duplicate dev server instance

.vscode/settings.json

@@ -60,6 +60,7 @@
     "koko",
     "labelledby",
     "LGPD",
+    "lighthousejs",
     "LIMS",
     "Linkify",
     "liradb",

_TODO.md

@@ -58,66 +58,3 @@ Vercel AI Gateway, maybe could use for a chatbot:
 Vercel AI Gateway, maybe could use for a chatbot:
 
 https://vercel.com/kevin-browns-projects-dd474f73/astro-webstackbuilders-com/ai-gateway
-
-## POM → Page/Route Mapping
-
-### BreadCrumbPage (BreadCrumbPage.ts)
-
-- Routes it targets: listing pages `/articles`, `/services`, `/case-studies`, then navigates to the first detail page it can find under each (e.g. ``/articles/<slug>`).
-
-- 1:1 or 1:many: 1:many (listing + arbitrary first detail for each content type).
-
-- Used by: `breadcrumbs.spec.ts`
-
-### ComponentPersistencePage (ComponentPersistencePage.ts)
-
-- Routes it targets: none hardcoded in the POM; the specs drive navigation. In practice it's used to start on `/` then navigate via Astro View Transitions to `/articles` and sometimes `/services`.
-
-- 1:1 or 1:many: 1:many (it's a view-transitions persistence harness for whatever page contains the selector under test).
-
-- Used by:
-    - `footer.spec.ts` (navigates / → /articles)
-    - `themepicker.spec.ts` (navigates / → /articles)
-    - `head.spec.ts` (navigates / → /articles, /services, plus a reload back to /)
-
-### HeadPage (HeadPage.ts)
-
-- Routes it targets: none hardcoded; it asserts head/meta/JSON-LD on whatever page you've navigated to. In the structured data suite it covers `/`, `/articles`, first `/articles/<slug>`, `/services`, first `/services/<slug>`, and `/contact`.
-
-- 1:1 or 1:many: 1:many (generic head / structured-data helper).
-
-- Used by: `structured-data.spec.ts`
-
-### MarkdownPage (MarkdownPage.ts)
-
-- Routes it targets: `/testing/markdown` (dedicated fixture page).
-
-- 1:1 or 1:many: 1:1 (single fixture route).
-
-- Used by: `markdown.spec.ts`
-
-### NewsletterPage (NewsletterPage.ts)
-
-- Routes it targets:`/testing/newsletter` (dedicated fixture page).
-
-- Also interacts with: the action endpoint `/_actions/newsletter/subscribe` (via `waitForResponse` expectations).
-1:1 or 1:many: 1:1 (single fixture route, plus the action endpoint).
-
-- Used by: `newsletter-subscription.spec.ts`
-
-### PerformancePage (PerformancePage.ts)
-
-- Routes it targets: none hardcoded; in current specs it's used against `/` (homepage).
-1:1 or 1:many: 1:many in design (generic perf helpers), but currently exercised as 1:1 on `/`.
-
-- Used by:
-    - `core-web-vitals.spec.ts` (goes to `/`)
-    - `lighthouse.spec.ts` (goes to `/`, but tests are skipped)
-
-### PwaPage (PwaPage.ts)
-
-- Routes it targets: primarily `/` (homepage), including helpers that wait for SW readiness/caches (some of which are environment-dependent).
-
-- 1:1 or 1:many: 1:many in capability (PWA primitives), but current coverage is 1:1 on `/`.
-
-- Used by: `offline-mode.spec.ts`