Restaurant Dashboard MVP
Executive Summary
The Cuiseek Restaurant Dashboard (RD) MVP will be designed to allow partner restaurant staff the ability to interact directly with Cuiseek's customer-facing dining outing planning tool. Cuiseek RD will enable restaurant host staff and managers to securely view incoming booking requests, commit to serve requested bookings, link Cuiseek bookings with their in-house table management systems, and eventually interact directly with incoming guests.
In its initial form, Cuiseek RD will be deployed as a web application on scalable cloud services to serve a growing audience as its feature set continues to evolve. Partner restaurants will interact with Cuiseek RD exclusively through a web browser.
As the iteration of Cuiseek RD described in this document is an MVP, all design decisions should focus on delivering the required functionality as efficiently as possible. However, as Cuiseek RD will be customer-facing, sufficient visual design and robustness should be included so that user engagement and trust can be maintained while the MVP assumptions are proven out.
Task Overview
The successful applicant will be expected to complete the following tasks.
Develop the web application outlined in this document, per the requirements below, using the proposed technical stack.
Commit code to the source control repository at least once for every day worked, or preferably more often as features are developed. Each commit should include a descriptive commit message.
Participate on a regular basis in a Slack channel. The Slack channel will be used by the requester to communicate about the ongoing development tasks, provide further information and answer any questions that arise.
Provide significant in-code documentation to make functional points understandable to other developers. Additionally, the README.md file should be filled out with details about how to build and deploy the system.
Deploy any prepared work to the provided Firebase hosting on a regular basis to allow for testing and feedback by the requester. Deployment shall be completed at least on a per-milestone basis.
Milestones
Development of the solution will be tracked by completion of the following milestones. These milestones should be completed in the order specified.
Implementation of the Authentication/Login page and related functionality include redirection of unauthenticated users.
Implementation of the Booking Requests Dashboard, including request acceptance and rejection.
Implementation of the View Booking Request page, excluding viewing of the pre-ordered menu items.
Implementation of the View Bookings page, including selection of queried data by date, assignment of table and management of statuses, however excluding the free-form search feature.
Implementation of the View Booking page, excluding the display of pre-ordered menu items.
Implementation of viewing the per-ordered menu items on the View Booking Request page and View Booking page.
Throughout the delivery of each milestone, documentation, communication, and source control commitals shall be upkept as specified in the Task Overview.
Technical Stack
The following is a summary of the proposed technical stack for Cuiseek RD, broken down by category.
Backend
Consistent with other Cuiseek products, Cuiseek RD shall be implemented on Google's fully scalable Firebase cloud products. Specifically, Cuiseek RD should make use of:
Firebase Hosting - Static Web Hosting
Firebase Cloud Firestore - NoSQL Database
Firebase Cloud Functions - Node.js Backend
Firebase Authentication - Email/Password based authentication
Front-End
Cuiseek RD will be deployed as a web application on static hosting. To interact with Firebase,
Cuiseek RD will need to make extensive use of JavaScript, however may be implemented and built from web application frameworks. At time of writing, the decision is to use the following, with others to potentially be added later:
Application Platform - React.
Design - Google Material Design Components, or similar product.
Source Control
All development effort on Cuiseek RD shall be committed to a GIT source control repository, hosted by BitBucket, to which the developer will be granted access for the duration of their involvement in the project.
All work shall be committed to the Toogit branch of the repository, with sub-branches used as required.
Please submit your resume as well as sample projects & code for review. Successful candidate will be provided additional detailed project requirements.
About the recuiterMember since May 20, 2018 Gunawan Gunawan
from Shaanxi, China