Introduction

Storyfeed is an implementation of the activity feed pattern for Laravel. Activities are recorded explicitly, read back as a timeline or an aggregated feed, and serialized following W3C Activity Streams 2.0.

Storyfeed::record(ActivityVerb::Upload, object: $document, actor: $user, target: $project);

Recorded in a burst, activities aggregate the way feeds are expected to:

Bob, Sally, and 3 others uploaded files to Project X.

How it works

• You record explicitly. Storyfeed::record() from an action, observer, or event listener — you choose what makes the feed. No model spying, no magic.
• Reads never touch your domain tables. Each entity is snapshotted at publish time, so a feed page is fast regardless of how many models it spans.
• Aggregation happens behind the scenes. Activities are grouped at write time along multiple axes; the read picks the best one.
• The payload is a versioned contract. Every item ships its own headline template, icon, and linked entities. Adding a new activity type never requires a frontend change.

License

Storyfeed is MIT, and everything MIT today stays MIT. The core is complete on its own; paid companions like storyfeed/ui add convenience on top and never take anything away. Building your own renderer against the payload contract is expected — the quickstart ends with one in plain Blade.

Next

Install the package, then build your first feed in about ten minutes.