Business resources

FoodTruckNerdz uses the same support-system guidance as other Dev-Centr orgs. Strategy lives on docs.devcentr.org under Business Bootstrap (capability areas); this page lists what matters here and where FTN-specific wiring lives.

Stack we care about

Job Guidance FTN notes

Scheduling / booking

Cal.com and Cal.diy — hosted Cal.com by default; Cal.diy only if we self-host deliberately

Use when founder/partner booking pages need a brand hostname (book. / cal.); put DNS in infra when adopted

Design (Figma-class)

Penpot — open design platform; stay on Figma if agency partners require it

Product UI / brand libraries; not a substitute for in-repo tokens

Secrets vault

Bitwarden and Vaultwarden — Bitwarden cloud default; Vaultwarden for tiny self-host; official Bitwarden when compliance/SSO matter

Current practice: Bitwarden items + custom fields → local env / Vercel (see website private-docs). Prefer ESC later for matrix sync

Email lanes

Email area — human vs product messaging

Resend on updates.foodtrucknerdz.com; Customer.io for journeys; ZeptoMail for human mail — see infra + website messaging docs
Full hub

Business Bootstrap · Stack map

Related on this hub

  • Partners & Services — product integrations (POS, delivery, discovery), not org bootstrap tools

  • Website: private docs & team secrets (Bitwarden / ESC) in the website component

  • Infra: org Pulumi stacks — vendor strategy stays on Dev-Centr; this org encodes DNS

Anti-patterns

  • Duplicating the full Cal.com / Penpot / Vaultwarden essays in FTN docs — link out; keep FTN pages for our hostnames and credentials.

  • Treating Partners as the place for Bitwarden or Penpot — different job.