Glassmorphism

You are building a web application using Next.js with Tailwind.
Read existing project instructions and reuse installed components where available.

## Project
Project brief: Not specified
Target users: Not specified
Page purpose: SaaS
Framework: Next.js
CSS approach: Tailwind
UI library: Custom / no library
Tone: Professional

## Visual direction
Base theme: Glassmorphism (visual-effect)
- Frosted glass effect with backdrop-blur
- Semi-transparent backgrounds using rgba values
- Subtle borders with low opacity white
- Layered depth with overlapping glass panels
- Gradient backgrounds behind glass elements
- Soft shadows for depth

## Resolved style
Use this final token set. It already includes the selected layers. These values take precedence over conflicting base characteristics.
Color palette: primary #7C3AED, secondary #EC4899, accent #06B6D4, background #0F172A, text #F8FAFC
Typography: Poppins for headings, Inter for body text
Load the declared fonts with the required weights. Use system fallbacks when a font is unavailable.
```css
:root {
  --tx-surface-bg: #0F172A;
  --tx-font-heading: "Poppins", sans-serif;
  --tx-font-body: "Inter", sans-serif;
  --tx-surface-bg-image: radial-gradient(ellipse 80% 50% at 20% 40%, rgba(124,58,237,0.15), transparent), radial-gradient(ellipse 60% 50% at 80% 20%, rgba(236,72,153,0.12), transparent), radial-gradient(ellipse 50% 40% at 50% 80%, rgba(6,182,212,0.10), transparent);
  --tx-card-bg: rgba(255,255,255,0.05);
  --tx-card-border: rgba(255,255,255,0.1);
  --tx-card-border-width: 1px;
  --tx-card-radius: 1rem;
  --tx-card-shadow: none;
  --tx-card-backdrop-blur: 16px;
  --tx-card-border-hover: rgba(255,255,255,0.2);
  --tx-card-shadow-hover: none;
  --tx-font-heading-weight: 700;
  --tx-font-body-weight: 400;
  --tx-text-muted: rgba(248,250,252,0.7);
  --tx-text-subtle: rgba(248,250,252,0.5);
  --tx-link-color: #7C3AED;
  --tx-button-radius: 9999px;
  --tx-input-bg: rgba(255,255,255,0.05);
  --tx-input-border: rgba(255,255,255,0.1);
  --tx-text: #F8FAFC;
  --tx-primary: #7C3AED;
  --tx-secondary: #EC4899;
  --tx-accent: #06B6D4;
  --tx-media-filter: none;
}
```
Use the CSS variables in your own components. Apply the heading and body font variables to their respective elements.

## Layout
- Place translucent panels over a gradient while keeping text areas readable.

## Interaction
- Use subtle border and shadow changes. Provide an opaque surface when blur is unsupported.

## Suitability notes
Use these limitations to assess the chosen page purpose. Explain any mismatch before applying an unsuitable treatment.
- Glassmorphism: Text-heavy pages with complex images directly behind transparent panels.

## Components
Generate the following components in this style:
- Hero
- Navbar
- Cards
- Footer

## Quality requirements
Choose section order and visual emphasis from the real content and page purpose. Add only sections needed for the task.
Use supplied content. Label sample data. Do not invent testimonials, customer logos, statistics, or compliance claims.
Every interactive control must perform its declared action or be clearly labeled as a demo.
Include loading, empty, error, success, disabled, and focus states where applicable.
Use semantic HTML, visible keyboard focus, readable text contrast, and labeled form fields.
Ensure responsive design (mobile-first). Preserve reading order and avoid horizontal page overflow.
Respect prefers-reduced-motion. Keep essential content visible when animations are disabled.

## Verification
Check representative desktop and mobile widths, keyboard interaction, and relevant component states. Run available project checks and report what was actually verified.
Use Tailwind utility classes with the declared tokens.
Product context is incomplete. Label assumptions and treat the result as a draft until the missing context is supplied.