Hand-drawn / Sketch

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: Education
Framework: Next.js
CSS approach: Tailwind
UI library: Custom / no library
Tone: Professional

## Visual direction
Base theme: Hand-drawn / Sketch (visual-style)
- Handwritten display headings with a readable body font
- Irregular borders and simple line illustrations
- Warm paper backgrounds with restrained bright accents
- Small imperfect details around a structured layout

## Resolved style
Use this final token set. It already includes the selected layers. These values take precedence over conflicting base characteristics.
Color palette: primary #292524, secondary #60A5FA, accent #FBBF24, background #FFFBEB, text #292524
Typography: Caveat for headings, DM Sans for body text
Load the declared fonts with the required weights. Use system fallbacks when a font is unavailable.
```css
:root {
  --tx-surface-bg: #FFFBEB;
  --tx-font-heading: "Caveat", sans-serif;
  --tx-font-body: "DM Sans", sans-serif;
  --tx-surface-bg-image: none;
  --tx-card-bg: #FFFDF5;
  --tx-card-border: #292524;
  --tx-card-border-width: 2px;
  --tx-card-radius: 8px 14px 6px 12px;
  --tx-card-shadow: 3px 3px 0 #FBBF24;
  --tx-card-backdrop-blur: 0px;
  --tx-card-border-hover: #111111;
  --tx-card-shadow-hover: 5px 5px 0 #FBBF24;
  --tx-font-heading-weight: 700;
  --tx-font-body-weight: 400;
  --tx-text-muted: #57534E;
  --tx-text-subtle: #78716C;
  --tx-link-color: #292524;
  --tx-button-radius: 8px 12px 6px 10px;
  --tx-input-bg: #FFFFFF;
  --tx-input-border: #78716C;
  --tx-text: #292524;
  --tx-primary: #292524;
  --tx-secondary: #60A5FA;
  --tx-accent: #FBBF24;
  --tx-media-filter: none;
}
```
Use the CSS variables in your own components. Apply the heading and body font variables to their respective elements.

## Layout
- Use irregular borders and small illustrations around aligned text and form controls.
- Keep large reading areas straight and maintain a clear single-column mobile layout.

## Interaction
- Use a small rotation or lift on decorative cards. Keep buttons and input targets stationary.

## Suitability notes
Use these limitations to assess the chosen page purpose. Explain any mismatch before applying an unsuitable treatment.
- Hand-drawn / Sketch: Dense financial or operational workflows that need precise compact alignment.

## Components
Generate the following components in this style:
- Navbar
- 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.