LET'S MEET - MEETING SCHEDULER

Angular platform is used to build scalable application. It uses socket.io to make the web app realtime. Angular is highly robust, meanwhile allows to create app for multiple platform like mobile, desktop and web.

Let's Meet mean stack application is used to schedule your meetings with clients. Both admin and user also get notified in real time, if any changes is made to the meeting details.

Requirements

These following will allow you to use this project in proper way.

1. Install Node and npm as per official documentation.

   Nodejs -- install Nodejs

2. Install Git to clone the repo.

   GIT -- install Github

3. Install angular-cli

   > npm install -g @angular/cli

Installation

1. Create folder in your local drive.
2. Move to your local folder.

   cd your-folder-name

3. Now, git init

   git init

   git remote add origin https://github.com/pankajsaini123/todoFront.git

   git pull origin master

   Install all dependencies that need to run project.

   npm i

   Run the command to run project in terminal.

   node index.js 

More about application

Project Description -

This project should be a ready to deploy meetings scheduling system.There should be two separate parts of the application.

A Frontend developed and deployed using the technologies and a REST API (with realtime functionalities) created using the technologies.

Frontend Technologies used - HTML5, CSS3, JS, Bootstrap and Angular

Backend Technologies used - NodeJS, ExpressJS and Socket.IO

Database used - MongoDB and Redis

Features of the Application -

1) User management System -

a) Signup -

User should be able to sign up on the platform providing all details like FirstName, LastName, Email and Mobile number. Country code for mobile number (like 91 for India) should also be stored. You may find the country code data on these links (http://country.io/phone.json,http://country.io/names.json)

b) Login - user should be able to login using the credentials provided at signup.

c) Forgot password - User should be able to recover password using a link or code on email. You may use Nodemailer to send emails. (Please use a dummy gmail account, not your real account).

2) User Authorization system -

a) User can be of two roles, normal and admin. Admin should be identified with a username ending with "admin", like "alex-admin" is an admin, since it ends with "admin".

3) User Slots management system (Flow for normal User) -

a) Upon login, normal User should be taken to a dashboard showing his current months', planned meetings, in the form of a calendar. Current day-cell should be selected by default.

b) User should be able to only view his meeting slots and he should not be able to make any changes

4) User Slots management system (Flow for Admin User)-

a) Upon login, admin User should be taken to a dashboard, showing all normal users in a list format

b) Upon clicking on any user, admin should be taken to user's current calendar, with current date selected, by default.

c) Admin should be able to add/delete/update meetings on any day, by clicking on a appropriate day-cell/timeline. d) These details should be stored in database for every user.

5) User Alerts management system

a) Normal User should also be notified in real time, though an alert if he is online, and email (irrespective of whether he is online or offline), when

i) A meeting is created by admin

ii) A meeting is changed by admin

iii) 1 minute before meeting, with an option to snooze or dismiss. If snoozed, alert should come again in 5 seconds, if snoozed again, it should re-appear in next 5 seconds and so on. Once dismissed, alert should no longer appear.

6) Planner Views

a) Similar to Google or outlook calendars.

b) The view must follow -

i) Planner should show only current year, past and future years to be ignored.

ii) User should be able to change months, through an arrow button(or prev/next button), each month should show all the dates in tabular format, like in actual calendar.

iii) Day Cells should be filled, if any meeting is kept, with a some design. There should also be a design for overlapping meetings.

iv) Upon click the day's cell, a view should pop, showing all meetings, along a 24 hr timeline, with the slots covering the exact duration of each meeting.

v) Upon clicking on a meeting, its details should pop up in another view

c) Admin Flow:

i) For admin, a create button should be there in calendar view, to create a meeting.

ii) Upon clicking on create button, details view should open.

iii) Once created, it should appear on the calendar view.

iv) Upon clicking on an already created meeting, same details view should open.

v) Details view should be a form

vi) Admin should be able to make changes in meeting details form, and submit.

vii) Admin should be able to delete a meeting as well, with another button

viii) Meeting details, should cover when, where and purpose. Also, by default username of the admin, who kept the meeting, should also show in non-editable format.

7) Error Views and messages -

You have to handle each major error response (like 404 or 500) with a different page. Also, all kind of errors, exceptions and messages should be handled properly on frontend. The user should be aware all the time on frontend about what is happening in the system.

Documentation

All required api documentation using apiDoc.

Apidoc - Api Documentation for todo app backend

Authors

• Pankaj Singh -- Pankaj Singh

Acknowledgements

• I would like to thank my friends who supports me during the development of this app.