girlscript / feminist-bible-phase-2 Goto Github PK

Make a controller function under authController to check if a user is logged in.

Build a sign up system from scratch. We won't be using things like passport js. Use bcrypt js for hashing the things. You can work on this issue once the user schema is created.

Make the following changes to the user schema:

1. Remove trim from the password field
2. Use naming convention such as firstName instead of firstname

Refer to the design (Header 2 frame) and add the button and avatar to the existing header components. These two elements will be shown only when the user is logged in. Use states in React.

As we are making an API so we would have to send response status codes. Therefore we should have the status codes (those which are commonly used) mentioned in the readme file of the backend, so that everyone uses the same set of status codes.

Please refer to the design and make the card. Do not set absolute width and heights.

Under admin controller create a function to add new project. See the issue of project schema for the fields required in the projects

Make the controllers for admin signin and sign up

Write a controller function and necessary route for updating user profile

1. Follow CSS BEM architecture.
2. Make a separate SCSS file for this page.
3. Do not compile scss.

Under controllers directory in userController create a function to create a story . (It's for the scenario when users will write some story (post) ). Add a route and link this to the controller function. Please attach a screenshot of the response in the PR ( Test in postman)

Add a controller function to get all the stories. Add a route as well. Attach a screenshot of the response in the PR. (response from postman)

In the site we are building , admins of an organization will add projects on which different members of the different organizations will collaborate on. We need the project title, project description, posted by ( the organization will be referenced), timestamps. For now just add these fields. Make a controller function to see all the organizations. Another controller function to get all the projects organization wise.

Follow CSS BEM architecture.
Make a separate SCSS file for this page.
Do not compile scss.

• Use existing header, blogCard components
• Use grid system

Add a controller function to delete a story. Attach Screenshot of the postman response in pr.

Create a project schema with fields project title, project description and posted by which should be an organization (referenced)

automatically

• run test cases for front-end and API codebase on each Pull Request (requirement: add database URI to repo secrets)
• deploy frontend to github-pages on new commits to master (gh pages needs to be turned on in gh-pages branch)

Use bcrypt js for encrypting the password. Use nodemailer to send the reset password email. On clicking the link user will have the option to enter new password and confirm password. Encrypt the password and save it to database. Let the user schema be created first then work on this

Create an admin schema . It should have the basic things as of now. Name, email, phone , password. Other things will be added later on.

Follow CSS BEM architecture.
Make a separate SCSS file for this page.
Do not compile scss.

Kindly refer to the design and make the footer. All the dimensions should be pixel perfect. Use scss variables wherever necessary.

Add a controller function to update a story. Attach Screenshot of the postman response in pr.

It should have the basic things of user , eg: Name, email, phone, password. Other things will be added later on

I would like to work on this.

Make a controller function to update the organization details

Please refer to the design. Do not set fixed height and width to the card. The image can have a fixed height.

Make the user login system. Don't use passport js. Use login system built from scratch.

Refer to the design.

• Add validations for email and password fields.
• Use existing header and input components.

Follow CSS BEM architecture.
Use the existing header, footer and blogCard components
Refer to the design Admin Profile

1. Follow CSS BEM architecture.
2. Use the existing avatar.scss file. Rename it to _avatar.scss
3. Do not compile scss.

Kindly refer to the design and make the blog card. All the dimensions should be pixel perfect. User variables wherever necessary.

Create an organization schema. It should includes fields name, email, totalMembers, password. These fields are enough for now. We will add other fields later on.

When some organization will post some story it must be approved by the admin. Make the routes and controller function. For reference look at the approval system of organization registration

Add a controller function to get a single story. Attach response from postman in the pr.

On sign up route in the swagger docs the status code 200 is used, whereas the code for created is 201. It should be corrected.

Improve the readme for the backend to include the setup, installation and usage guide for mongo db.

It should have name, author, make author reference type. One field for storing the image for the story. Time when the story was posted. Heading of the story.

Please refer to the design. Make sure the UI is pixel perfect. Follow BEM notation.

Implement Swagger to document the REST APIs. So that the frontend developers can easily look into it and get the required endpoints easily

Write a controller function and add necessary route to get user profile

Follow CSS BEM architecture.
Use the existing header, footer and projectCard components
Refer to the design project listing

In our website some organizations will request for registration and soon they will register approved : false will be there in database.
So the admins should be able to see the approval requests. So that they can either accept or decline them. Make two other controller functions which will allow admin to accept the approval or to decline. Keep all these approval thing inside the adminController.js file