new Blog Posts as Push Notification

1 Initial Problem

Blog Posts as Mail?

no direct Interaction with content

timly manner

2 Conceptual Summary

PushNotifications had to be active and the user had to have the possibility to receive Blog Posts as Push Notification active.

Nicht im Blog Selbst zusätzlich aktivieren, weil sonst für den Nutzer nicht klar ist, warum er einige erhält und andere nciht, obwohl er aus seiner Perspektive die aktiviert hat. --> Koppeln an Benachrichtigungen

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

Personal User Settings

The Blog-Notification will be listed within the Push-Notification Provider Form

Blog Settings

At the Bottom a new Option Send Push Notifications shall be displayed. By activating the Checkbox Push-Notifications will be available for all Blogs.

The Byline will clarify the behaviour.

This Option will only appear if the Push-Notifications if Push Notifications are activated in the adminsitration.

3.3 New User Interface Concepts

None

3.4 Accessibility Implications

Due to the Usage of KS-elements no a11y implications have to be considered. The accessibility of the Push Notification itself depends on the Browser and the OS used.

4 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

4.3 Privacy

{ Personal data that will need to be stored or processed to implement this feature have to be listed here. For each date give a short explanation why it is necessary to use that date. }

4.4 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers: Stake, Sebastian [sstake]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.