EdgeKit Publications
Newsletters built from this morning’s stories
Feeds fill as the edition sends, named checks hold back a broken one, and your email platform delivers it, scheduled by an editor or by autopilot.
SubjectMainB · subject test
SubjectWhat the tariff ruling changes on MondayPreheaderPlus the week in marketsSlots
- IntroRich textGood morning. The tariff ruling lands today: here is what it changes.
- Editors’ picksCuratedPort deal signed after a six-month standoffWhat the new tariffs mean for exporters
- Top storiesFeedTariff ruling: what changes for importers on MondayGilts slide as the Bank signals a pauseThe week ahead: five numbers to watchFilled at the send · preview
The Morning BriefTue 8 June
What the tariff ruling changes on Monday
Good morning. The tariff ruling lands today: here is what it changes.
Top stories
Tariff ruling: what changes for importers on MondayGilts slide as the Bank signals a pauseUnsubscribe · View in browser
ChecksAll passed
- Every variant has a subject
- Feed stories are live by the send time
- Under Gmail’s clipping limit64 KB of 102 KB
The morning shift
Somebody rebuilds your newsletter by hand every morning
They copy links out of the CMS, paste them into the email platform, fix the headlines, check it on a phone and send before the next story lands. The list lives in the email platform, so a reader who unsubscribed there is still subscribed in their account.
| By hand | With Publications |
|---|---|
| Links copied out of the CMS, and the 6:55 story misses the 7:00 send | Stories arrive from your CMS, and feeds fill at the moment the edition sends |
| A test goes to the whole list, or the subject line is blank | Named checks keep Schedule disabled while one is failing |
| The email platform’s list and your account pages disagree | One list on the reader record, pushed to your platform, with its unsubscribes coming back |
| Somebody has to be at a desk on Saturday | Autopilot creates and schedules the edition |
How an edition is built
What Publications takes off the morning shift
Feeds
The 7:00 edition carries the 7:00 story
A feed picks stories by section, tag, content type or author, and fills at the moment the edition sends, not when somebody built it. A story your editors already picked is not repeated.
- The window you want: since the last edition, or the last few hours
- No story twice: skip what an earlier edition already sent
- Include
- SectionMarketsSectionEconomyTagtariffsTypeStory
- Exclude
- Tagsponsored
- Window
- Since the last sent edition
- Order
- Newest first · 4 stories
Filled at Tue 07:00 · Europe/London
Editors’ picks
Your editors choose. Nobody pastes links.
Editors search every story live on the title, drop the ones they want into a slot and put them in order, rewriting a headline or summary for the email without touching the article. Their own intro or sign-off cannot break the template.
- Headline and summary can change for one edition; image and link stay the story’s own
- Bold, italic, links, headings, lists and quotes, never raw HTML
- One editor at a time: others see the edition read-only, with Take over
- Tariff ruling: what changes for importers on MondayMarkets · 06:55Add
- Exporters brace for the new tariff scheduleEconomy · Mon Added
- 1Port deal signed after a six-month standoff
- 2Exporters brace for the new tariff scheduleHeadline editedHeadlineWhat the new tariffs mean for exportersLeave a field empty to send the story’s own.
- 3Inside the new rules on market data
Editing · others see this edition read-only
Schedule and autopilot
Set the days once. Autopilot does the mornings.
Pick the days, send times and time zone once. Autopilot creates each edition up to 21 days ahead and schedules it, or leaves it as a draft for an editor. An edition that fails a check stays a draft, and one you unschedule is left alone.
- 7:00 stays 7:00 when the clocks change
- Breaking news is a newsletter with no schedule, sent when you say
- Every autopilot send names the person who switched autopilot on
- Send timeSubjectStatus
- Mon 7 June 07:00Markets brace for the tariff rulingSent
- Tue 8 June 07:00What the tariff ruling changes on MondayScheduled · autopilot
- Wed 9 June 07:00The Morning Brief, Wed 9 JuneScheduled · autopilot
- Thu 10 June 07:00The Morning Brief, Thu 10 JuneDraft · 1 check failing
- Fri 11 June 07:00—Upcoming
One list
Unsubscribe once, and every system agrees
The list lives on EdgeKit’s reader record and is pushed to your email platform. EdgeKit owns the unsubscribe link and the one-click unsubscribe header, and an unsubscribe made inside your ESP comes back. Run EdgeKit’s paywall and subscriptions too, and they share that record.
- A one-click unsubscribe header on every edition
- Opening the link never unsubscribes: a person confirms on a page in your brand
- That page offers every list on the title, not just this one
- The Morning BriefSubscribedSince 14 Feb · sign-up
- Markets WeeklyUnsubscribedTue 8 June · unsubscribe link in an edition
- Policy DigestUnsubscribedMon 7 June · in your ESP, synced back
ESP sync
Before it can be scheduled
A broken edition cannot be scheduled
Schedule stays disabled while any named check is failing.
Checks1 check failing · 2 warnings
- Every variant has a subjectPassed
- The newsletter list is deployedPassed
- The email channel is set up in your ESPPassed
- Every variant has its ESP message and segmentFailingB · subject test has no segment
- Every variant rendersPassed
- Push is set up and within your ESP’s capsPassediOS 1,204 of 1,912 bytes · Android 1,204 of 4,000
- The edition has contentPassed
- Feed stories are live by the send timeWarning1 story due by 07:00 is not live yet
- Under Gmail’s clipping limitWarning94 KB of 102 KB
- Desktop and mobile previewSee the email at both widths, and the push as the platform will receive it.
- Test sendsA named group gets every variant first, so the newsroom sees what readers will.
- At most onceIf the platform’s answer is unclear, the send waits for a person. EdgeKit never retries a send blind.
In every edition
Push, archive, tests and tracking, built in
Templates in your brand
EdgeKit builds your templates: logo, colours, type, social links and the postal address your footer needs.
As many newsletters as you need
Daily, weekly or breaking, each with its own list, schedule and sending setup, on shared templates and brands, with no new code.
Push beside the email
One edition carries an iOS and Android push through your ESP, filled from a story, editable, sent to its own segment and checked against each platform’s size limit.
A web archive on your domain
One shareable page per edition, its main version frozen at the send, hideable one by one, and indexed by search engines only if you switch that on.
A/B variants
Each variant has its own subject, preheader and push text and goes to its own segment, under one campaign.
Tagged links
Link templates add your UTM parameters to every link back to your title, filling in the newsletter, send date, variant and slot.
Corrections, not edits
A sent edition is a fixed record of what went out, to which segment and when. A correction is a duplicate you fix and send.
Roles that fit a newsroom
The editor role writes and schedules. Channels, segments and brands sit with whoever you give them to.
Adoption
Beside your CMS and email platform, not instead of them
Publications is adopted on its own. It reads your stories, builds and checks the edition, and hands it to the platform that already delivers your email. Your paywall, sign-in and billing can stay where they are.
White-glove onboarding: we set it up with you, start to finish.
- Your CMSArc XP today
- EdgeKit PublicationsBuilds, checks, schedulesThe list, on the reader record
- Your email platformYour ESP, as it runs today
- Inbox and phoneEmail, and push through your ESP
- 01
Connect your CMS
EdgeKit copies your stories, then picks up each one your CMS reports as changed. Arc XP is connected today; for another CMS, EdgeKit builds the connector.
- 02
Brand your templates
EdgeKit builds templates in your brand. Your team sets up each newsletter: its list, slots, feeds and schedule.
- 03
Connect your sending platform
Your team creates the campaign and a segment per variant in your ESP, and EdgeKit checks every id against it before it saves.
- 04
Test, then hand over the mornings
Preview it, send a test to your group and schedule the first editions by hand. When they look right, switch on autopilot.
Questions
What media groups ask about Publications
Do our editors have to leave Arc XP?
No. Stories are written and published in your CMS as they are today. EdgeKit reads them from there, and editors pick and order them in the edition.
Do we have to change our email platform?
No. EdgeKit renders the edition and your ESP delivers it, so delivery, segments and reporting stay where they are. Push goes through your ESP too. If EdgeKit does not connect to yours yet, it builds the connector.
Can an edition go out with nobody at a desk?
Yes, if you want it to. Autopilot creates and schedules each edition from the schedule, and its feeds fill as it sends. It runs the checks a person does, and an edition that fails one waits as a draft. One difference: an empty push is filled from the first live story at the send. Set autopilot to create only and an editor schedules each one.
What does EdgeKit keep from our CMS?
A copy of your stories, drafts and scheduled ones included, so a feed can take a story the moment it goes live. EdgeKit picks up each change your CMS reports and writes nothing back.
What happens if a send fails?
Each variant and channel is its own send. A failed one can be sent again once fixed; an unclear one waits for a person, as it may already be delivered. Nothing resends on its own, and your team and EdgeKit are notified.
Who can schedule an edition?
Anyone with the send permission. The built-in editor role writes and schedules editions. There is no separate approval step: scheduling is the approval, and the edition stays editable until it sends.
Where do sponsors go?
Sponsorship runs through LiveIntent, Passendo, Kevel or the email ad manager you use, its placements built into your template. EdgeKit’s own ad manager is in development.
Do we need the rest of EdgeKit?
No. Publications keeps the newsletter list on EdgeKit’s reader record, which is what keeps unsubscribes in agreement. Your paywall, sign-in and billing can stay where they are, and you can add them later.