Skip to content

For organisations: publishing posts and events

Your organisation can write posts and events directly in locali — no detour through your own feed. What you write appears on your organisation page, in the spaces whose area or topics match, and (for events) in the town calendar.

This page walks through all of it once: switching it on, writing, sharing, feeds, numbers.

Switching it on

The organisation decides for itself — no request to the hub team, and it does not depend on the organisation type. Clubs, institutions, initiatives and businesses take the same route:

  1. Open your organisation's management area (the gear icon on the profile) → Settings.
  2. In the "Publish your own" block, choose Enable.

Two things to know:

  • Only the Owner can flip the switch. Editors write and publish, but do not control the capability.
  • Enabling means the publishing rules apply. They are shown next to the switch and are available in the hub at any time.

Switching it off works the same way and is not a sanction: everything already published stays visible, only new entries are unavailable until you switch it on again.

If an organisation repeatedly breaks the rules, the hub team can withdraw the permission. A note then replaces the switch — in that case only the hub team can restore it.

The hub has to offer it

Direct publishing can be switched off hub-wide. If your hub has not enabled it, the block does not appear at all. Ask the hub team in that case.

Writing a post or an event

Once enabled, the management area gains a new section, "Aktuelles & Termine". It lists everything you have written, and New starts an entry — you choose between post and event.

Both are a single form, not a multi-step wizard. Very little is mandatory:

Entry type Mandatory Optional
Post title, text subheadline, teaser, up to 4 images
Event title, start, location end, all-day, recurrence, description, image

Everything optional sits behind More options — the form stays deliberately plain.

The text editor

The editor offers bold, italic, headings, lists and links. What you see is what appears later — you do not need a preview.

Images

Up to four images per post. The first one is the preview image: it appears on the card in the feed and in the link preview when somebody shares the entry. Every image takes an image description for people who cannot see it — please fill it in.

Subheadline and teaser

  • Subheadline — a short second line under the title.
  • Teaser — the preview text. Left empty, locali takes the beginning of your text automatically. If you set your own teaser, it applies everywhere: in the feed, in shared links and in the RSS feed.

Checking the reach

Right above the publish button, "Appears in:" lists the spaces that will receive the entry — for events plus the note that it lands in the town calendar. It updates as you type and never blocks.

If nothing but your own organisation page is listed, the default areas and topics are missing. You set them once under Aktuelles & Termine → Areas & topics; every entry can still be adjusted individually afterwards. Editors may edit this section too.

Draft, in review, published

  • Draft — locali saves your form as you type. If you break off, it offers the draft back next time. A draft is never public.
  • In review — the first entries of a newly enabled organisation are looked at by the hub team before they go public. The default is the first three (the hub can set a different number). The aim is a response within 24 hours. After that every further entry goes live immediately — locali tells you when that point is reached.
  • Published — publicly visible.
  • Cancelled — events only: the event stays visible and is marked as cancelled, with your reason. A wrong event is worse than no event — so cancel instead of deleting.

If an entry is rejected in review, the rejection always names the concrete rule and hands the entry back for revision and resubmission. Nothing is deleted silently.

Sharing

Right after publishing, a share sheet appears. It shows the real link preview first — exactly the card with image, title and teaser that turns up in WhatsApp or on Facebook.

  • On a phone, Share opens the device's usual share menu (WhatsApp, Signal, email …).
  • On a desktop you get Copy link plus buttons for WhatsApp and Facebook.
  • The same share button is available later on every entry in the list — and in the notification when a reviewed entry is approved.

Instagram

Prepare for Instagram puts the image and a ready-made caption at hand. To be honest about it: Instagram does not allow links in posts. That is why it is three steps — save the image, copy the text, paste it into Instagram. The caption ends with the locali reference so people can still find the full entry.

Your feeds

Under Management → Settings → "Your feeds" there are two addresses:

Feed Content
Posts (RSS) your organisation's directly written posts
Events (calendar) your directly entered events as a calendar subscription

Both copy with one click. The point behind them: embed them on your own website. Then you write once in locali and your own website shows it automatically — locali is your source, not another channel you have to maintain on the side.

Readers can also subscribe to your event calendar: on your public organisation page, in the Events tab, via Subscribe to calendar. New events then appear in their calendar app automatically.

If you already have a feed on your website

Many organisations already run an RSS or iCal feed that locali reads. You can run both in parallel — but events and posts behave differently. This is the most important point on this page:

  • Events are merged. The same event coming in both ways appears publicly exactly once; the richer entry (with image, with a longer text) wins the display.
  • Merging requires an exact match of title, start and location — not "roughly similar". Sommerfest and Sommerfest 2026 therefore stay two entries. If you run both in parallel, keep the titles literally identical.
  • Posts are not merged. There is no such merging for posts. If you deliver the same announcement through your feed and also write it directly in locali, it stands there twice, permanently — on your organisation page, in the spaces and in "Aktuelles & Termine". Nobody cleans that up later.

Hence one simple rule: publish every announcement in only one of the two places. Either you write posts directly in locali and your feed only delivers events — or your posts keep coming through the feed and you do not additionally write them here.

When an organisation uses both, a note appears under Management → Sources. When you switch over completely, you can decommission the old source there — the cleanest way to get rid of duplicated posts.

Who may do what

Task Owner Editor
Switch publishing on and off yes no
Write, edit and cancel posts and events yes yes
Set the default areas and topics yes yes
Submit, change, pause and decommission external sources (RSS/iCal) yes no
Manage members and roles yes no

The cut behind it: what flows in under the organisation's name is a trust decision and belongs to ownership. What the organisation writes — including the reach of its own entries — is editorial work.

The numbers on your entries

Every entry shows two numbers in the management area: views and via shared links. The second one answers the practical question "does anybody actually arrive through the link I shared?".

What you should know about them:

  • The numbers are visible only to your organisation — never public, never a ranking input. Nothing in locali decides the order except time.
  • They are counted without tracking individual visitors — no cookies, no profiles, and no IP address is stored with the counts. It is a plain sum. (Like any web server, the hub sees the IP address of a request while it is being served — it protects against overload and abuse and is not stored with the counts.)
  • So it is an approximation: a reload counts again, your own views count too, and automated visits count too whenever the program renders the page like a browser — some search engine crawlers do. Read the number as "how often was this opened", not as "this many different people".

The rules

locali is not an advertising platform. The guiding question for every entry: does it tell about local life — or does it actively sell? Friday's onion tart, the anniversary, changed opening hours, a job opening: local life. Prices, discounts, vouchers, "today only", buy CTAs: selling.

For businesses there is an additional guideline of roughly one to two posts per week — events and cancellations do not count. It is a soft guardrail, not a hard limit. Clubs are held to the same standards as businesses.

The full version with all the examples lives in the hub under Publishing rules — linked at enablement, while composing, and in the feed settings.

Frequently asked questions

Question Answer
Do we have to ask the hub team before we start? No. The Owner switches it on in the settings.
Is this only for clubs? No — any organisation type can switch it on.
Does my name appear under the entry? No. The organisation is always the public sender, never the person who wrote it.
How long does the review of the first entries take? The aim is a response within 24 hours.
What happens if we switch it off again? Everything already published stays visible; new entries need it switched on again.
An event is called off — delete it? No, cancel it. The event stays visible with the cancellation note so nobody turns up for nothing.
We already have a calendar feed. Will everything be duplicated? No, identical events are merged — when title, start and location match exactly.
And if we already have a post feed (RSS)? Then it will be duplicated: posts are not merged. So publish every announcement in only one of the two places — or decommission the old source.

Read on