| name | newsletter-assembly |
| description | Assembles all pipeline components into the complete, polished newsletter. Use when running Phase 4 of the newsletter pipeline. Combines Phase 3 curated sections with Phase 2 events, adds introduction and closing, enforces section ordering and quality checks. Keywords: newsletter assembly, phase 4, final assembly, newsletter generation. |
| metadata | {"category":"domain","phase":"4"} |
Newsletter Assembly
Assemble Phase 3 curated sections and Phase 2 events into a complete newsletter.
Quick Start
- Read Phase 3 curated sections from
workspace/newsletter_phase3_curated_sections_*.md
- Read Phase 2 events from
workspace/newsletter_phase2_events_*.md
- Create introduction with 2-3 key highlights
- Assemble sections in mandatory order
- Add standard closing, changelog links, YouTube playlists
- Enforce heading structure and density targets for long windows
- Write output to
output/YYYY-MM_month_newsletter.md
Inputs
- Phase 3 Curated Sections:
workspace/newsletter_phase3_curated_sections_*.md (required)
- Phase 2 Events:
workspace/newsletter_phase2_events_*.md (required)
Output
- File:
output/YYYY-MM_month_newsletter.md
- Complete newsletter ready for distribution
Core Workflow
Step 1: Create Introduction
Use the standard template with 2-3 dynamic highlights:
This is a personally curated newsletter for my customers, focused on the most
relevant updates and resources from GitHub this month. Highlights for this month
include [2-3 key highlights]. If you have any feedback or want to dive deeper
into any topic, please let me know. Feel free to share this newsletter with
others on your team as well. You can find an archive of past newsletters
[here](https://github.com/briancl2/CustomerNewsletter).
Select highlights from the most impactful GA features or major enterprise announcements in the curated sections.
Step 2: Assemble in Mandatory Order
See section-ordering.md for the required section sequence.
- Introduction (with highlights)
- Monthly Announcement / Lead Section (if present in Phase 3)
- Copilot (mandatory heading shape:
# Copilot with ## Latest Releases, plus Copilot at Scale with changelogs)
- Enterprise and Security Updates (H1 for Feb benchmark-style runs)
- Resources and Best Practices (H1 when sources exist)
- Webinars, Events, and Recordings (H1, with H2 subheadings from Phase 2)
- Closing
Use --- dividers between major sections.
Step 3: Mandatory Content Blocks
Verify these are present in the assembled newsletter:
In Copilot at Scale: Standard tracking links. See quality-checklist.md.
When BENCHMARK_MODE=feb2026_consistency, expand this to the full tracking set:
- Copilot Feature Matrix
- GitHub Copilot Changelog
- VS Code Release Notes
- Visual Studio Release Notes
- JetBrains Plugin
- Xcode Releases
- Copilot CLI Releases
- GitHub Previews
- Preview Terms Changelog
In Events section: Brian's YouTube playlists at the beginning.
Step 4: Add Closing
If you have any questions or want to discuss these updates in detail, feel free
to reach out. As always, I'm here to help you and your team stay informed and
get the most value from GitHub. I welcome your feedback, and please let me know
if you would like to add or remove anyone from this list.
Step 5: Quality Checks
See quality-checklist.md for the full pre-delivery checklist.
Run through:
Reference
Done When
