Act as a product writer and front-end engineer. Build a changelog page for {{business_name}} in my {{tech_stack}} project, styled in {{visual_style}}. Turn these raw notes into the first entries: {{source_notes}} Writing each entry: - a title naming the change from the user's side ("Export invoices as CSV"), not the ticket name - a type: New, Improved or Fixed, as a text tag with a matching icon - 1 to 3 sentences: what changed, who it helps, where to find it - a screenshot or short muted clip only when it shows something new - a link to the docs or the setting - no internal ticket numbers, no "bug fixes and performance improvements" Structure: entries newest first, each an article with a permalink anchor on its date or title; grouped by month with h2 month headings that stick while scrolling the group. Layout: 1280: a date column of 3 (sticky within each entry) and content of 7, max 1000px; 768: date above content; 360: single column, 16px gutters. 48px between entries, a 1px divider. Type: entry titles 20 / 22px weight 600; body 16px, line height 1.6, max 65ch; dates 14px in tabular-nums. Features: - filter buttons by type, with aria-pressed and visible focus, reflected in the URL so a filtered view can be shared - RSS and Atom feeds, plus email subscription if the project sends email - a quiet "New since your last visit" label, remembered in localStorage, with no dot animation States: an empty filter result with Clear filter; long titles wrap; missing media collapses; pagination or year archives after 50 entries. Media: videos muted, with controls and a poster, never autoplaying; images with width, height and alt text. Motion: none beyond 150ms hover states; nothing under prefers-reduced-motion. Avoid: emoji tags, confetti, version numbers without dates, every entry called "Improvements".