- Name - Kailash Kejriwal (@Kailash360)
- Organisation - Python Software Foundation
- Sub-Organisation - EOS Design System
- Project - User Story - Frontend and UX
- Proposal - View / Download
EOS User Story allows to see the details of each story ina story page. It included the story title, description, metadata, comments, timeline status and so on. But the UX was not properly structured and implemented. Moreover, the comments section was not properly organized and the timeline section appeared a bit confusing to the users.
Revamp the story page which would involve:
- Improving the story heading and description to display the text properly
- Restructure the comments section to properly display the hierarchy of discussions
- Replace the story status section with a timeline component
- Add sections for similar stories based on author and product
- Fix the responsiveness of the story page
- mrpoved the UI/UX of the story page, restructured the comments section, added a timeline component, similar stories section and fixed the responsiveness of the story page
- PRs:
The stories can previously be viewed in a list organzied w.r.t the story status. However, it did not allow much flexibility to the users. Also, it was difficult to understand the authority of a user as every user is given equal access to all the features. Furthermore, some information about the stories like the status types were hardcoded into the frontend. It should have been fetched dynamically from the Strapi backend. The authorities like managers could not add custom status type for the story.
Improve status-based view of the story list:
- Display the stories column-wise under their status in the story list
- Add drag-and-drop feature for the stories so that their status can be updated
- Add access roles which would provide each type of user with specific rights
- Add delete feature for the stories, which should be accessible to a specific user type
- Dynamically fetched the status list
- Added feature to create custom status types
- Displayed the stories in a column-wise view based on the status, added drag-and-drop feature to update the status, and added access roles to allow specific user types with specific feature, and allowed managers to create custom status types
- PRs:
You can find a detailed description of progress and work done in weekly blogs.
I plan on contributing significantly to the project after the GSoC period. Things I plan to do:
- Further improving the code quality and working on making the codebase future proof.
- Adding the feature to reorder the status types
- Adding a deadline feature for each type of a story status
I am thankful to Google, Python Software Foundation, and EOS Design System for providing me with this excellent opportunity and the mentors, Cynthia Sanchez, Harshita Mangla, Aditya Sharma and Sundeep Chand, who guided and helped me throughout the program.
I would also like to thank my fellow GSoC contributor Hrishikesh Agarwal and the EOS Design System community for helping me during the program.