Skip to content

Phase 3.5: Newsletter Generation with Mailchimp API Integration #934

Description

@ckenst

Overview

Develop a newsletter generation system that works with the Mailchimp API. This includes building a draft generator, integrating with Mailchimp, and supporting editorial review while maintaining subscriber consent and privacy.

Goals

  • Create a command-line tool to generate newsletter drafts for a target month
  • Read conference data from _data/current.yml and select relevant conferences
  • Generate polished Markdown drafts with timely information (CFP, registration, early-bird)
  • Support editorial review and sponsor content
  • Integrate with Mailchimp API for draft creation and management
  • Keep final sending manual until the workflow is proven safe

Implementation Notes

  • Upgrade or replace tools/monthly_data.rb with a non-interactive command (e.g., --month 2026-09)
  • Define recurring newsletter sections and selection rules
  • Document the Newsletter Format with representative past issues
  • Render Markdown drafts rather than raw YAML
  • Group supported CFP, registration, and early-bird info without inventing missing details
  • Include clearly marked areas for introduction, sponsor copy, announcements, and notes
  • Store generated drafts in a version-controlled, predictable location
  • Make repeated generation deterministic
  • Integrate Mailchimp API for managing drafts (create, update, preview)
  • Protect Mailchimp API credentials (use environment variables or GitHub secrets, never commit)
  • Maintain human control of sending—no automatic send

Related

  • Part of Phase 3.5: Newsletter Generation & Platform Migration
  • Depends on: Phase 1.5 completion
  • Complements: Quality Ledger & Metrics (Phase 2)

Acceptance Criteria

  • monthly_data.rb or successor accepts --month parameter
  • Markdown drafts are generated and stored predictably
  • Newsletter format is documented with examples
  • Mailchimp API integration allows draft creation
  • API credentials are protected (never committed)
  • Editorial review areas are clearly marked
  • Generated drafts are repeatable and deterministic
  • Tests cover month selection, chronological order, missing dates, escaping, links, empty-month behavior
  • Workflow documentation includes command, expected output, review checklist, and troubleshooting

Resources

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions