Bug 27033 - Add plugin hook to add a big link in staff home page
Summary: Add plugin hook to add a big link in staff home page
Status: RESOLVED DUPLICATE of bug 27527
Alias: None
Product: Koha
Classification: Unclassified
Component: Staff interface (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Fridolin Somers
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-16 15:18 UTC by Fridolin Somers
Modified: 2022-01-08 20:51 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: Trivial patch
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Screenshot (69.22 KB, image/png)
2020-11-17 09:13 UTC, Fridolin Somers
Details
Example plugin (1.42 KB, application/octet-stream)
2020-11-17 09:14 UTC, Fridolin Somers
Details
Bug 27033: Add plugin hook to add a big link in staff home page (4.32 KB, patch)
2020-11-17 09:34 UTC, Fridolin Somers
Details | Diff | Splinter Review
Bug 27033: Add plugin hook to add a big link in staff home page (4.38 KB, patch)
2020-11-17 19:22 UTC, David Nind
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Fridolin Somers 2020-11-16 15:18:04 UTC
In staff home page we have some big links : Circulation, Patrons ...

Add plugin hook to add such a link.
Defined by a CSS class, an URL, a Font Awesome icon and a content.
Comment 1 Fridolin Somers 2020-11-17 09:13:00 UTC
Created attachment 113689 [details]
Screenshot
Comment 2 Fridolin Somers 2020-11-17 09:14:18 UTC
Created attachment 113690 [details]
Example plugin
Comment 3 Fridolin Somers 2020-11-17 09:34:33 UTC
Created attachment 113693 [details] [review]
Bug 27033: Add plugin hook to add a big link in staff home page

In staff home page we have some big links : Circulation, Patrons ...
Add plugin hook to add such a link.
Defined by a CSS class, an URL, a Font Awesome icon and a content.

In order to porpose a space where those links will show, I propose to
create 3 columns of links.
The new one will have "About" link (in order to not be empty when no
plugins) and links from plugins.

Test plan :
Use example plugin and see the big link in home page like in screenshot
Comment 4 David Nind 2020-11-17 19:22:51 UTC
Created attachment 113758 [details] [review]
Bug 27033: Add plugin hook to add a big link in staff home page

In staff home page we have some big links : Circulation, Patrons ...
Add plugin hook to add such a link.
Defined by a CSS class, an URL, a Font Awesome icon and a content.

In order to porpose a space where those links will show, I propose to
create 3 columns of links.
The new one will have "About" link (in order to not be empty when no
plugins) and links from plugins.

Test plan :
Use example plugin and see the big link in home page like in screenshot

Signed-off-by: David Nind <david@davidnind.com>
Comment 5 David Nind 2020-11-17 19:26:17 UTC
LOL! 8-) Love the plugin: Have a break, sign you out of Koha!!

Owen might want to have a look at how to make the columns more responsive. For example, when narrowing the size of you screen so that the options flow nicely into one column if the screen width gets too narrow.
Comment 6 David Cook 2020-11-17 23:27:36 UTC
I like the idea but I'm not sure about the terminology. I actually clicked on this bug because I had no idea what a "big link" would be hehe.

When I worked first-hand in libraries, we would often refer to the "Circulation module", "Cataloguing module", "Acquisitions module", "Serials module", et cetera... so I wonder if "koha_module_link" might be more accurate naming?

That said, "About Koha" and "Advanced Search" don't really seem like "modules" to me...

"top_nav_link" for the top navigation and "home_nav_link" for the home page navigation? (Or swap out "nav" for "menu" so "top_menu_link" or "home_menu_link"?

Again, I really like this idea, but I think having easily understood terminology would be a good idea too.

(At first, I thought this bug was another Fridolin Somers April 1st prank where it made links extra big or something 😅.)
Comment 7 Fridolin Somers 2020-11-18 13:05:03 UTC
Indeed the terminology could be better.

I prefer "home_nav_link".
The goal is to navigate to somewhere, module or more specific page.
We already have OPACNav preferences.

So hook named : "intranet_home_nav_link".
And maybe rename the class "biglinks-list".

Other votes ?
Comment 8 Fridolin Somers 2020-11-18 13:07:24 UTC
(In reply to David Nind from comment #5)
> LOL! 8-) Love the plugin: Have a break, sign you out of Koha!!
> 
> Owen might want to have a look at how to make the columns more responsive.
> For example, when narrowing the size of you screen so that the options flow
> nicely into one column if the screen width gets too narrow.

Those links more responsive would be great.
But no idea how to do it 😊
Comment 9 David Cook 2020-11-19 03:08:21 UTC
(In reply to Fridolin Somers from comment #7)
> Indeed the terminology could be better.
> 
> I prefer "home_nav_link".
> The goal is to navigate to somewhere, module or more specific page.
> We already have OPACNav preferences.
> 
> So hook named : "intranet_home_nav_link".
> And maybe rename the class "biglinks-list".
> 
> Other votes ?

Sounds good to me. Curious to hear what others think.
Comment 10 Jonathan Druart 2022-01-07 09:27:58 UTC
Shouldn't this be actually replaced with bug 15326? Aleisha rewrote it to add a new "page" type of additional contents.
It would be a core feature, and plugins could simply add new contents by adding rows to the DB tables.
Comment 11 Fridolin Somers 2022-01-08 01:09:05 UTC
Sure, lets close

*** This bug has been marked as a duplicate of bug 27527 ***
Comment 12 Katrin Fischer 2022-01-08 20:51:01 UTC
I am not sure if the CMS is solving this; I think this was to add new module style links to the start page? And possibly add them to the 'More' menu as well? I think it could still be done with the js hook if needed.