Document Council Review: Brainforge Website Migration Plan

Plan: brainforge-website-webflow-to-code-migration-2026.md
Date: 2026-03-06
Status: Revisions applied

Council Feedback Summary

1. Stack & Repo

Astro only – No hybrid with Webflow Cloud or DevLink. Fully off Webflow.
Repo structure – Marketing site under apps/marketing-site/ in the monorepo (alongside apps/platform/).

2. Environments & Staging

Staging – Dedicated staging environment (e.g. staging.brainforge.ai or Railway preview URL) for testing before QA/prod.
Promotion flow – PR → Staging (auto) → QA (manual) → Production (CEO approval).

3. Phase 2 Scope

Phase 2 – Explicitly include newsletter, resources, and search pages (BF-WEB-9b).
Services – All 5 services from CMS; case studies (4 new + 11 legacy decision deferred).

4. Rollback & Cutover

Rollback – Section 15.3 added: DNS revert to Webflow if critical issues; keep Webflow published read-only for 2–4 weeks as fallback.
Webflow cancellation – After 2–4 weeks stable, cancel Webflow plan; archive export if needed.

5. Demo Strategy

Demo pages – Migrate to Astro or iframe to standalone demo app; no links to brainforge-staging.webflow.io post-cutover.

6. Form Backend

Newsletter form – Specify backend (HubSpot, Resend, etc.) in Phase 3; fix “Oops! Something went wrong” form issue before migration.

Revisions Applied

Section	Change
4.1	Clarified Astro-only; repo under `apps/marketing-site/`
7.3	Added staging environment (staging.brainforge.ai or Railway preview)
14.3	Added BF-WEB-9b for newsletter, resources, search
15.3	Added rollback (DNS revert, Webflow read-only backup)
15.4	Added Webflow cancellation after 2–4 weeks stable
3.6	Demo strategy: no Webflow subdomain links post-cutover
17	Open question: newsletter form backend (Phase 3)

Council Sign-off

Revisions incorporated. Plan ready for Linear ticket creation and Phase 1 execution.