Currently navigating to a direct resource url will still bring up a back button which simply sends to window.history.back(), i.e. if you followed a link from another website it sends you back to the site, not further back within a navigation stack on the resources site. Therefore would be good to either track current navigation stack and send back appropriately, or hard-code back buttons via path (complicated as typcially /resource/xyz comes from resource clicked in /list/abc)
Currently navigating to a direct resource url will still bring up a back button which simply sends to window.history.back(), i.e. if you followed a link from another website it sends you back to the site, not further back within a navigation stack on the resources site. Therefore would be good to either track current navigation stack and send back appropriately, or hard-code back buttons via path (complicated as typcially /resource/xyz comes from resource clicked in /list/abc)