Blog
Run one or more blogs/channels for company news, take posts through an editorial workflow from draft to publication, maintain them in several languages, and deliver them internally or as a public feed.
Live preview — real view with sample data
M21 · Blog
| Title | Blog | Published |
|---|---|---|
| Service due | Item 1 | 09/06/2026 |
| Defect reported | Entry 2 | 20/06/2026 |
| Handover ok | Record 3 | 01/07/2026 |
| Re-check | Item 4 | 12/07/2026 |
| Routine checked | Entry 5 | 23/07/2026 |
Not a screenshot: the same interface you get in production.
What you do here
Create one or more blogs under “Blog channels” (e.g. “Company news” or an internal team blog) and organise them into categories. Use “New post” to enter a title, teaser and the body in Markdown, pick channel, language and category, add tags and a cover image. The system suggests the short link from the title — you can override it. Note: after publication a new short link changes the public address.
The editorial workflow
A post moves from “Draft” through “Review” to “Published” — drag it through these stages on the board. Staff may write their own drafts and submit them for review; publishing itself requires the separate “Publish & approve” permission and can be granted independently of editing. To publish later, set a future date and the status “Scheduled” — the system releases it on time.
Internal or public
A channel is internal by default. Switching it to “Public” makes its published posts available without login — as an RSS feed per language, as a JSON feed for embedding into other websites and blogs, and as a single-item lookup per address. The system requires the legally mandated details for this: a link to the imprint (§ 5 DDG) plus the name and address of a responsible person (§ 18 (2) MStV). If any is missing, the channel is not served. The address pattern defines what public addresses look like (default: /en/blog/my-post). Drafts, scheduled posts and internal channels never appear in the feed.
Multiple languages
Every post has a source language. Add further languages at the bottom of the post under “Translations” — each version has its own title, short link, teaser, body and image description. Importantly, each language also has its own status and date and is released individually. The versions are independent of one another: a released English version appears even if the original is still a draft or already archived. Short links only need to be unique within one language; the same short link may exist in several languages. For pure translation work there is a separate permission, “Maintain translations”: it allows creating and editing every language version while the original post stays read-only. Releasing still requires “Publish & approve”.
Images, names and reach
A cover image needs an image description (for screen readers), its source and its licence — crediting the author is mandatory for third-party images (§ 13 UrhG). Whether your name appears under a post is controlled per post via “Show author”; this covers a withdrawal of consent or leaving the company without deleting the post. View counts are deliberately kept as a per-post total only — who read a post is not recorded.
What's inside
- Editorial
- Posts
- Post
- Blog channels
- Blog channel
- New post
- Submit for approval
- Publish
- Unpublish
- Archive
- Set status
- Pin
- Unpin
- New channel
- Edit channel
- Delete channel
Fits together with
Other blocks from the same area.
Notifications
The notification center gathers all in-app notices in one place – unread first, cleared with a single tap.
M22Chat
Talk to your team here — in topic channels, in a colleague's thread, or one to one.
M23Helpdesk
Here you handle support requests as tickets, from arrival via email, portal or chat through to resolution.
M24Contacts
A shared directory for all important contacts – people and organizations, internal, workshop, customers, authorities and emergency. With one-tap dialing, multiple channels per contact and a communication history.