Back to blog
Intranet/ Feeds

Apr 3, 2026

Adding social features to your intranet without rebuilding it

Everyone keeps telling you the intranet should feel more like a social product. Nobody is giving you six months to rebuild it. Drop Feeds into the routes you already have.

The employee intranet is 300 SharePoint pages and a link to Slack. Somebody in HR keeps saying it should feel "more social" and nobody on engineering has six months to rebuild it. You don't need six months.

What "more social" actually means

Strip the buzzword and it comes down to three things: announcements people can react to, comments that thread under posts, and unread badges that actually mark things as read when people catch up. That's not a social network — that's a feed. Which is exactly what Feeds ships.

Everything else the intranet already does — the org chart, the policies, the PTO request form — stays put. You're not rebuilding the intranet. You're giving it a discussion surface.

Drop Feeds in next to what you already have

One feed app per channel — HR, engineering, announcements, the Stockholm office — and the component can render any combination of them. Pass one uid or several, space-separated, and it merges them into a single stream.

<wy-feed uid="intranet-hr intranet-eng intranet-announcements"></wy-feed>

Posts, replies, reactions, mentions, unread badges — all in the component. Give different employee groups different uid combinations on their landing page and you get scoped feeds without writing a filter layer.

Who posts what

Announcements go through HR. Engineering posts release notes. The Stockholm office posts about the fika schedule. Each area has its own feed app on the server; on the client you decide which apps a given user sees. One API for timeline, comments, and unread state — no grafting.

AI summaries of the week

Nobody wants to scroll through 80 unread posts after a week of vacation. Feeds ships an unread summary that collapses them into a paragraph — pluggable model, so you pick the one that fits your cost and compliance constraints.

What you don't have to build

  • Unread tracking per user per post, with correct behavior across devices.
  • A reaction pipeline that doesn't double-count on reconnect.
  • Push hooks for the unread badges the mobile team is going to ask for.

The auth is the intranet's existing auth. The users are the users you already have. The feed is a component on a route. Ship it Thursday.

Ship the collaboration layer today

Free to start. No credit card. Your first component running in under ten minutes.

Talk to us

Questions, integrations, or just kicking the tires. Real answers from real engineers.