Municipal Newsletter & Publication Workflow — layout software for the municipal newsletter: paginated flatplan, templates that enforce their blocks, review workflow through to print approval, PDF export.
Municipal communication departments that publish a newsletter
Overview
Municipal Newsletter — DYONYSOS
App for the department that produces a municipality's newsletter, two to four times a year, on Odoo 19 Community.
Also searched as: municipal newsletter software, magazine flatplan, municipal newspaper layout template, print-ready proof (BAT), desktop publishing for local authorities.
This is not a free-form editor. Placing a text block wherever you like, down to the pixel, is the promise of every consumer desktop publishing tool — and the result, in a town hall that uses it without a layout designer, is a lopsided newsletter, with gaps and columns that never line up from one issue to the next. This module enforces a page plan with templates: each page gets a layout — mayor's message, opinion column, two columns, three news briefs, full-page photo, events calendar, civil records — and it is the template that determines how many blocks it accepts, and of what type.
The flatplan is the working view. An issue has numbered pages; you see them all, in order, reorder them by drag and drop, and the numbering recalculates automatically — it is the screen every managing editor looks for before any other.
The template rejects what it does not accept. A “three news briefs” template has three slots, not four: a fourth cannot be filled, and the module says so. Each block has a type — headline, standfirst, body, image, sidebar, caption — a position in its template's grid, and content; moving it changes its position in the grid, not its page, unless it is explicitly moved to another page.
Civil records and the events calendar are sections of the newsletter, not special cases. They are block types like any other, coming back in every issue on the page reserved for them.
Sign-off is binding. Draft, review, approved for print, published: the workflow is linear, and approval for print is irreversible without going back to draft — you cannot return directly to review to fix a comma. Moving to approved for print is itself refused if a page is empty or a mandatory block of the template is not filled in, and the refusal names the page and block concerned.
The output is a PDF, not a print-ready file. The issue is exported to PDF, page by page, in flatplan order — a proof for review and sign-off, not a production file.
What the module does not do
No pixel-perfect layout editor: a block's position is the one given by its slot in the template, never a free position on the page. No CMYK, bleed or color profile management: for offset printing, the printer finalizes the file. No photo retouching or cropping: images are uploaded as is. No online submission of articles by departments or residents, and no tracking space for associations. No automatic distribution once published (website, newsletter, social networks): the PDF is distributed through the municipality's usual channels.
Two roles
Editor: filling in blocks, events and births/marriages/deaths sections, page plan. Publication director: templates, proofreading, final print approval and publication.
Key points
- Typed blocks — Headline, standfirst, body, image, sidebar, caption, events calendar, births, marriages and deaths — each with its own completeness rule.
- One block per slot — A “three briefs” template has only three slots: a fourth cannot be filled.
- Linear workflow — Draft → proofreading → print approval → published.
Specifications
| Price | €319 excl. VAT |
|---|---|
| License | OPL-1 |
| Odoo series | 19.0: published on the Odoo Apps Store; 20.0: published on the Odoo Apps Store |
| Version | 1.0.0 |
| Edition | Odoo Community / on-premise |
| Technical name | dyo_public_bulletin |
| Domain | Municipalities and public sector |
Price excluding VAT as displayed on the Odoo Apps Store; purchase and installation are done on the Store or through your Omnifloo instance.