Community formats for newsrooms
Your articles fill the feed. They do not build a community. Ten card formats that turn a news app into a place readers come back to.
Most newsrooms start the same way. An RSS feed or a scraper pushes every published article into the app as an Article card. The feed is full from day one. Nothing else happens.
That is normal, and it is not a failure. Automated import solves the volume problem. It does not solve the return problem. A reader who only ever receives finished articles has no reason to open your app instead of a search engine, and no reason to come back tomorrow rather than next month.
Community content is the layer on top. It is small, cheap to produce, and it does one thing your articles cannot do: it makes the reader a participant instead of an audience.
The formats below work the same way for a trade title serving one industry and for a regional title serving one area. The examples alternate between the two.
The three jobs community content has to do
Invite. Ask something only your readers can answer. A question, a call for photos, a vote on what to report next.
Respond. Show that answers were read. Quote a comment in a follow-up. Publish the result of the poll. Name the reader who sent the tip.
Repeat. Same format, same day, same slot. Rhythm beats volume. One reliable Friday question outperforms twenty one-off experiments.
A format that does not do at least one of these is just more content.
What the automated feed already covers
Already handled by import | Still missing |
|---|---|
Article cards from RSS, scraping, or your CMS | A reason to comment |
Social cards mirroring your own posts | A place to ask the newsroom something |
Video and Audio from your existing production | Reader contributions that make it into reporting |
Everything your own newsroom published | Anything worth discussing that you did not publish |
Push on every new article | Any signal that a person is on the other side |
Ten formats for news-driven communities
1. The daily question
Card type: Poll
Cadence: Every weekday, same slot in the feed
One question tied to the top story of the day. Two to four options, no free text. "Will you pass the new packaging levy on to your customers?" Voting takes three seconds, which is why it works: it is the lowest possible first act of participation. Readers who vote once are far more likely to comment later.
Publish the result the next day as a Text card, with the count and one line of interpretation. In a trade title that result is news in itself, because nobody else has the number.
Watch out for: polls on questions where the answer is a fact. Polls are for opinion and priority, not for quizzing readers.
2. The outside story
Card type: Article, with the editor note filled in and comments on
Cadence: Two or three times a week
An editor picks one piece of journalism your newsroom did not publish. A regulation explainer, a study, a court ruling, a documentary, a report from an adjacent industry. Not from a direct competitor, and never as a replacement for your own reporting.
The card is the Article. The community part is the editor note above it: one sentence of framing and one question. "Retail solved its returns problem with this model. Would it survive in wholesale?" Readers who never comment under your own articles will comment under someone else's, because there is nothing at stake for them in disagreeing.
Three things this earns. Your app becomes worth opening even on days when your desk published little. Readers see an editorial voice choosing, not a machine importing. And the comments tell you which outside topics your audience actually cares about, which is free research for your own agenda.
Watch out for: sending traffic to a competitor. Pick publications that do not compete for your subscribers, and stay away from paywalled pieces your readers cannot open.
3. The open thread on a running story
Card type: Thread
Cadence: Whenever a story runs longer than one day
A supply bottleneck, a strike, a price round, a new regulation coming into force, a plant closure. Open a Thread card headlined by the situation, not by your article: "Delivery times from your suppliers are slipping again. What are you seeing in your own orders?" The card opens straight into the comment view, so there is no article standing between the reader and the input field.
Two payoffs. Readers get the fastest picture of what is happening in their market, which is exactly what they subscribe for. Your desk gets numbers, examples and named cases that no newsroom of your size could gather alone. Every verified item becomes reporting, and the follow-up article should say where it came from.
Watch out for: an open thread with no editor in it. Threads need someone from the newsroom answering in the first hour, or they die.
4. Ask the reporter
Card type: Thread for questions, Long Post for the answers
Cadence: Every two weeks, one reporter at a time
A reporter announces a window: "I cover the new packaging regulation. Ask me anything until Thursday." Questions come in as comments. Thursday, the answers go out as one Long Post, with a User Block linking to the reporter's profile.
This is the single fastest way to turn a byline into a person. It also surfaces what readers actually do not understand about your beat, which is usually not what the newsroom assumed. In a trade audience it doubles as demand research: the questions show you which practical problem is unsolved right now.
Watch out for: promising an answer to every question. Say up front that you will answer the most common ones.
5. The reader assignment
Card type: Text or Image card for the brief, Gallery card for the result
Cadence: Weekly or tied to the season
Ask for something specific and easy: your shelf display for the new season, your booth at the trade fair, the queue at the new bakery, your view of the bridge closure. Specific beats open. "Send us your photos" gets nothing. "Photograph the price sign you had to change this week" gets a hundred.
Collect submissions through comments or chat, then publish the best as a Gallery card with each contributor credited in the caption, with company and town. In a trade audience that credit is professional visibility, which is worth more than any incentive you could pay.
Watch out for: copyright. Ask for permission in the brief and record it. The Gallery card has a caption per image, so name the sender there.
6. The newsroom short
Card type: Video
Cadence: Two or three times a week, straight out of the news conference
Sixty to ninety seconds, shot vertically on a phone, no intro, no music, no set. An editor coming out of the morning conference: "We just argued for ten minutes about whether to name the company. Here is why we decided not to." Or a reporter in front of the building they are about to enter.
The point is the face and the voice, not the production. Readers who have seen your editors speak react differently in the comments underneath them, and they recognise the byline the next time it appears. This is also the format most likely to be watched to the end, because it is short and it is clearly not a broadcast package.
Practical rules. Publish it the same day it is shot, or do not publish it. Burn in subtitles, since most people watch without sound. Keep files well under the 100 MB card limit. If there is nothing to see, record it as an Audio card instead and keep everything else the same.
Watch out for: letting it drift into a video show with a format, a jingle and a schedule. The moment it looks produced, it stops working.
7. The newsroom note
Card type: Long Post or Text
Cadence: Once a week, or after any big story
How you reported the piece. What you could not confirm and why. Which company refused to answer. Which reader tip changed the angle. Two hundred words is enough.
Trust in news is low, and abstract trust campaigns do not move it. Showing your working does. This format also gives readers something to react to that is not the subject of the article itself, which keeps difficult stories from turning every comment section into the same fight.
Watch out for: turning it into self-promotion. Note the doubts, not the awards.
8. The agenda vote
Card type: Poll, then Article or Long Post
Cadence: Monthly
"We have time for one of these three investigations next month. Which one?" Real options, real consequence, result published.
Readers who chose the topic read the resulting story at a completely different rate, and they tell colleagues about it, because it is partly theirs. It also gives your editorial meeting a data point it did not have before.
Watch out for: offering options you are not prepared to actually do. One broken promise here costs more than the format earns in a year.
9. The service thread
Card type: Thread, pinned in its own mix
Cadence: Permanent, one per topic
"Which supplier still delivers this part in under two weeks?" "How are you documenting the new inspection rules?" "Who takes back old equipment?" These questions have nothing to do with your journalism and everything to do with why people open your app on a Tuesday morning.
Open one permanent Thread per recurring need, let readers answer each other, and have an editor correct wrong information. Over months these threads become the most valuable pages you own, they are almost free to run, and they are the hardest thing for a competitor to copy, because the answers belong to your readers.
Watch out for: stale answers. Check the pinned threads once a month.
10. Member spotlight
Card type: Long Post with a User Block
Cadence: Every two weeks
Three questions to one reader, subscriber, or contributor, with their photo and a link to their profile. Who they are, what they follow your coverage for, one thing they wish more people in the trade knew.
A community becomes real when members can see each other. Until then, every reader assumes they are alone in the app with the newsroom. This format also rewards the regulars, who are the people who keep comment sections alive.
Watch out for: always picking the loudest commenter. Rotate, and include readers who never post.
Card types mapped to community jobs
Card type | Community job it does best |
|---|---|
Poll | First act of participation, agenda setting, closing the loop |
Thread | Sustained conversation, tips, peer to peer help |
Text | Fast newsroom voice, results, corrections |
Long Post | Answers, spotlights, background, anything that needs structure |
Gallery | Publishing reader contributions with credit |
Video | Faces and voices, the news conference made visible |
Audio | The same job when there is nothing to see |
Image | Calls to action, single strong moment |
Article | Your own journalism on import, outside journalism on purpose |
Comments and reactions are switched on per mix, not per card. Put community formats in their own mix with comments enabled and give it a fixed slot in the news feed or a pinned tab, so readers learn where to look.
A starter week
Day | Format | Effort |
|---|---|---|
Monday | Daily question (Poll) | 5 minutes |
Tuesday | Newsroom short (Video) | 10 minutes |
Wednesday | Result of Monday's poll (Text) | 5 minutes |
Thursday | Newsroom note (Long Post) | 30 minutes |
Friday | Reader assignment brief (Image) | 10 minutes |
Two per week | Outside story with editor note (Article) | 10 minutes |
Permanent | Two service threads | Monitoring only |
Under two hours a week. Start with three of these, not ten. Add one when the previous one runs by itself.
Moderation, in three rules
Be present early. The first hour of a thread decides its tone. An editor comment in that hour sets the standard for everyone who arrives later.
Answer, do not defend. Readers accept a correction faster than a justification.
Hide, do not argue. Comments can be hidden, and good comments can be highlighted. Use both. Highlighting is the stronger tool, because it shows the room what good looks like.
How to tell if it is working
Views are the wrong measure here. Watch these instead:
Share of readers who have ever interacted once. Vote, reaction, or comment. This is the number that predicts retention.
Repeat commenters. Ten people commenting weekly is a community. A thousand people commenting once is a spike.
Returning sessions per week per user. Community formats should move this, articles alone rarely do.
Tips and submissions that became reporting. The one number that justifies the effort to the newsroom.
Filter analytics by the mix that holds your community formats, and compare it against the automated article mix. The difference is what this layer is worth.



