Skip to content
innflow-aiPublic

Latest commit

 

History

221 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Innflow marketing frontend

Standalone Next.js App Router frontend for Innflow's property-management marketing site.

This repository is operationally separate from the authenticated product app. It does not import product code, use Prisma, require workflow-runtime variables, deploy infrastructure, alter DNS, or change the current Framer site.

Phase status

  • Phase A: discovery and content-truth documents complete.
  • Phase B: semantic design tokens and shared homepage primitives complete.
  • Phase C: responsive homepage vertical slice complete.
  • Phase D: code preparation complete. Supporting routes, metadata/discovery surfaces, redirects, attribution, a URL-level legacy inventory, and local release evidence are implemented. Preview deployment, DNS cutover, and rollback execution remain approval-gated.

Local development

npm install
cp .env.example .env.local
npm run dev

Open http://localhost:3000.

Quality checks

npm run lint
npm run typecheck
npm run test:run
npm run build
npm run audit:site
npm run audit:bundle

The production output is served locally with:

npm run start

Configuration

Destinations are centralized in src/config/site.ts. These environment variables configure the app, contact, and analytics settings:

  • NEXT_PUBLIC_MARKETING_ORIGIN
  • NEXT_PUBLIC_APP_ORIGIN
  • NEXT_PUBLIC_SIGNUP_URL
  • NEXT_PUBLIC_CONTACT_URL
  • NEXT_PUBLIC_POSTHOG_KEY
  • NEXT_PUBLIC_POSTHOG_HOST

Demo calls to action use siteConfig.demoUrl, currently the approved Cal.com booking link. The legacy /demo and /BL/BL-demo routes redirect there as well. Qualification is deferred to a future Innflow flow.

Deployment instructions (approval-gated)

No deployment was performed. When explicitly authorized:

  1. Create a preview deployment from this repository with the environment values above.
  2. Run the quality gate and browser review against the preview origin.
  3. Complete the legal-content, link, metadata, consent, analytics, and redirect audits.
  4. Approve docs/REDIRECT_MATRIX.md and docs/MIGRATION_PLAN.md.
  5. Keep Framer live while preview review and rollback rehearsal are completed.
  6. Schedule DNS cutover separately; do not remove Framer until monitoring confirms the new origin and rollback window are healthy.

Source provenance

Approved logo and product media were copied into public/ from read-only sources listed in docs/DISCOVERY.md. Third-party reference screenshots remain untouched in output/playwright/ and are not shipped as site assets.

Releases

Packages

Used by

Contributors

Languages