Created SIEM integration frameworks for engineering based on design system components
For this project we needed to create a way for engineering to build integration experiences for our users, without needing custom designs for every variation of integration.
There were 2 problems to solve. Our form components were not designed with this use case in mind and required a re-evaluation. As well, there were unique flows based on different setting configurations in the API details that would lead to infinite design work if we were to create unique experiences for each API integration. As well, all integrations are different as data is being pulled from external sources so we do not have a way to change the data, apart from its styling and positioning on the page.
Looking at this these API details from Synqly I worked with engineering to build out a structure of what needed to appear on a page in order for these details to be filed out by our users.
I used this as a template to build a framework on how to structure form elements based on type of data requested by the API.
Using the established component library I worked with the Design System team to ensure we were using standard components and look for places where the components did not work as intended in our use case or where there was not a component which accurately solved the form data element in this context., since our standard form components are based for non linear interactions or form building experiences.
Once we had a framework established and components updated we were able to create unique integration experiences with out the need of unique designs from the design team for every third party API, or branching configurations within those API settings.