-
Notifications
You must be signed in to change notification settings - Fork 0
"Bird icon" on contact page #83
Comments
I had a quick look at this, and unfortunately this is not as easy as one might expect: The "bird icon" is a wagtail feature. However, the contact list is not a wagtail page, it is a django page. Of course, one might put a little "bird" image into that corner with a target link to the contact edit page. But to mimic the wagtail function, we'd need to animate-open a submenu , maybe only showing available options, instead of sending unprivileged users to pages which then just show error messages. And in wagtail this is not implemented with an image, but with a glyph in a web downloadable font which is put into place by some impressive javascript and css magic. Doable, but it would take more time than currently is available. This will stay unresolved for a while. Maybe the user can just bookmark https://intranet.molgen.mpg.de/admin/personal/contact/ for now or log in at https://intranet.molgen.mpg.de/ and navigate via "Kontakte" - "Personen" |
I would opt for the "put a little bird image in the corner and send unprivileged users to an error page" as a quicker and simpler (?) option. Bookmarking stuff and navigating via other pages is something that the users I encountered are not really happy with. The little bird could and should look different in order to subtly convey the idea that things are different on that page compared to the regular wagtail pages ... would that be doable? |
The "bird icon" could also be static on the very bottom of the list for the time being. I could imagine a simple link "Add contact" at the bottom. |
The wish has surprisingly been fulfilled as a side effect of the Wagtail update in #88. |
Is there a way to add the "bird icon" to the contact list? Its absence is not really expected (at least according to the feedback I got): When people want to add a contact, navigating to the contact page first seems to one of the standard routes they take ....
Best,
Martin
The text was updated successfully, but these errors were encountered: