Our team would like to import our own theme to our portal without the requirement to have developers override styling using NAB.
The issues we're seeing are developers on our team have the ability to style apps inconsistently with one another, override styles that are added to the Override.css file set for global theming, and conflicts directly with any Front End development updating and maintaining the overall company branding.
Example of this is if an app developer adds a set margin or padding using the NAB (or relies on the default 16px setting), that directly conflicts with any Overrides.css styling for those set attributes in those components no matter if those attributes have an !important statement attached to them because it's being injected as inline-styles using JS which trumps any stylesheet properties. That includes using IDs over classes, too.
We're requesting the option to upload/import our own master theme on the same level as the Neptune theme available so we're appending as much (preferably all) styles for branding and theming to each app being built. This way, our users recognize this is a company portal as much as possible and allow our app developers to focus on building apps while avoid any inconsistencies along the way.
I've reached out for ideas and suggestions via email on this topic hoping there was additional documentation on this topic and the most guidance I've been given is using the available features in NAB and crickets in regards to this specific feature of importing our own theme that our company develops and maintains based on the desired UX/UI. We can do a lot in NAB, but knowing that it directly conflicts with stylesheets leaves apps at risk of inconsistencies for branding.
The issues we're seeing are developers on our team have the ability to style apps inconsistently with one another, override styles that are added to the Override.css file set for global theming, and conflicts directly with any Front End development updating and maintaining the overall company branding.
Example of this is if an app developer adds a set margin or padding using the NAB (or relies on the default 16px setting), that directly conflicts with any Overrides.css styling for those set attributes in those components no matter if those attributes have an !important statement attached to them because it's being injected as inline-styles using JS which trumps any stylesheet properties. That includes using IDs over classes, too.
We're requesting the option to upload/import our own master theme on the same level as the Neptune theme available so we're appending as much (preferably all) styles for branding and theming to each app being built. This way, our users recognize this is a company portal as much as possible and allow our app developers to focus on building apps while avoid any inconsistencies along the way.
I've reached out for ideas and suggestions via email on this topic hoping there was additional documentation on this topic and the most guidance I've been given is using the available features in NAB and crickets in regards to this specific feature of importing our own theme that our company develops and maintains based on the desired UX/UI. We can do a lot in NAB, but knowing that it directly conflicts with stylesheets leaves apps at risk of inconsistencies for branding.
Comment