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.
Built from the same certified templates as everything else
The more meaningful change is underneath the editor. Newsletters now compose from Bloomz’s Message Template Library, the same district-owned, certified template system every other message type in Bloomz already draws from. That library isn’t a separate, newsletter-specific set of canned blurbs. It’s the one library, with the one certification catalog: translator name, credential, who certified it, when.
Inside the editor, an “Insert from Template” option opens the same template picker you’d see composing a regular post or mass message. Pick a certified template, and its text lands in the newsletter as a paragraph block, translations attached. There’s no second template system to keep in sync, no English-only newsletter blurb sitting next to a fully certified Spanish version of the same reminder used everywhere else. If a template’s languages are certified, that certification travels with it into the newsletter, the same way it does everywhere else in Bloomz, as we covered in one review queue, five content types.
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. Pulling from certified templates chips away at the second problem directly. A coordinator who starts a newsletter with a certified “early release Friday” block isn’t retyping and re-translating a sentence the district has already said correctly a dozen times, they’re reusing it, translations included, and moving 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 certified-template insert 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. 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.