An activity feed is the time-ordered record of what has happened to one thing: what people said about it, what the system did to it, and what got attached along the way: held together by a rail down the side so the entries read as one thread rather than a pile of notifications. The six blocks here run from whole thread pages down to the rows they are built from.
Two kinds of row live in every feed and they should not look alike. A person's row carries an avatar, a name, a time, a body and the reactions it drew. A system's row carries a glyph where the avatar would be and a single sentence naming the object it acted on. Give them the same weight and a channel of conversation reads like an audit log. Read state is the other thing to settle: marking the whole feed read the moment it opens is convenient for the badge and useless for the person, who came back to find the line they had got to.
Commits with their hashes, a diff people argue about, the checks that gate the merge and the merge itself, all on one rail so the order of events is never in question.
A day of a team's work in one scroll: who joined, what was said, what was uploaded, which replies are still unread, and a composer at the foot to answer any of it.
The panel on a deal, a ticket or a document that answers what happened to this: status changes and renames written by the system, sitting beside the notes people left by hand.
Something an outside service dropped into the thread, quoted in a card of its own with its source mark and its time, so it is clear that nobody in the room typed it.
A conversation runs oldest first, with the newest at the bottom and the composer under it, because that is where the reader is already looking when they reply. A monitoring or audit feed runs newest first, because the latest event is the reason anyone opened it. Pick one per surface and keep it; do not flip the order behind a filter.
Collapse them. Show the entry, the faces of the people who replied and a count, then open the replies in place when someone asks for them. Carrying an unread count on that control is what makes the collapse safe. Do not expand every thread by default: a long feed becomes unscrollable and the entries between threads get lost.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
An activity feed is the time-ordered record of what has happened to one thing: what people said about it, what the system did to it, and what got attached along the way: held together by a rail down the side so the entries read as one thread rather than a pile of notifications. The six blocks here run from whole thread pages down to the rows they are built from.
Two kinds of row live in every feed and they should not look alike. A person's row carries an avatar, a name, a time, a body and the reactions it drew. A system's row carries a glyph where the avatar would be and a single sentence naming the object it acted on. Give them the same weight and a channel of conversation reads like an audit log. Read state is the other thing to settle: marking the whole feed read the moment it opens is convenient for the badge and useless for the person, who came back to find the line they had got to.
Commits with their hashes, a diff people argue about, the checks that gate the merge and the merge itself, all on one rail so the order of events is never in question.
A day of a team's work in one scroll: who joined, what was said, what was uploaded, which replies are still unread, and a composer at the foot to answer any of it.
The panel on a deal, a ticket or a document that answers what happened to this: status changes and renames written by the system, sitting beside the notes people left by hand.
Something an outside service dropped into the thread, quoted in a card of its own with its source mark and its time, so it is clear that nobody in the room typed it.
A conversation runs oldest first, with the newest at the bottom and the composer under it, because that is where the reader is already looking when they reply. A monitoring or audit feed runs newest first, because the latest event is the reason anyone opened it. Pick one per surface and keep it; do not flip the order behind a filter.
Collapse them. Show the entry, the faces of the people who replied and a count, then open the replies in place when someone asks for them. Carrying an unread count on that control is what makes the collapse safe. Do not expand every thread by default: a long feed becomes unscrollable and the entries between threads get lost.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Today
Started on arrow-key navigation. Reactions and the composer are next.
Redlines and a quick capture:
Looped in the people who own the shortcut map.
@Mia Kwan the dark chips are on page 3. Can you check them?
Today
Started on arrow-key navigation. Reactions and the composer are next.
Redlines and a quick capture:
Redlines and a quick capture:
Looks right to me. The brand chip reads as yours at a glance.
Is the add button the same 28px as the chips?
Yes: 28 with a hairline, no fill until hover.
Looped in the people who own the shortcut map.
@Mia Kwan the dark chips are on page 3. Can you check them?
Today
Morning. Picking up the command menu today.
Redlines for the chip states are in the kit.
New
Looped in the people who own the shortcut map.
The dark chips are on page 3. Can you check them?
Today
Started on arrow-key navigation. Reactions and the composer are next.
Redlines and a quick capture:
Looped in the people who own the shortcut map.
@Mia Kwan the dark chips are on page 3. Can you check them?
Today
Started on arrow-key navigation. Reactions and the composer are next.
Redlines and a quick capture:
Redlines and a quick capture:
Looks right to me. The brand chip reads as yours at a glance.
Is the add button the same 28px as the chips?
Yes: 28 with a hairline, no fill until hover.
Looped in the people who own the shortcut map.
@Mia Kwan the dark chips are on page 3. Can you check them?
Today
Morning. Picking up the command menu today.
Redlines for the chip states are in the kit.
New
Looped in the people who own the shortcut map.
The dark chips are on page 3. Can you check them?