Discussions
Best practices for using SVG assets in custom Avaya experiences?
Hi team,
I am exploring visual assets for customer-facing and agent-facing experiences built around Avaya Experience Platform. For lightweight onboarding screens, campaign flows, or knowledge-base surfaces, we sometimes want simple SVG-style illustrations or icons that can stay sharp across devices.
Are there any recommended guidelines for using externally generated SVG assets in custom Avaya Experience Platform experiences, especially around file size, sanitization, accessibility text, and where those assets should be hosted?
For context, I am testing tools such as VectorArtGen AI Vector Art Generator to create SVG-ready concepts from prompts, then manually reviewing and cleaning the output before use: https://vectorartgen.com/
Would you recommend embedding optimized SVGs directly, hosting them as static assets, or using another pattern for production implementations?