Enhance usability of "Visit the primary node" links on secondary nodes
When you're on a page on the secondary, e.g. an issue, and you'd like to comment on that issue, you cannot easily visit the exact same page on the primary node. You'll have to press the "Go to primary node" button in the top navigation to visit the primary, and there browse to the same issue again.
The current "primary node" message and related link does not provide value to users exploring the secondary node UI.
If I experience a read-only error, I want to get direct access provided to this actual page on the primary instance.
We changing the link should happen (partly) on the frontend, because the
# anchor link to a specific comment should be retained.
We're changing the link in the broadcast message to the matching page in the primary node but keeping the icon link in the nav bar directed at the primary node homepage.
We're introducing a small change to the broadcast message (marked with italics): "You are on a secondary, read-only Geo node. If you want to make changes you must visit this page on the primary node."
Keep in mind that the position of the broadcast message may change to being on top of the navbar once we start to look at standardising them.
We're also changing the styling of the broadcast message so it doesn't look like an alert but more like conveniently-placed helpful information instead.
Style changes introduced:
- bacgkround color is
$blue-100(works well with all nav bar colors)
- text color is our primary style
- remove the link underlining and change the color to our anchor text color