Bug 10958 - No need for home link on home page
Summary: No need for home link on home page
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Templates (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-26 18:59 UTC by Nicole C. Engard
Modified: 2023-11-16 21:52 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2013-09-26 18:59:19 UTC
On the OPAC there is a Home link on the top left it makes no sense and a lot of libraries are asking to have it removed, but if I remove it with JS I lose the breadcrumbs on every page. Can we get rid of the home link on the home page?
Comment 1 Owen Leonard 2013-09-26 19:17:49 UTC
I'm not rejecting the idea of this bug, but why not make your JS more specific so that it only targets the home page?

$("#opac-main #breadcrumbs").hide();
Comment 2 Nicole C. Engard 2013-10-03 15:55:57 UTC
Well that works for now :) But I do think that link should be removed for real (not just with js).

Nicole
Comment 3 Aleisha Amohia 2015-12-22 01:41:42 UTC
What if we replaced the Home link with a link the summary page (opac-user.pl) ?
Comment 4 Owen Leonard 2015-12-22 13:13:38 UTC
I would prefer a solution which removed the breadcrumbs from the home page to one which changed the expected structure of the bookmarks link. I think it's good to let users make assumptions about what they're going to find in an element like breadcrumbs which might be familiar to them from other sites.
Comment 5 Marc Véron 2015-12-22 14:47:27 UTC
(In reply to Owen Leonard from comment #4)
> I would prefer a solution which removed the breadcrumbs from the home page
(...)

+1 for removing the breadcrumbs
Comment 6 Katrin Fischer 2015-12-27 20:36:49 UTC
Could one not just use CSS to do this?
Comment 7 Aleisha Amohia 2016-07-07 22:36:16 UTC
why can we not just remove the link from the tt file?
Comment 8 Katrin Fischer 2019-05-05 10:53:11 UTC
I like the consistency of the Home link on the start page. Whatever the styling it makes clear that this is the start page.
Comment 9 Katrin Fischer 2023-07-08 21:30:40 UTC
With the staff interface redesign we still have the home icon on the start page, same for the OPAC. 
Can we agree to keep or remove?
Comment 10 Lucas Gass 2023-11-15 21:05:19 UTC
(In reply to Katrin Fischer from comment #9)
> With the staff interface redesign we still have the home icon on the start
> page, same for the OPAC. 
> Can we agree to keep or remove?

I vote for remove. I always have to hide this with CSS for new instances. Breadcrumbs are a trail back to the homepage and if you are already there I find them useless, redundant, and confusing.
Comment 11 David Cook 2023-11-15 23:17:09 UTC
I've never had any complaints about this from any libraries, and personally I like having the "Home" breadcrumb on the home page. 

Looking around online but not finding anything on this exact topic. 

I found oregon.gov used in an article on usability, and their Oregon Health Authority section is an example where the breadcrumb isn't shown on some home/landing pages, but I think it looks terrible. Although I think it's terrible because the banner is smaller on pages with the breadcrumb and bigger on pages without it, which makes for an inconsistent look and feel. 

I think my libraries would complain about content displaying higher on the home page without the breadcrumb and lower on pages with the breadcrumbs, but maybe I'm wrong. Maybe they wouldn't care either way. 

But I don't think we can 100% remove a visual element that's been present for so long without a way to bring it back. 

Overall, I think this one might just come down to preference, so probably best to add a system preference.
Comment 12 Lucas Gass 2023-11-15 23:22:26 UTC
> Overall, I think this one might just come down to preference, so probably
> best to add a system preference.

You're right, it comes down to preference. I am not sure if this even warrants another new system preference since one can just add to OPACUserCSS:

#opac-main .breadcrumbs {
    display: none;
}


Maybe a sys pref is overkill and we should just "RESOLVE - WONT FIX" this one?
Comment 13 David Cook 2023-11-16 00:17:37 UTC
(In reply to Lucas Gass from comment #12)
> You're right, it comes down to preference. I am not sure if this even
> warrants another new system preference since one can just add to OPACUserCSS:
> 
> #opac-main .breadcrumbs {
>     display: none;
> }
> 
> 
> Maybe a sys pref is overkill and we should just "RESOLVE - WONT FIX" this
> one?

Part of me thinks a syspref is overkill, but it must be annoying having to add that to each new instance, so I suppose I'd like to make everyone happy. 

I suppose I always add the following to OPACUserCSS for every new instance, so maybe we all have different bits and bobs we always add. 

#logo {
  display: none;
}

Previously, I've suggested adding a profile for koha-create that could setup sysprefs in a vendor-specific way. That could be an interesting alternative too...
Comment 14 Katrin Fischer 2023-11-16 21:52:09 UTC
We haven't been asked to change this so far. What about accessibility? Would it be useful to keep it for orientation?