Integrate "What's New" Notifications/Updates

[philippotto]

URL of deployed dev instance (used for testing):

• https://olvy.webknossos.xyz

Steps to test:

• open dev instance (isDemo is enabled currently)
• click on "What's New" to see a modal with wK news
• publish some new news on olvy (hit me up for credentials)
• reload wk and expect a red dot on the "What's New" button
• open the modal again --> dot should disappear
• reload page
• dot should be gone

Issues:

• fixes Integrate "What's New" UI #5652

---

• Updated (unreleased) changelog
• Updated (unreleased) migration guide if applicable
• Updated documentation if applicable
• Adapted wk-connect if datastore API changes
• Needs datastore update after deployment
• Ready for review

[philippotto]

I integrated the feedback I got and now the lastOpenedReleasesTimestamp is stored in the database. Also, the notification indicator is integrated into the avatar. It looks like this:

@fm3 Please have a look at the back-end code I added. I'm not sure whether I adhered to the existing practices (e.g., the parameter ordering was not very clear to me).

[philippotto]

@fm3 Also maybe can you help with writing a migration which adds the lastOpenedReleasesTimestamp column (could default to lastActivity or to the execution time of the migration if that's necessary)? Happy to have a call about it 🤙

[fm3]

@philippotto I pushed a version that moves this timestamp to the multiUser’s novelUserExperienceInfos. Note that I also changed the code slightly to allow for this field to be missing. This way users that never clicked the button will see all that happened since their registration (which is similar to defaulting to the time of the evolution, as we will start publishing entries only then). This way we don’t need a migration or any other back-end changes. Do you agree that this covers the use cases?

[philippotto]

@philippotto I pushed a version that moves this timestamp to the multiUser’s novelUserExperienceInfos. Note that I also changed the code slightly to allow for this field to be missing. This way users that never clicked the button will see all that happened since their registration (which is similar to defaulting to the time of the evolution, as we will start publishing entries only then). This way we don’t need a migration or any other back-end changes. Do you agree that this covers the use cases?

Thank you for doing this! Somehow I missed that this will be a front-end-only code change then 🤦 But glad to see that it turned out that way 👍