diff --git a/mobile/templates/mobile/_notification_row.html b/mobile/templates/mobile/_notification_row.html new file mode 100644 index 0000000..b9a2116 --- /dev/null +++ b/mobile/templates/mobile/_notification_row.html @@ -0,0 +1,25 @@ +{% load i18n %} +{% comment %} + One M7 notification row -- included from notifications.html once per day + bucket. Expects ``row`` ({notification, news_item}) in scope. The whole + row is the tap target (a submit button styled full-width, since a POST + form can't wrap another form/link) -- tapping always marks it read, and + also navigates to the linked News item when there is one (see + NotificationsView.post). A club-coloured bar marks it unread, same + treatment as management/templates/management/home.html's own + notifications card. +{% endcomment %} +
diff --git a/mobile/templates/mobile/notifications.html b/mobile/templates/mobile/notifications.html new file mode 100644 index 0000000..550ab3a --- /dev/null +++ b/mobile/templates/mobile/notifications.html @@ -0,0 +1,75 @@ +{% extends "mobile/base.html" %} +{% load i18n %} + +{% comment %} + M7 -- design_handoff_rosterchief_platform/README.md's M7 section ("Inbox"). + See NotificationsView's own docstring for why this is a flat, generic, + day-grouped list rather than the mockup's per-type cards: the underlying + model has no type/category field, and nothing but news publishing creates + a notification yet. Scoped to every managed_people, not just scope_person + -- same as unread_notification_count itself (mobile/mixins.py). +{% endcomment %} + +{% block content %} + {% if not managed_people %} +{% trans "No one to show yet" %}
+{% trans "Once you're linked to a member record, their notifications will show up here." %}
+{% trans "Nothing here yet." %}
+