From 33382a02c77ac58a22a44f09951d9c50e2792ec0 Mon Sep 17 00:00:00 2001 From: eti Date: Mon, 20 Apr 2026 15:42:41 +0000 Subject: [PATCH] appview/topbar: switch "+ new" button from primary to secondary having a primary call to action always present in the nav bar was creating issues with other call to actions at a hierarchical level this change prevents buttons clashing against each other because of their level of importance *As a rule of thumb, the main call to action on a page should be heaviest in weight when compared to other buttons and/or links. All other action items should appear secondary in terms of color, placement, shape, and overall weight allocation.* refs: - https://www.smashingmagazine.com/2009/10/call-to-action-buttons-examples-and-best-practices/#offer-secondary-alternative-actions - https://uxmag.com/articles/usability-tip-one-main-call-to-action-item-per-task#:~:text=As%20a%20rule,to%20move%20forward. Signed-off-by: eti --- appview/pages/templates/layouts/fragments/topbar.html | 2 +- 1 file(s) changed, 1 insertion(s)(+), 1 deletion(s)(-) diff --git a/appview/pages/templates/layouts/fragments/topbar.html b/appview/pages/templates/layouts/fragments/topbar.html --- a/appview/pages/templates/layouts/fragments/topbar.html +++ b/appview/pages/templates/layouts/fragments/topbar.html @@ -27,7 +27,7 @@ {{ end }} {{ define "newButton" }}
- + {{ i "plus" "w-4 h-4" }}
-- tangled.sh