# Project: WordPress Gutenberg eco mockup

## Standing instruction — eco-conception log

Throughout this project, collect every eco-design / sustainable-build argument
that comes up in the working process. When the user asks, summarize them as a
ready-to-use list for a dedicated slide in their client presentation.
Keep each point client-facing: the decision, and the benefit it buys.

### Running log

**Platform & theme choices**
- Base the build on a core WordPress block theme (Twenty Twenty-Five) — no page
  builder plugin, no premium theme vendor. Fewer vendor layers, less code to load.
- Custom work lives in a child theme (theme.json overrides, a few custom patterns,
  block style variations). Nothing that a core update touches, nothing to migrate off.
- Deliberately low count of custom patterns: if a redesign ever happens, less is
  thrown away.
- No theme migration on a schedule. Default themes are maintained for years and new
  WordPress capabilities arrive via core, not via the theme — so staying put is the
  low-waste choice, and switching is a redesign decision, not maintenance.
- Rejected GeneratePress-style stacks because their design power lives in a parallel
  plugin system alongside Gutenberg — more code, more lock-in, more to maintain.

**Page weight & performance**
- One webfont only (serif for headings); body text uses the reader's own system font
  — zero bytes downloaded for body type.
- Images used sparingly, cropped small, lazy-loaded, never decorative.
- No analytics, no third-party embeds, no map iframe — and therefore no cookie
  consent banner to load or maintain.
- Block themes load less PHP per request than classic themes (most styling comes from
  theme.json rather than multiple enqueued stylesheets).
- Image crops and sizes decided with phones in mind, so a 375px screen never downloads
  desktop-sized assets — the saving lands where bandwidth, old devices and battery
  actually hurt.
- Mobile-first as an editing discipline, not just a layout: asking "what survives in one
  column" cuts decorative sections before they are ever built.

**Longevity & accessibility**
- Accessibility as an eco concern: contrast passing 4.5:1 on all body-scale text means
  the site works on cheap screens, in sunlight, on old devices.
- Built so the client's own staff can edit it in the native editor — no agency
  dependency, no rebuild cycle.
- Green hosting, stated publicly on the site.

## Working notes
- Client brief not yet provided as of the last session. Do not invent a placeholder
  client; wait for the real brief before building.
- Theme decision: Twenty Twenty-Five (there is no Twenty Twenty-Six; next default is
  Twenty Twenty-Seven, ~Dec 2026 with WP 7.2).