Lovable prompt for a footer section

Add a footer section to the existing landing page for a project management SaaS in this Lovable project, replacing whatever placeholder footer is there now, and make it earn its place. Wire the newsletter form for real — store submissions in a subscribers table and show an inline success state — because engineering managers at startups will judge the product by whether small things work.

Four stacked layers:
- Capture: a heading naming the concrete thing subscribers get from a project management SaaS (a weekly teardown, release notes, a template drop — derive it), an email field, and a quieter-than-primary submit button. Directly beneath, one sentence pointing back to the main offer with "start a free trial" as its anchor text.
- Navigation: link columns grouped by reader intent — evaluate (pricing, comparisons), learn (docs, blog), trust (about, security, contact). Pick 3-4 groups that fit a project management SaaS; plain-word headings.
- Legal: a single row with the copyright line, privacy, terms, and social icons sized to the small text, not larger.
- Optional: the product name oversized and bleeding off the bottom edge at whisper contrast, only if the style block below suits it.

Form behavior: validate email format client-side, disable the button while submitting, swap the form for a one-line confirmation on success — no page reload.

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.

Rhythm and responsive rules:
- Same top padding as the page's other sections (about 6rem), then tighten: 3rem between layers, 1rem inside each.
- On phones: layers stack full width, link groups go two columns, and the email field stays within the first screen of the footer.

After building, verify: a test email appears in the subscribers table, the success state renders inline, link group headings are specific to the product, the legal row is one line on desktop, and the footer background differs enough from the section above that the boundary is visible.