Future Ideas v1 — organized by product area
This is an attempt to organize all the ideas floating around the docs, roadmap, and issues into one place. This isn't where to prioritize things, it's just to see the "big picture" of everything we're thinking about.
Groups
Add "Create Group" navigation for easier access (#498)
Special group that every user is automagically member (#315)
- Use case: welcome group, or when user must get some kind of info (even maybe legally)
- Implementation: Add a group property (on the groups table) something like is_mandatory and create an artisan scheduled command to add any user to this group which is not yet added.
Users
Allow user to set correct timezone + autodetect by default (#370)
New role: External contributor (#449)
New role: Read-only member (#449)
Discussions
Allow a group to publish public content.
Allow Fediverse users to follow group discussions. (#271)
Store attachments in a separate directory in files, called "discussions" for example
Fix the "scroll to latest unread item" functionality on discussion list
Provide a nice navigation for longer discussions (ex: Flarum & Discourse) in a simple way
Add inline image display.
Show last comment instead of discussion body on discussion short template (#353)
External requests (from outside a group)
- Allow people outside a closed group to contact the group by web form, email or Fediverse account (real inbox for groups).
- When an “external” person contacts a group, a new discussion is created and labeled as “from an external person”
- Group can discuss as usual and the whole discussion is sent to the external person as well
- Example: Basecamp external client feature
- Extend users model & database to allow external users to be stored using their Fediverse handle instead of email
- Add new “external” role to group members
- Nice to have: Users authenticate with Fediverse account
Files
Upload discussion attachments to a separate folder (#441).
Provide Webdav access to files per group. For connected users, show all their groups, each in a separate folder when using webdav
Provide WOPI interface to allow integration with online office tools. Collabora Online, OnlyOffice, and Office seems to use this not well known standard
Allow drag-and-drop file upload
Preview more file types on file embed and show view
Store group files using the same structure as folders in group to allow easier sync (#546)
- Currently: group/(group id)/files/(file id)/(content). Instead, use same way as filemanager of groups, including directories.
Notifications
Add push notifications (#333)
- AgoraKit is a progressive web app (PWA) with 40% of users on small screen. Users expect to receive real-time notifications.
- Native notifications using web push notifications
- UI to configure notifications per group, per user (same as email notifications)
Add "welcome" email (#366)
- configurable, on group creation , on user subscription, localized
- "onboarding journey": right after creation/registration, one week after, one month after
Add notifications per channel, per group, per user with nice defaults and simple checkboxes.
- "get an email / webpush when an event is created in group xyz"
- "When someone joins / leaves / etc. the group xyz"
Allow notifications to be grouped in the summary email
Add notification types for group admins
Notify user by mail when membership is accepted (closed groups) (#219)
Notify group admin when an invited user join a group (#258)
When user is added to a group (#265)
- add the group description to email sent
- allow group admin to set a custom message to invited / added users
Calendar
Public calendar of events (#398)
- Allowing groups to publish events publicly is an important tool for communicating outside the group.
- Allow groups to publish events to a publicly available calendar.
- Support iCal feeds.
Allow Fediverse users to follow of public group events. (#271)
Link discussions to events (#538)
Provide caldav access
Recurring event support (#639)
Propose an event (#537)
Documents
Users asked the ability to create and edit documents (if possible collaboratively). Two options :
Use existing Onlyoffice / Collabora / office tools (#161)
- Allow to edit files (see WOPI/Webdav support idea for files)
Create a new document content type
- Allow users to create and edit documents inside the files tab.
- Search and implement a lightweight online editor (https://www.blocknotejs.org/ & https://milkdown.dev/ looks both interesting, based on prosemirror and using the collaboration engine (websocket server needed))
Maps
Add maps where there is geocoded info (e.g. actions, profiles, groups) (#170)
Proximity searching to allow searching nearby groups (#195, discuss)
Framework
Simplify install using Phing-based build to provide a file archive users can upload directly to install AgoraKit on shared hosting
These are areas we should ALWAYS be improving, so they don't need to be in a "to do" list:
Accessibility
Documentation
Localization
Interoperability
Philippe and I recently collaborated on a list of priorities for applying for an NLNet grant. It has three equal focuses that build on each other:
Overall, we hope this achieves the following:
I'm laying out which existing roadmap items this covers with issue numbers and I'll make some issues for discussing the newer feature ideas to refine the scope of them. Notes, requests, and feedback welcome!
Improvements
Iterations and additions to existing feature sets to make the platform more broadly appealing.
Badges
Open-ended system for recognition based on time invested and group experiences.
Behaviors to recognize:
Considerations for a new badge:
Onboarding
Improve the experience for new members.
Collaborative Moderation
Experiment with new workflows and transparency. We'll want to pick a subset and focus because this could get out of hand easily.
Potential actions:
Support required:
I am slowly assembling this into a Project on GitHub: https://github.com/orgs/agorakit/projects/1/views/1