SvelteKit Portal
Budget: €250 – €750 EUR
I need an estimate for the following project.
It is a portal which must be developed in SvelteKit 1.0. The technology to be used can be TypeScript or JavaScript. At the styling level, you can use a library such as Tailwind or similar.
The portal must connect to a Restful API (VTiger) which we have hosted on a server. As for the API documentation, we already have a POSTMAN file with all the calls and examples.
Regarding the functionality of the portal, the following are the points to be taken into account.
https://github.com/TailAdmin/tailadmin-free-tailwind-dashboard-template
1. Access through login and password.
2. Once we have accessed, it should show a screen which will have a header, sidebar, main and footer (attached an example of the concept).
3. In the header there should be a logo on the left side and a user icon (avatar) with a menu showing the following options (Edit profile and logout). By clicking on the "profile" option, the system should load the profile data in the main section. The data to be displayed are (Name and email). If you click on logout, the system should exit and display the login window (and delete the API access token that was initially saved).
4. In the sidebar there should be the following options (Home and Tickets). The default option should be Home and the main should only show a title indicating "Main Page". On the other hand, the sidebar must allow to contract to give more amplitude on the screen.
5. When clicking on the Tickets option, the system should display a table in the main section with the tickets obtained from the API. Since the API pages every 100 records, the table should have a page indicator based on the total number of records (this data is obtained from the API call itself).
7. The columns that the table should display are (TicketNum, Account, Date, Title and status).Finally, each record should have an icon in the last column to download a document which is obtained through another endpoint call.
8. To offer a more practical experience, above the table we should have a text box and a "search" button which allows us to search for a specific ticket.
9. When clicking on a record in the table, the system should display another screen (main section) with the ticket details. In this case, only the ticket number and description should be displayed. Once inside, the system should give the option to return to the list of tickets.
10. Finally, in the same screen and in the upper right part of the screen there is a button to add a new record. In this case, we should display a form with the following data (Name of the account, Title, Date and Time). To obtain the account, the system must call another endpoint which will return the list of accounts associated with the user. With which, based on the obtained data we will have to fill the combobox.
It is a portal which must be developed in SvelteKit 1.0. The technology to be used can be TypeScript or JavaScript. At the styling level, you can use a library such as Tailwind or similar.
The portal must connect to a Restful API (VTiger) which we have hosted on a server. As for the API documentation, we already have a POSTMAN file with all the calls and examples.
Regarding the functionality of the portal, the following are the points to be taken into account.
https://github.com/TailAdmin/tailadmin-free-tailwind-dashboard-template
1. Access through login and password.
2. Once we have accessed, it should show a screen which will have a header, sidebar, main and footer (attached an example of the concept).
3. In the header there should be a logo on the left side and a user icon (avatar) with a menu showing the following options (Edit profile and logout). By clicking on the "profile" option, the system should load the profile data in the main section. The data to be displayed are (Name and email). If you click on logout, the system should exit and display the login window (and delete the API access token that was initially saved).
4. In the sidebar there should be the following options (Home and Tickets). The default option should be Home and the main should only show a title indicating "Main Page". On the other hand, the sidebar must allow to contract to give more amplitude on the screen.
5. When clicking on the Tickets option, the system should display a table in the main section with the tickets obtained from the API. Since the API pages every 100 records, the table should have a page indicator based on the total number of records (this data is obtained from the API call itself).
7. The columns that the table should display are (TicketNum, Account, Date, Title and status).Finally, each record should have an icon in the last column to download a document which is obtained through another endpoint call.
8. To offer a more practical experience, above the table we should have a text box and a "search" button which allows us to search for a specific ticket.
9. When clicking on a record in the table, the system should display another screen (main section) with the ticket details. In this case, only the ticket number and description should be displayed. Once inside, the system should give the option to return to the list of tickets.
10. Finally, in the same screen and in the upper right part of the screen there is a button to add a new record. In this case, we should display a form with the following data (Name of the account, Title, Date and Time). To obtain the account, the system must call another endpoint which will return the list of accounts associated with the user. With which, based on the obtained data we will have to fill the combobox.