Editorial / Magazine

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

## Visual direction
Base theme: Editorial / Magazine (visual-style)
- Serif display headings with a clear type hierarchy
- Warm paper backgrounds and thin dividing rules
- Article columns, captions, and pull quotes
- Large featured images with readable supporting text

## Resolved style
Use this final token set. It already includes the selected layers. These values take precedence over conflicting base characteristics.
Color palette: primary #1C1917, secondary #78716C, accent #B45309, background #FAF7F2, text #1C1917
Typography: Libre Baskerville for headings, Source Sans 3 for body text
Load the declared fonts with the required weights. Use system fallbacks when a font is unavailable.
```css
:root {
  --tx-surface-bg: #FAF7F2;
  --tx-font-heading: "Libre Baskerville", sans-serif;
  --tx-font-body: "Source Sans 3", sans-serif;
  --tx-surface-bg-image: none;
  --tx-card-bg: #FAF7F2;
  --tx-card-border: #D6D3D1;
  --tx-card-border-width: 1px;
  --tx-card-radius: 0;
  --tx-card-shadow: none;
  --tx-card-backdrop-blur: 0px;
  --tx-card-border-hover: #B45309;
  --tx-card-shadow-hover: 0 6px 16px rgba(0,0,0,0.1);
  --tx-font-heading-weight: 700;
  --tx-font-body-weight: 400;
  --tx-text-muted: #57534E;
  --tx-text-subtle: #78716C;
  --tx-link-color: #B45309;
  --tx-button-radius: 0;
  --tx-input-bg: #FFFDFA;
  --tx-input-border: #A8A29E;
  --tx-text: #1C1917;
  --tx-primary: #1C1917;
  --tx-secondary: #78716C;
  --tx-accent: #B45309;
  --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 a readable article column, serif headings, captions, and thin horizontal rules.
- Use multiple columns for summaries on desktop and a single reading column on mobile.

## Interaction
- Keep reading text stable. Use underlines for links and visible keyboard focus.

## Suitability notes
Use these limitations to assess the chosen page purpose. Explain any mismatch before applying an unsuitable treatment.
- Editorial / Magazine: Dense operational dashboards that need compact controls.

## 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.