Changelog

Linked vault hosting guidance (Bitwarden cloud vs official self-host vs Vaultwarden) from Private docs & team secrets to Dev-Centr Business Bootstrap; FTN docs hub gained Business resources for Cal.com/Cal.diy, Penpot, and vaults.

Square Developer app renamed to FoodTruckNerdz; API version bumped to latest; use-case set documented (payments, customers, team, catalog). Credentials and OAuth redirect matrix recorded; secrets from Bitwarden synced into local env + Vercel (Square sandbox, Resend on updates.foodtrucknerdz.com, Radar, Stripe sandbox, Customer.io test keys, Adapty, Yoti sandbox, Linear inbound). Private-docs options (edge vs OIDC) and GitHub-org-secrets guidance captured.

Production deploys on the FTN Vercel team were failing typecheck because Convex _generated API lagged communityEvents. GitHub Actions was also targeting a personal Vercel scope; deploy now uses team slug ftn-cea058e2.

Adapty was chosen as the subscription management stack for paid app access (mobile IAP + future Stripe web sync), kept separate from business-team memberships and Square POS.

Customer.io (United States data center) was chosen as the messaging / marketing brain for Email, SMS, Push, and In-app — with Resend kept for hard transactional mail and Twilio for SMS transport. WhatsApp and Slack are out of scope for now.

Late July also locked email lane separation: Resend stays in application code on updates.foodtrucknerdz.com; human Gmail send-as uses ZeptoMail when needed; marketing stays on Customer.io (news.). Org DNS for Resend/DMARC moves toward the infra Pulumi repo.

Community events (meetups / conferences / workshops) landed as a separate model from truck gig listings, with a unified public schedule, RSVP attendee management, PR approval for FTN-affiliated branding, and a Yoti verification scaffold.

Late July: the public site redesign shipped — marketing homepage, Browse/Search discovery routes, red + cream identity with Diana Montero logo credit, account context switching, and SolidStart retired from deploy (archive footnote only).

Tooling: monorepo moved to pnpm 11.17.0 (Corepack) with allowBuilds in pnpm-workspace.yaml, and setup docs rewritten for Node 24 + the four workspace members.

Website performance monitoring and website testing were added to the ops roadmap with an explicit note that no vendor research has been done yet.

Next.js is documented as the official web stack; SolidStart is on hold. The site gained a developer platform role (users.platformRole), an FTN developer panel (floating control, not in public nav), and a /dev/styles catalog for card surfaces including optional liquid-glass-react cards.

Mid-month, deployment and backend work matured: Vercel and GitHub Actions were aligned with the pnpm monorepo (including deploying from the repository root), the Next.js build was relaxed when Convex URLs are absent at build time, and product work shipped for venues and events and auth, with docs updated to match.

Later in April, the public face of both web apps moved: a shared glassmorphism direction on Next and SolidStart, a SolidStart on-ramp with a 3D hero and geolocated search, and follow-up fixes for shared styles, logos, and layout. Documentation was reorganized in Antora (shared guides on the ROOT module; older material under the old-website module). A short-lived doc experiment about code signing in a release pipeline was reverted. The month ended with lockfile maintenance and small comment cleanups around Square and internal APIs.

Housekeeping and foundations: day-to-day editor settings moved to .vscode/, org naming and cross-links in docs pointed at FoodTruckNerdz on GitHub, and a batch of workspace updates was merged in from a fork. Separately, the map stack grew multi-provider support and client performance hooks, and code-workspace settings were refreshed from the shared template approach.

The monorepo took the shape you see today: pnpm and package metadata at the repository root, the Next app in site-nextjs/, Node 24 on Vercel, Biome for formatting and lint, and environment variables documented in Antora instead of only in ad hoc .env comments. Old migration paths and folder names were cleaned up, Zustand stores in the Next app were restored, and small doc quality rules landed (AsciiDoc list style, how to republish the doc site). That February wave sits right after a late-January security pass on React Server Components (below).

A React Server Components advisory was addressed through a merge from the fork queue, and a few default editor nags were toned down. The doc tree moved to a flatter docs/ layout, check-in behavior was captured in the published doc set, and pnpm became the default story in build instructions. JSON and code-workspace files picked up the same Biome treatment as the rest of the repo, and per-repository settings kept aligning with the common workspace template. This January work completes the move that began when Antora was introduced the previous fall.

Repository layout, Git, and first-run deployment all moved at once: the Next app lived under a clearer subfolder, Vercel and Convex install and build lines were made explicit, example env files were committed on purpose, and a round of over-eager Git LFS tracking was unwound. Cursor and Turbopack cache ignores, pnpm config, and workspace metadata (including funding) landed in the same period, overlapping the Antora transition that had started in October.

Narrative content moved out of ad hoc READMEs and into Antora, with a root README.adoc as the shell for humans cloning the repo. An in-tree dev-setup GUI was extracted to its own repository so the monorepo could stay slimmer. Early October was mostly stashes and small doc nudges before that cutover landed.