Bolt prompt for a footer section

In this Bolt project, create the footer for the a project management SaaS landing page as its own file — src/components/Footer.tsx, or the equivalent for the current stack — and import it at the end of the page so the instant preview shows it the moment it compiles. Footers written inline at the bottom of a page file get neglected; a separate file keeps this one honest.

Contents, in order:

First, a brand block and newsletter capture side by side on desktop: wordmark, a two-line description of a project management SaaS written for engineering managers at startups (what it is, then who it serves), and an email form whose label promises a specific artifact — not "subscribe to our newsletter". The form is secondary; under it, add a plain link repeating "start a free trial" for anyone who reached the bottom unconverted.

Second, the link architecture: derive 3-4 column headings from the shape of a project management SaaS — a tool gets Product / Docs / Company, a service gets Services / Work / Company, a content site gets Topics / About / Follow. Real destinations only; where a URL is unknown, leave a TODO comment instead of inventing a route.

Third, a hairline-separated legal strip: copyright, privacy, terms, and social icons inline at text size.

Fourth, optionally, the product name set enormous behind the strip, clipped at the bottom edge, faint enough to skim past.

Visual direction:
Minimal dark style. Near-black canvas (#0A0A0B) with one elevated surface tone (#141416) for cards — never more than two surface steps. Hairline borders (1px, white at 8% opacity) instead of shadows; if a shadow is unavoidable use 0 1px 2px rgba(0,0,0,0.4) and nothing softer. Text in exactly three steps: white at 92% for headings, 60% for body, 40% for captions. Generous negative space — section padding at least 120px on desktop, 64px on mobile. The accent color appears only on interactive elements and one hero highlight, nowhere else.

Palette: a strict neutral ramp (white, #F5F5F5, #E5E5E5, #737373, #171717) carries the entire interface; pick one accent and use it only for primary CTAs, active states, and a single hero highlight. If the accent appears more than five times per viewport it stops being an accent. Keep semantic colors (success, error) desaturated so the accent stays in charge.
Typography: one geometric sans (a Futura/Poppins-class face) at three weights maximum (400/500/700). Scale: 64-88px hero, 32px section heads, 18px lede, 16px body, 13px caps labels with 0.08em tracking. Tight headline leading (1.05-1.1), relaxed body (1.6). Let the geometry carry the personality — no italics; weight and size do all hierarchy.
Motion: none. Zero scroll animations, zero entrance effects — the page is fully composed the instant it paints. Spend the motion budget on input feedback instead: 120-150ms ease-out color and transform transitions on hover and press states only. Hold this constraint absolutely; it is a statement, not an omission.

Spacing and breakpoints:
- Top padding about 1.5x the gap between mid-page sections, so the footer reads as an ending rather than another block; 4rem brand row to columns, 3rem to the legal strip.
- Below 768px: the brand block and form stack first, columns go 2-up, and the legal strip wraps with icons on their own line.

Check in the preview: the footer lives in its own imported file, no invented URLs exist (TODOs instead), the email input and button align on one line at desktop width, columns hold 2-up on narrow viewports without overflow, and the clipped wordmark never scrolls the page sideways.