the link to open a support modal is currently hardcoded into the pano/components/app_top_nav partial, but the implementation is application-specific. kinda lame, but up for changing and making configurable as part of app_top_nav call signature, especially if you need it to change for manager view.
I haven't considered the proper way to support the custom colors and vendor logo in the top nav that you'll need in Engage manager view. You could do some of those changes just with the ability to add a CSS class to the top nav via the helper, but you'll also need to be able to pass a custom logo and url for when the logo is clicked.
some font families have changed for certain heading sizes. I don't think there are any necessary changes in the Engage codebase, and you probably already have the necessary font files in public/fonts, but YMMV.
@mmlindeboom so the relevant things here, if you merge this into 4-0, are:
you'll need to refactor your top navs in the app and manager view areas like so: https://github.com/techvalidate/cx/blob/cdf6f9302ef175419f5e7c958c2a257bf289ab37/app/views/app/app/_top_nav.haml
you'll need to override the top nav css in Engage to inject the Engage logo, like so: https://github.com/techvalidate/cx/blob/cdf6f9302ef175419f5e7c958c2a257bf289ab37/app/assets/stylesheets/app/_top_nav.sass
I haven't considered the proper way to support the custom colors and vendor logo in the top nav that you'll need in Engage manager view. You could do some of those changes just with the ability to add a CSS class to the top nav via the helper, but you'll also need to be able to pass a custom logo and url for when the logo is clicked.
some font families have changed for certain heading sizes. I don't think there are any necessary changes in the Engage codebase, and you probably already have the necessary font files in public/fonts, but YMMV.