B2BEA.org Rebuild custom-html-import-spec

Full legacy body rendered for humans

B2BEA.org V1 Custom HTML Import Spec

Source of record: RedKey local project artifact draft.

• Project: B2BEA.org Rebuild
• Project ID: a820dd0c-6cef-4133-bfbd-d802fd806e44
• Artifact: custom-html-import-spec
• Version: 1
• Status: draft
• Generated: 2026-05-08

Purpose

Define how B2BEA can publish special custom landing/resource/editorial pages without letting custom HTML bypass metadata, accessibility, route, design, analytics, and rollback controls.

Allowed Uses

• Homepage variants
• Major campaign/resource landing pages
• Signature editorial features
• Approved one-off imports from design tools

Custom HTML is not allowed for standard directories, admin, vendor, member, company, auth/account, forms, tables, filters, or operational workflows.

Import Record

type CustomHtmlImport = {
  id: string;
  route: string;
  owner: string;
  title: string;
  status: 'draft' | 'preview' | 'published' | 'archived' | 'rolled_back';
  treatment: 'campaign_custom' | 'signature_editorial' | 'home_custom';
  htmlEntry: string;
  assetBundle: string[];
  metadata: RouteMetadata;
  usesGlobalHeader: boolean;
  usesGlobalFooter: boolean;
  approvedExternalAssets: string[];
  analyticsHooks: string[];
  previewUrl?: string;
  publishedVersion?: string;
  rollbackVersion?: string;
  createdAt: string;
  updatedAt: string;
};

Required Checks

Before preview:

• route does not conflict with an existing canonical route
• HTML has one main landmark
• page title and H1 are present
• external assets are allowlisted
• no inline secrets or credential-like values
• no private workspace links exposed

Before publish:

• SEO/GEO/social metadata passes validation
• desktop and mobile screenshots pass
• accessibility smoke passes
• analytics hooks are present
• rollback version exists if replacing a published page
• owner and publish approver are recorded

Storage Decision

Preferred storage model:

• Import registry record in Sanity or Supabase.
• Source HTML and asset bundle versioned in the app repo or durable object storage.
• Published app consumes a versioned immutable bundle.

Open decision remains: Sanity, Supabase, or both for registry ownership.

Rollback

Rollback must restore the previous published bundle and metadata as a single operation. If no prior published version exists, archive the custom route and remove it from sitemap/search index.

Acceptance Criteria

• Custom imports cannot bypass route registry, metadata, or QA.
• Standard page families cannot be silently implemented as custom imports.
• Publish and rollback are auditable.
• Implementation can build a registry and validation pipeline from this spec.