Blockers in Custom UI to UI Kit 2 transition

Forge
,
1

Hello !

I wanted to give a try on translating our Custom UI Confluence macro into a UI Kit 2 Confluence macro.

Here are some comments about the blocking points when transitioning to UI Kit 2 from Custom UI.

No SVG support
There is no support of SVG graphics in UI Kit 2. The only workaround we found is to inline the SVG as data:image/svg+xml;

It would be great to be able to use SVGs as components, like in a regular React application.

Poor text styling
Typography is a fundamental component of good software UI.

With UI Kit 2, styling is really poor:

  • Using Heading
  • Using Text variations (Code, Strike, Em, Strong)
  • Using a box with an xcss defining the text color

There is no way to define font size or weight out of using Heading or Text/Strong.

No animations
In our Custom UI application we display a Box which can expand or collapse.

We perform an animation using CSS transform and transition. Those properties are not allowed in xcss, preventing any animation.

Conclusion
We really want to use UI Kit 2, but these points are really downgrading the quality of the software we can release with this technology.

Is there a chance UI Kit 2 evolves on the short term to be able to fix the issues mentioned here ?

6 Likes