activist
activist copied to clipboard
Add event favoriting/bookmarking feature for users
Terms
- [x] I have searched open and closed feature requests
- [x] I agree to follow activist's Code of Conduct
Description
Feature Request: Event Favoriting/Bookmarking Problem: Users currently have no way to save or bookmark events they're interested in for later reference. This makes it difficult to keep track of events they want to attend or follow up on.
Proposed Solution: Add a favoriting/bookmarking system that allows users to:
Save events to a personal favorites list Easily access their bookmarked events Toggle favorite status from event cards/pages Implementation Details:
Backend:
New model: EventFavorite with user, event, and created_at fields
Endpoints:
POST /events/favorites - Add event to favorites
DELETE /events/favorites - Remove event from favorites
GET /events/favorites - Get user's favorite events
Frontend:
Add favoriteEvents: string[] to event store state New actions: toggleFavorite(eventId), fetchFavorites() Heart icon button on event cards that toggles favorite status Optional: "My Favorites" page to view all bookmarked events User Stories:
As a user, I want to bookmark interesting events so I can easily find them later As a user, I want to see a visual indicator of which events I've favorited As a user, I want to view all my bookmarked events in one place
Acceptance Criteria: Users can click a heart/bookmark icon to favorite an event Favorite status is visually indicated on event cards Favorite status persists across sessions Users can unfavorite events API endpoints handle authentication properly Frontend gracefully handles API errors Additional Context: This is a foundational feature that enhances user engagement and provides building blocks for future features like personalized recommendations or email notifications for favorited events.
@andrewtavis
Contribution
No response
Hey @monu808! Glad to have this issue :) The general idea that we have here is that a user could "support" entities like organizations, groups and events, and then we'd have a star functionality for content like resources. Does this sound sensible to you? From there, we'll need to do a check to see how much of this has been done in the backend already. We need to update the search components and the entity pages to allow the user to support them, and then from there we need to have a place where they can see what they support per entity type.
Hey @monu808! Glad to have this issue :) The general idea that we have here is that a user could "support" entities like organizations, groups and events, and then we'd have a star functionality for content like resources. Does this sound sensible to you? From there, we'll need to do a check to see how much of this has been done in the backend already. We need to update the search components and the entity pages to allow the user to support them, and then from there we need to have a place where they can see what they support per entity type.
Thanks for the clarification — that makes sense! 👍 Supporting entities (orgs, groups, events) and starring content feels like a clean separation. I’ll need to check the current backend setup and then scope out the changes needed for the entity pages and search components to reflect support status.
Would be great for you to check that out, @monu808! Appreciate the feedback on the current approach as well 😊 Please let us know what you find out and we can plan the next steps from there! :)
Hi @andrewtavis
I’ve reviewed this issue and I’m really excited to work on it! I’d like to request assignment so I can start contributing. I’ll make sure to follow the project’s guidelines and maintain code quality.
I’m preparing for GSoC 2026 and eager to learn while contributing meaningfully to this project. 🙏
Best, Dharmendra Solanki
Hey @ProgrammingPirates 👋 Would you have interest in looking into https://github.com/activist-org/activist/issues/1572? This issue is a bit larger and I don't think that we have capacity to jump into it right now. Happy to suggest other issues!