I’m @Piotr_Wargulak Java Domain Lead, reaching out from SolDevelo - an engineering team with a long history of supporting open-source projects and helping them grow. We specialize in Java performance & monitoring, accessibility audits, and frontend modernization, and we’re excited to explore where we can bring real value to OpenELIS.
We’ve seen that the new React/Carbon-based frontend is actively evolving. Since accessibility is often easiest to address early, we’re considering preparing a short demo accessibility audit to highlight practical, actionable improvements. If that’s useful, we’d be happy to share it with the community.
Before we dive in, we’d love your input: Where do you see the biggest opportunities for outside contributors right now? Are there specific UI or performance pain points that you’d like help with? Any part of the system you feel is “important but neglected”?
Our goal is to become a dependable contributor - just as we’ve done in other OSS communities - by solving real problems that matter to real users.
Looking forward to your thoughts and guidance. Let’s figure out together where we can make the strongest impact.
I would like to share a sample accessibility audit that we conducted in March for the new React / Carbon Design UI. The sample report is available here.
And we wonder how important the accessibility of OpenELIS Web UI is for the community, and how much value fixing the accessibility issues would provide.
Hi @Piotr_Wargulak ,
Thanks so much for reaching out, and welcome to the OpenELIS community .We realy appreciate your effort on doing the accesibiliy audit report on OpenELIS.
Apologies for the delay in getting back to you , a few of our team members have been on short leave recently
I would say we have just started transitioning from JSPs to a React front end and there are still many areas of improvement needed and your efforts would be greatly aprreciated.
The main areas where contributions would be particularly valuable include:
UI performance – improving responsiveness and smoothness of the new React frontend through more efficient state management (e.g., using useMemo and other React optimization techniques) and establishing consistent UI patterns across the application.
API performance – Optimizing backend endpoints to handle workflows more efficiently.
Security – Enhancing data protection and ensuring secure handling of information across the system
Accessibility – Improving the interface to be accessible and user-friendly for everyone, including users with disabilities
Your expertise and effort will highly be appreciated.
@Moses_Mutesasira Regarding API performance, do you already have a knowledge about specific slow endpoints? It would be very interesting to know if there is an information coming from end-users, for example some web page with results loads very long, or they click some action and has to go to get a coffee to wait for result.
Otherwise, we could start with introduction of some form of performance testing, something in a direction of Gatling.
Hey @Piotr_Wargulak welcome to the openELIS Community. I am happy to navigate you through all the React.js web ui pages where suitable changes are needed, with its related REST/endpoints
@aditya Would be great, but before that I would like to understand from where the change requests are coming from.
To be fully transparent, I would like to ensure that whatever we do, the need comes from the needs of the real users. In the past SolDevelo has invested in other OSSs, where the connection of what was requested by the community and what end user really needed was weak, ultimately making the work not as impact-full as we hoped for.
Do you know what UI/UX aspects the end-users struggle the most?
Or do you know which pages, UI flows, are most comment so improving them would produce the best value?
I think it might already been answered, just want to make sure.
Since we are currently operating b2b we don’t get constant feeds backend we are moving JSP pages to React Js those needs to match the exact funcnallity which were there in JSP pages.
That would be the great work and it will be impacatfull as well
later on we want to make web rerender free using useMemos useCallBacks and Proper state management for now
