-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notifications. #2009
Notifications. #2009
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We do this to keep our backlog under control, but we thank you for your contributions. |
Notifications are added and displayed in the dashboard. A last login field, and notifications table are added to the database. Notifications are passed from the database into cookies when the dashboard page is reloaded and taken from the cookies to display in the notification react component that was added. They are displayed at the top of the dashboard page. These notifications can be exited and removed from the cookie with the x button. In order to create a notification you must type directly into the database in postico. Unit tests are written. |
It would be nice to have some kind of in-app notifications for important events - upcoming downtime, release changes, etc.
What I'm envisioning is a way for administrators to create announcements and set a date for when those announcements will be displayed. Potentially we could also determine who sees these announcements - only authors, only learners, or both. Whenever a user accesses Obojobo, the system could check if their last login is earlier than the announcement window and, if so, display the announcement to them. If multiple announcements are relevant it could stack them.
This will likely require a new database table. At the moment there are no admin-only interfaces in Obojobo. While it would be nice to have one for this purpose, it may make the most sense to stick with manually plugging information into the database. See #2010.
The text was updated successfully, but these errors were encountered: