Skip to project details
South Jersey Real Estate
Menu

Editorial automation

South Jersey Weekly Newsletter

A cloud-hosted editorial and delivery system that turns trusted South Jersey sources into a useful newsletter while keeping proof review, audience handling, and daily sending under the owner’s control.

Active production workflowCloud-hosted, owner-approved delivery to consented readers, capped at 250 recipients per New York day
Approved issueReady for guarded delivery
South Jersey neighborhood homes used in the approved newsletter issue header
Weekly regional briefHuman-reviewed before delivery
Trusted sources → human approval → daily batches
01

The need

Producing a dependable weekly issue requires more than drafting copy: sources, approval, responsive email design, audience state, quotas, compliance content, and duplicate prevention all need to agree.

02

The editorial contract

Editorial preparation and production delivery remain separate. Google Drive supplies the dated issue and header. The owner verifies receipt of the Gmail proof, explicitly approves that exact proof, and separately approves the exact audience and delivery plan before production staging or arming.

Issue path

Approval is part of the product.

Google Drive supplies the dated issue and header. The owner verifies receipt of the Gmail proof, explicitly approves the exact proof, and then separately approves the exact audience and delivery plan. Only after both approvals may SJRE Newsletter Cloud stage and arm separate Brevo campaigns for daily batches of up to 250 readers per New York day. Delivery state and scheduling remain in the cloud, and uncertain send results pause for reconciliation before another batch can proceed.

  1. 01

    Dated Google Drive issue and header inputs with approved-source preparation

  2. 02

    Verified Gmail proof receipt and explicit approval of the exact proof

  3. 03

    Separate approval of the exact audience and delivery plan

  4. 04

    Responsive email output with an isolated Brevo list and campaign per daily batch of up to 250 recipients

  5. 05

    Cloud scheduling, persisted send state, installed-alarm verification, and guarded reconciliation

Public trust

Visible boundaries

No unfinished draft is sent. Verified Gmail proof receipt, explicit approval of the exact proof, and separate approval of the exact audience and delivery plan are required before staging or arming.

Consent, suppression checks, audience blocklists, compliance content, campaign identity, duplicate state, and sufficient credits for each batch remain required; total delivery is capped at 250 recipients per New York day.

SEND_PENDING is persisted before send. Uncertain results pause for reconciliation and are never blindly retried. The cloud controller owns delivery state and scheduling without requiring an online NAS or local runtime.

Current record

What is verified today

  • Approved dated issues have entered the cloud-hosted Brevo workflow using the established responsive template.
  • About 850 subscribers as of October 30, 2026, according to the owner-reported audience record. Eligible and delivered audiences vary by issue after consent, suppression, and delivery checks; this does not mean every subscriber receives every issue.
  • The controller records exact proof and plan approvals, campaign identities, daily batches, installed alarms, and send or reconciliation outcomes; editorial preparation and production sending remain owner-approved.
Current outcome

An operating companion newsletter workflow serving the consented audience grown by South Jersey Real Estate.

Next step

Continue the owner-reviewed cycle, verify the actual installed schedule, and reconcile ambiguous send outcomes before proceeding.

Supporting technology

  • Cloudflare Workers
  • Durable Objects
  • Google Drive
  • Gmail
  • Brevo
  • Responsive HTML

Continue from the project’s verified current status.

Visit South Jersey Real EstateReturn to all projects