Support configuring card/widget header icon on dashboard page
NetBox version
v3.5.4
Feature type
New functionality
Proposed functionality
Related to https://github.com/netbox-community/netbox/pull/12664/commits/7d566837b6700acc904711952f50606a4ae2fec1
Allow for dashboard cards to have an icon added.
Use case
The dashboard purpose is to allow users the opportunity to customize this view to include only the information most relevant to them. Adding visual cues as to the content of the widgets/cards makes it even better (and prettier).
Database changes
None
External dependencies
None
I have several widget with mixed content. How will the header icon be defined? By selector? Unicode is not enough?
P.S. Text shadow or more contrast text colors for some header colors will be much more appreciated imho:
Hi @stavr666, My plan was to define icon names from Material Design Icons.
Something like that:
<h6 class="card-header text-center">
{% if widget.icon_name %}<i class="mdi mdi-{{ widget.icon_name }}"></i>{% endif %}
<span class="ms-1">{{ widget.title }}</span>
</h6>
Nothing would prevent you from using your method as well.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.
https://github.com/netbox-community/netbox/issues/12128 is probably blocking this
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.
@jsenecal now that #12128 is completed, would you like to take a fresh look at this issue?
It really depends on @jeremystretch tbh @jeffgdotorg
I've not been involved with this FR at all.
Closing this out at stale as there's been no further discussion.