A weekly newsletter is a stack of small decisions: which photo, which three dates, how to phrase the reminder about picture day so it doesn’t get buried under the science fair recap. Newsletter Studio, Bloomz’s block-based newsletter editor, has always let a communications coordinator or teacher build that out visually, drop in a header, a couple of paragraphs, an image, a button, a divider, a footer, and land on something that looks finished instead of pasted-together. What changed is where that editor lives and what it’s built from.
A newsletter surface, not a buried tab
Newsletter Studio used to be reachable only one way: open Create Post, switch to the Newsletter tab, and start from there. If you wanted to check on a draft or grab a template without composing a post at the same time, there was no door in for that. The Bloomz web app now has a standalone Newsletters surface, its own tile, its own gallery of drafts and published templates, separate from the compose flow. Open it, pick a template or start blank, and build with the same six block types the editor has always supported: header, paragraph, image, button, divider, and footer. Nothing new was invented at the block level, this is the same editor, just no longer stuck behind a compose screen.
This surface is web-only for now. It’s built on the same browser-based editor Newsletter Studio has always used, and the tile and route only show up when you’re on the web app.
Start from your own saved templates
The more useful change is inside the editor. An “Insert from Template” option (which also needs the Message Templates feature turned on for your school) opens a picker of your group’s own saved newsletter templates. Pick one, and its blocks land in the newsletter you’re building, ready to edit. Save a layout once (the early-release reminder, the picture-day block, the weekly footer) and reuse it instead of rebuilding it every Friday.
To be precise about what this is: these are your group’s own saved newsletter templates. They are not the certified Message Template Library that other message types draw from, and they don’t carry translations. If a newsletter needs to reach families in other languages, that is a separate step.
Why this matters for the Friday newsletter
We’ve written before about why most school newsletters go unread: they arrive in one language, ship late because building them takes too long, and mostly reach families who were already engaged. Starting from your own saved templates chips away at the second problem directly. A coordinator who starts from last week’s structure isn’t rebuilding a layout the team has already built a dozen times, and moves faster because of it.
What’s not here yet
Newsletter Studio still has six block types, no video, poll, document, or RSVP block has been added. There’s no drag-and-drop import from outside design tools and no open or click analytics on a sent newsletter yet, that reporting doesn’t exist on the newsletter surface today. And the editor itself remains web-only, there isn’t a mobile app version to build a newsletter in yet.
Available now
The standalone Newsletters surface and Insert from Template are available on the Bloomz web app for any school with the Studio Editor feature turned on, the same flag that already governs Newsletter Studio. Insert from Template additionally requires Message Templates to be enabled. If your school hasn’t enabled it, ask your success manager. See how newsletters fit into the rest of Bloomz messaging on the Communication Hub page.