Skip to content

Themes & Icons

Theming

  • DGT-CUS-180 — Brand per app, using the modern model-driven app theme (logo, colors set on the app), rather than the legacy organization-wide theme — org themes are a classic-era mechanism and don't belong in new work.
  • Keep theming inside the solution so it deploys with everything else; a color set by hand in production is a value someone has to remember to reapply after every refresh.
  • Respect accessibility: sufficient contrast, and don't rely on color alone to convey state.

Icons

  • DGT-CUS-190 — Use SVG web resources for table and command-bar icons — vector scales cleanly across the Unified Interface densities where fixed-size PNGs blur. Reserve raster formats for genuine images (photos, logos with gradients).
  • Store icons as web resources in the solution and name them per the icon conventions (prfx_/Icons/Entity/... for table icons, prfx_/Icons/Button/... for command icons). Assign the table icon in the table's properties; assign button icons in the Command Bar designer.
  • Keep a consistent visual style across a project's icons (one icon set / stroke weight), and check them in both light and dark mode.

Icons are web resources — they deploy like code

Because icons are web resources, they go through the same packaging and dgtp push path as scripts. Keep the SVG sources in the repository alongside the web resource project, not only uploaded ad hoc in the maker portal.