Note: This is a test post. It exists only to trigger and validate the subscriber-notification pipeline. Please ignore it.

Purpose

This article is a deliberate test fixture for the FAQ subscriber-notification system. When this post is merged to main, the GitHub Actions deploy workflow should:

  1. Detect the new _posts/2026-03-22-test-sub-notification.md file via git diff --diff-filter=A HEAD~1 HEAD.
  2. Extract the title and excerpt fields from the front matter.
  3. Call the notify-subscribers Supabase Edge Function with the post metadata.
  4. The Edge Function should send a notification email to every active subscriber (confirmed = true, unsubscribed_at IS NULL).

What to Check

After the workflow run completes, verify:

  • The notify job in GitHub Actions ran and reported success.
  • At least one test subscriber received an email containing the post title and excerpt.
  • The notification_log table in Supabase contains a row for the slug test-sub-notification.
  • The email includes a working Read the full article link and a functional Unsubscribe link.

Mockup Content

The following paragraphs are placeholder prose used to give the email a realistic body length so that rendering and line-wrapping can be assessed in a real mail client.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Fusce vehicula ligula at orci tincidunt, nec feugiat quam sodales. Integer commodo nisi vel dolor blandit, at feugiat enim consequat. Quisque imperdiet lorem ac nisi convallis, a efficitur augue vulputate.

Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo.

This post was created for internal QA purposes. It will be removed after the notification system has been verified.