synchronizing / sports-portfolio Goto Github PK

We need documentation for an API so back-end can begin writing routes and front-end will know what routes to hit.

At a high level our API should handle

• Retrieving a card from DB and store in client's memory
• Adding a card form client's memory to a user's cart in DB
• Retrieving a user's cart from DB
• Removing a card from a user's cart and updating DB
• Sending user's cart to our email service

This should easily follow CRUD, if there's anything you think is missing post a comment.

NOTE: Something that might be of interest is using swagger which is already built into our project because of the mean.io boilerplate.
---> SEE ./server/config/swagger.json and edit that.

Recommended resources
API Design suggestions
Sample Swagger.json and preview editor

This is an Angular component that we can add to the project.

Someone please create a shareable Gmail account for this project, and register to the following with it:

• MLab
• Heroku

Please share its info as a reply to this, and share it on Slack. Once the Heroku account is set-up, make sure to test our boilerplate:

1. Pull the repo, and try hosting on Heroku on their free plan.
2. Sync the Heroku repo with the master branch on GitHub so it's always updated.
3. Document the URL and credentials Heroku provides and share in Slack and below.

As of now, I believe the way we have the schemas set-up on our slides is probably fine, however I do not believe we would need the Cart schema. We could utilize Order with the confirmed column as a mean to keep track of whether or not it has been purchased, and therefore a substitute for Cart. Thoughts?

We have been unable to connect to our mongodb online. I have been the only one who has connected. If we can find what has been causing this issue and address it that would rock. I will start troubleshooting today. cheers ya'll

We have to figure out how the application will feel like. I would recommend checking out HTML themes on themeforest.net (make sure they aren't Wordpress, etc.)

The current wireframe for the project looks like so:

Homepage:

Sign-Up

Dashboard

The sidebar we are currently using is based on the ng2-semantic-ui package, which currently does not have support for the sidebar to be always open. To fix this the following must be done:

1. Fork the original ng2-semantic-ui.
2. Merge it with the fixed sidebar branch ng2-semantic-ui/yhnavein:feat(sidebar)/stay-open
3. NPM install the forked updated version.

Possible implementation demonstrated by another group.

Get some sample sports cards (front and back) and create a directory structure within the assets directory that makes it easy to access front and back images of the same card from the schema.

Card components are specifically for the navigator.

Create mongoose controllers for the card and orders. Adding a branch th/mongocontrollers and keeping my code stored there.

Post questions for Rick Strattum here, so that @bauff can keep track of everyone's concern.

Create colorscheme and set font size/spacing for better accessibility

Once the navigator is up and running, we need to expand on the sidebar's filtering settings.

This card-view component should allow admin privilege users to edit the cards directly from the UI. If you are in user privilege, you should only be able to view it.

From what I understand components are meant to hold views and logic specific to the component and data is meant to be fetched using services.
read more: https://angular.io/guide/architecture-services

So we should make a service that handles making appropriate requests to the backend so we can inject this data directly into our components.