Changelog

• Tease: Guidance Evolves Through Practice
• Lede: This changelog records front-end guidance updates as implementation experience turns preferences into reusable recipes.
• Why it matters:
  • It separates established principles from newly observed techniques.
  • The updates emphasize evidence, restraint, responsive behavior, and browser verification.
• Go deeper:
  • Read the eight preferences for the current front-end guidance.

Notable changes to this guidance, newest first.

2026-07-03

• Added a layout-cleanup recipe: test with representative worst-case content, distinguish data defects from semantic and CSS defects, fix each at its owning layer, and use responsive wrapping or clamps only as guardrails for legitimate variation.

2026-06-20

• Published this site as a readable view of the front-end preferences.
• Refined the guidance after an adversarial source-faithfulness review: corrected the motion guidance to “used sparingly, mostly for hero/feature moments”; added the concrete Nectar entrance/stagger values (~1.0–1.2s with 0.05–0.2s stagger); gated the WordPress lessons behind a WordPress/Nectar condition and added a non-WordPress “find the nearest known-good reference” step; trimmed WordPress-specific jargon out of the general principles; clarified the Nectarblocks 2.6.0-vs-2.5.4 version split.
• Initial version: captured eight core preferences distilled from a client WordPress + Nectarblocks rebuild — adapt-don’t-invent, preserve-first, keep-it-boring, match-with-restraint, motion-subtle-and-last, real-media-crop-checked, prove-it-in-a-browser, recipe-shaped lessons.