Skip to main content

Marketing App Spec

apps/marketing is the optional public-facing marketing site for the Continu.dev starter kit.

Use it when a fork needs a separate acquisition, brand, or SEO surface outside the authenticated product app.

Responsibilities​

  • homepage and marketing landing pages
  • public brand and positioning pages
  • SEO-focused content and campaign entrypoints
  • optional public forms or intake flows that do not require the product shell

Non-responsibilities​

  • organization staff workflows
  • tenant portal workflows
  • platform-operator routes
  • authored Convex backend modules

Boundaries​

  • keep public presentation concerns in apps/marketing/src/**
  • keep starter-wide config, theme primitives, and shared typed helpers in packages/*
  • if a flow becomes authenticated or tenant-aware, move it into apps/app

Homepage Direction​

The homepage presents aegi as an agency operating system, not as a collection of unrelated tools.

  • Lead with the continuity of client context from intake through delivery and revenue.
  • Use editorial pacing, generous type, sticky narrative sections, and restrained motion.
  • Keep editorial headings compact and close to the oversized aegi treatment, while reserving its most extreme compression for the wordmark itself.
  • Use the localized final hero phrase as a restrained, reduced-motion-safe pastel color cycle that rests between quick transitions.
  • Use a large editorial product stage and restrained interface compositions rather than dense feature-card grids.
  • Keep imagery optional and subordinate to hierarchy, product clarity, typography, and copy.
  • Keep each homepage section in its own route-local component so it can evolve independently while the homepage remains a small composition layer.
  • Let the three primary product showcases disclose deeper, product-accurate context through accessible expansion dialogs without adding persistent copy to the page.
  • Let the hero stage remain pinned while product chapters scroll beside it and update the active preview.
  • Carry motion through the page with restrained reveal, field-drift, hover, and capability-rail patterns that respect reduced-motion preferences.
  • Keep the pre-launch call to action focused on early access and product updates.