Communities have become very good at creating content.
Announcements. Photos. Discussions. Polls. Updates.
But there is one thing a feed has never been particularly good at:
Getting people to show up.
A feed tells you what is happening.
A calendar tells you when to participate.
For communities built around real-world or recurring activities, that difference matters.
A feed is designed for discovery
Open a typical community feed and you'll see a stream of information.
New post.
Old post.
Announcement.
Comment.
Another announcement.
The newest information naturally pushes older information down.
That's exactly what a feed is supposed to do.
But events don't work that way.
If your community's monthly meetup is on September 12, it doesn't become less important because someone posted something new today.
Time doesn't work like a feed.
Communities run on participation
A healthy community isn't just people reading things.
It's people doing things together.
A workshop.
A meetup.
A weekly class.
A networking session.
A club activity.
A discussion.
A community gathering.
These activities need a shared understanding of time.
That's why communities need a calendar.
A calendar answers a different question
A feed asks:
What's new?
A calendar asks:
What's happening next?
That second question is often more useful when the goal is participation.
Someone joining a community shouldn't have to scroll through hundreds of posts to discover what they can attend next week.
They should be able to open the schedule and immediately understand:
What's happening → when → where → what can I join?
The calendar can become the community's front door
Imagine a community calendar where members can:
Now the calendar isn't just displaying information.
It is helping the community coordinate itself.
From content to coordination
This is an important shift.
A feed is primarily a communication layer.
A calendar is a coordination layer.
Communities need both.
The feed can tell members that something interesting happened.
The calendar can help them decide whether they want to be there next time.
Why recurring schedules matter
Many communities aren't built around one annual event.
They have ongoing activities:
Weekly meetups.
Monthly gatherings.
Regular workshops.
Recurring classes.
Multiple groups with different schedules.
Managing these through scattered posts, messages and spreadsheets quickly becomes difficult.
A shared, structured schedule gives everyone a common source of truth.
Where Fragment fits
Fragment is designed around group schedules and recurring events.
Organisers can create schedules that participants can follow and interact with, while keeping event information, bookings and updates connected.
Explore Fragment
A community doesn't need another place for people to endlessly scroll.
Sometimes it needs something much simpler:
A place that tells everyone where they need to be, and when.