Create routes and components that allow the user to access any student, section, session, exam, etc.
Add a search bar to search by name, sorting options, and filtering options.
Create components/pages for a single section, session, exam, or other content.
Add functionality to those pages (delete, edit, add fee to included/related students, and other actions) to allow for better and faster interaction with the underlying data. This creates a much better UX.
Add similar functionality and actions to the getAll/search page (i.e. delete all found/filtered content, add fees to all found students, etc.)
No need to refactor older components, these can coexist. Only navigation and such will need to be added
This is a different approach from the purely form-based interaction with the data, slightly more work but visibly more user-friendly.
Create routes and components that allow the user to access any student, section, session, exam, etc.
Add a search bar to search by name, sorting options, and filtering options.
Create components/pages for a single section, session, exam, or other content.
Add functionality to those pages (delete, edit, add fee to included/related students, and other actions) to allow for better and faster interaction with the underlying data. This creates a much better UX.
Add similar functionality and actions to the getAll/search page (i.e. delete all found/filtered content, add fees to all found students, etc.)
No need to refactor older components, these can coexist. Only navigation and such will need to be added
This is a different approach from the purely form-based interaction with the data, slightly more work but visibly more user-friendly.