The newsfeed model
Posts, publishers, members-only posts, and what fans can say back.
What the newsfeed is made of, and the vocabulary the other two pages use.
A newsfeed
Your community's own feed of posts, in your product rather than on a social platform you do not control. Your community team writes the posts in the admin panel, and fans read, react and comment in your app.
Publishers, posts, gating and moderation are handled in the Hub. Newsfeed in the Hub docs covers that side.
Posts
A post reads like a social post, not an article. It has no title. It has:
| Field | What it is |
|---|---|
publisher | Who posted it, with a name and an avatar |
description | The body, as structured content |
images | Photos and videos |
actions | Buttons linking somewhere, like "Buy tickets" |
socialData | A link to the original, when the post mirrors one from X, YouTube or Twitch |
reactions | Emoji counts, and whether this fan has used each one |
commentCount | How many comments |
publishedAt | When it went out |
Build the card around the publisher and the body. A card that leads with a missing title looks broken.
Publishers
Every post goes out under a publisher: the club's main account, a player, the merch team. A community can have several. Fans can filter the feed by them, which is the main reason to show publisher chips at all.
Pinned and featured
Two separate flags, set by your community team.
Pinned posts stay at the top. The SDK sorts them first on every page of the feed.
Featured posts are the editorial pick. A common layout is a "For you" tab showing everything and a "Featured" tab showing only these.
Members-only posts
A post can be restricted to a membership tier. For a fan below that tier, the platform strips the body before it reaches your app, so there is nothing to accidentally leak. They still see that the post exists, who posted it, and what it would take to read it.
That is deliberate, and it is the reason to keep locked posts in the feed rather than hiding them. A locked post is an advert for membership. Membership covers the gate, which works the same way here as in the battlepass and the store.
Reactions
Fans react with emoji your community team defined, not a fixed set. A post's reactions come with counts and with whether this fan has already used each one. Reactions update on screen immediately, before the platform confirms.
Comments
Threaded, with replies nested under replies. Comments can be switched off per post. Fans vote comments up and down, react to them, edit their own and delete their own.
A comment has to be between 1 and 500 characters, after trimming whitespace. The SDK checks that before sending, so an empty or overlong comment never leaves the page.
A fan who is not signed in gets a sign-in prompt where the comments would be. Commenting, voting and reacting all need a session.