# Homepage Deliverables Specification — Amendment

**Date:** 2026-06-04
**Amends:** `Homepage Deliverables For Figma To Tailwind Drupal Handoff.pdf` → **§3 "Tailwind CSS Requirements"**
**Status:** Agreed with client.

---

## Change: `tailwind.config.js` requirement waived

The original spec (§3) requires the freelancer to provide a **`tailwind.config.js`** with
theme-extension tokens (colors, font families, typography scale, spacing scale, border radius,
container widths, breakpoints), a production-ready **purged build**, and "Tailwind token
discipline" (configured design tokens instead of raw values in markup).

**The client has explicitly asked to remove the Tailwind config / build step.** Accordingly,
the following §3 sub-requirements **no longer apply**:

- ❌ `tailwind.config.js` file
- ❌ `theme.extend` design-token configuration
- ❌ Production-ready **purged/compiled** build (no `@tailwindcss/cli`, no `css/output.css`)
- ❌ "Token discipline" via config tokens — design values are expressed inline instead

## Current Tailwind approach (replaces the above)

- **Tailwind Play CDN** loaded per page: `https://cdn.tailwindcss.com/3.4.16` — classes resolve
  in-browser at runtime, **no build step**.
- Design values are written as **arbitrary-value utility classes** directly in the markup —
  e.g. `bg-[#2b286f]`, `text-[69px]`, `rounded-[7px]`, `font-['Poppins',sans-serif]`,
  `leading-[81px]`. There is no central token config.
- Rules not expressible as utilities live in **`css/custom.css`** (linked from each page).
- Legacy `css/input.css` / `css/output.css` are dead artifacts (no page links them).

## What still applies from §3

The rest of §3 is unchanged and still required:

- Clean, utility-first implementation
- Minimal custom CSS outside Tailwind (only `css/custom.css` where utilities can't express a rule)
- Fully responsive across desktop / tablet / mobile

## Unchanged

All other spec sections remain in force — modular section components, Drupal-Twig readiness
(§4), dynamic-content readiness (§5), section-specific structure (§6), minimal vanilla JS with
`data-*` hooks (§7), accessibility (§8), performance/cleanliness (§9), and the acceptance
criteria (§13) — **except** that "Tailwind configuration is included and organized" in §13 is
read as "Tailwind is used cleanly via the CDN approach above."

> Note: `docs/integration-notes.md §5` still documents the superseded `tailwind.config`/v4
> `@theme`/CLI-build approach and should be updated to match this amendment.