Why this workflow matters
Most teams lose consistency not because content is weak, but because distribution is manual. A small automation layer turns publishing into a repeatable operation.
Publishing should be one action. Distribution should be automatic.
Release flow
1) Publish article in both locales
Create EN and RU pages with the same slug and add that slug to the bilingual manifest.
Reason: The automation workflow detects newly added slugs from the manifest diff.
2) Push to main
Once pushed, GitHub Actions reads the new slug and runs the send script for EN and RU.
Reason: This removes manual campaign creation for every article release.
3) Verify send status in Resend
Open Broadcasts and confirm both sends were created and delivered to the intended segments.
Reason: Operational visibility helps catch env or domain issues early.
Operational checks
| Capability | Status |
|---|---|
| Footer form appears site-wide | enabled |
| Language-based segment routing | enabled |
| Welcome email on subscribe | enabled |
| Auto send on new slug push | enabled |
References
- Resend Broadcasts API documentation: resend.com/docs/api-reference/broadcasts
- Internal release model: bilingual slug manifest + automated workflow trigger on push.