All articles
Guides

How to turn your local website's stories and events into a newsletter issue

Build one email issue from the articles, events and listings you already published, without rewriting everything.

lightbreak StaffOctober 11, 2026 · 2 min read

By the end of this guide you will have one finished newsletter issue assembled from stories, events and listings already on your website. You need access to your site's recent posts, your email platform, and an hour or so of focused time. The workflow below is manual and works in any email platform, and it keeps your site as the home of the full story.

Select the timely items

Go through what you published since the last issue and pick only what is still timely on send day. An event happening this weekend qualifies. A restaurant profile from three weeks ago qualifies if nothing newer pushed it out. A story about a meeting that already happened usually does not, unless you are reporting what happened there. Aim for a short list, roughly five to eight items, because a local issue that reads in five minutes gets opened again next week.

Keep the site and the email in their lanes as you choose. The website is the archive, where the full story, the full event listing and the full photo set live. The email is the front porch, where a reader decides in a few seconds whether to click through. That split is what lets you reuse published material instead of rewriting it.

Build the issue
  1. 01
    List what you published since the last issue

    Open your site's posts and pages from that window and note the headline, URL and publish date of each candidate item.

  2. 02
    Cut the list to the timely items

    Cross off anything already dated, already covered in a previous issue, or thin on its own. You should see five to eight items left.

  3. 03
    Order the items

    Put the item with the broadest interest first and group the rest by type, such as news, events, food and homes.

  4. 04
    Write a short intro for each item

    Write two or three sentences per item in the email's own voice, covering what happened and why a local reader cares. Do not paste the whole article.

  5. 05
    Link each item to its canonical page

    Add a link to the story, event or listing page on your site, and make sure it points to the permanent URL, not a preview or draft URL.

  6. 06
    Check dates, prices and links

    Open every link in the draft, confirm event dates are still correct, and recheck any price or address against the site page.

  7. 07
    Add a subject line and preview text

    Write a subject line that names the most interesting item, and preview text that names a second one.

  8. 08
    Preview the issue

    Send a test to yourself and open it on a phone. Fix anything that looks broken, then stop.

  9. 09
    Decide to send

    You, or whoever owns the issue, make the call to send it from the email platform. Nothing goes out until a person says so.

Where people get stuck

The intro is the most common wrong turn. Editors copy the whole article into the email, and readers stop scrolling. The email's job is the short version, and the site's job is the full story. Two or three sentences plus a link is enough for most items.

Dates are the second trap. An event listed on your site last week may have moved or sold out. Open the organizer's page or calendar entry for anything time-sensitive before you commit it to the issue. A wrong date in an email is worse than no email.

The third is the send decision. It is tempting to schedule the issue and walk away. Keep a human looking at the final preview, even on a deadline week. A broken link or a story that changed overnight costs more than the fifteen minutes the check takes.

What to check in the final pass

  • Every link opens the live, permanent page on your site, not a draft or a redirect that could break.
  • Every date in the issue matches the organizer's current listing, including start times.
  • Every price and address matches the site page it came from, down to the dollar.
  • The subject line names a specific item, not a generic greeting.
  • The test email opens cleanly on a phone, where most local readers will open it.

Where software helps

The manual version takes a couple of hours per issue. Some of that work can be handed off. lightbreak builds a newsletter issue from local sources, writes each story in the publication's voice, makes GIFs for homes, pets and restaurants, and checks the finished issue with a review agent that reads the whole issue against every source it came from, covering links, photos, prices and dates. On a September 29 Leander Scoop issue the review agent opened 31 links and fact-checked 18 stories in 27 seconds. It does not send anything. Most publications on lightbreak ship an issue in under 15 minutes, and the finished issue pushes to Beehiiv or ActiveCampaign, where your subscribers, delivery history and list health stay put. A person still decides when it sends.

Questions people ask

Does my email platform stay the sender?
Yes. lightbreak builds the issue, and your email platform sends it. lightbreak works with Beehiiv and ActiveCampaign today, and your subscribers, delivery history and list health stay exactly where they are.
Who decides when an issue goes out?
A person does. The software can prepare and check the issue, but nothing sends until someone makes the call.
Do I have to rewrite my site's stories for the email?
No. Write a short email-specific intro of two or three sentences, then link to the canonical page on your site for the full story.
Does lightbreak work with my platform?
lightbreak works with Beehiiv and ActiveCampaign today. There is no subscriber migration, and moving over costs nothing.
How much does lightbreak cost?
Pricing depends on how many publications you run and is quoted on a call. Every plan includes unlimited issues, every source feed, stories in your voice, automatic GIFs, the review agent, API and MCP access, and templates set up for you.
From the same team

More tools from the people behind lightbreak.