The conversation skeleton needs some styling adjustments to enhance its visual presentation and improve user experience. Currently, it lacks consistency and readability in certain areas.
Expected Outcome:
A polished and visually appealing conversation skeleton that provides a seamless experience for users while waiting for content to load.
we need to develop an API endpoint that retrieves all conversations associated with a particular user. Through it, the clients will be able to fetch the complete history of conversations for a specified user, for example, viewing past messages and analyzing user engagement.
Expected Outcome:
An API endpoint that retrieves and delivers all conversations related to a specific user, enabling advanced user interaction analytics.
This will improve the organization of conversations within the application. Users will benefit from the ability to assign meaningful titles to their conversations and efficiently perform common tasks, such as creating new conversations or removing outdated ones.
Whenever the user creates an account, the system does not take them back to the login page to log in with their account, which does not allow the user to know that their account is created.
Adding CSS styling to the 404 and 500 error pages will improve the user experience when encountering these error states. Users will be presented with visually appealing error pages that align with the design of the rest of the application.
By integrating toasters, or notification pop-ups, into our frontend interface, we can dynamically alert users to any errors or validation issues returned from the backend during password validation or other form submissions.
The login, register, and welcome pages currently lack a skeleton layout, which is essential for providing users with visual feedback while the content is loading. Implementing a skeleton layout for these pages will enhance the user experience by indicating that the page is actively loading and reducing perceived load times.
Due to complex dependencies that llama.cpp uses , normal openjdk image did not work out, we need to use alpine or more basic image and install our dependencies and create new image.
A Dockerized version of the application that simplifies deployment, enhances scalability, and ensures consistency in different deployment environments.