-
-
Notifications
You must be signed in to change notification settings - Fork 760
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorganize Profile Section in Web Module for Improved Usability #781
Comments
I am new to the project and would like to work on this issue. |
@prbhtkumr Claim |
Hey @vikas-chaudhary-2802 Currently, there's an ongoing code refactoring initiative in progress, and I would like to align my efforts with this issue as I'm relatively new to the project and it offers a great learning opportunity. I hope you understand. However, there are plenty of other exciting areas within the project where your contributions would be highly valuable. I encourage you to explore other open issues or functionalities that interest you. If you have any questions or need assistance finding another area to contribute, feel free to ask. I look forward to seeing your contributions to the project! |
There is indeed some refactoring going on. As this improvement was proposed by @prbhtkumr it is only fair for him to work on it in own fork. For you @vikas-chaudhary-2802 I suggest to have a look at the the pagination feature in crawler results #805 |
Issue Summary:
The current profile section in the web module appears cluttered with multiple protocols and products, making it challenging for users to navigate and select profiles efficiently. This issue proposes reorganizing the profile section to enhance user experience.
Proposed Changes:
Separate Section for Profiles:
Introduce a separate section for profiles to declutter the existing profile selection interface.
Improved Categorization:
Group profiles based on protocols and products to make it more intuitive for users.
Screenshot:
Implementation Plan:
Benefits:
The text was updated successfully, but these errors were encountered: