Monorepo for Tangled tangled.org
761
fork

Configure Feed

Select the types of activity you want to include in your feed.

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 <eti@eti.tf>

authored by

eti and committed by
Tangled
33382a02 799a850e

+1 -1
+1 -1
appview/pages/templates/layouts/fragments/topbar.html
··· 27 27 28 28 {{ define "newButton" }} 29 29 <details class="relative inline-block text-left nav-dropdown"> 30 - <summary class="btn-create py-0 cursor-pointer list-none flex items-center gap-2"> 30 + <summary class="btn py-0 cursor-pointer list-none flex items-center gap-2"> 31 31 {{ i "plus" "w-4 h-4" }} <span class="hidden md:inline">new</span> 32 32 </summary> 33 33 <div class="absolute flex flex-col right-0 mt-3 p-4 rounded w-48 bg-white dark:bg-gray-800 dark:text-white border border-gray-200 dark:border-gray-700">