Upload custom image set

[knitcodemonkey]

Issue

Current Behavior

There is only one image set: "Bee Creative"

Desired Behavior

• Instructions on how to upload image(s) with your own quilt fabric
• Form to upload images
• Form to select/use your image set
• Images upload to their own folder. Name of folder should be included in name of file.

Questions

• Do we allow all image sets to become public?
• Does this require a user profile?

[izhuravlev]

@knitcodemonkey Would you like me to help you work on any of the issues created?

[knitcodemonkey]

I would gladly accept any help you’d like to offer.

I’ve been concerned about image uploads for many reasons. Opening them up to everyone will likely cause a great mess. I thought implementing firebase auth, and a cloud image storage solution may help keep image sets private for each quilter.

I’ve also been wanting to convert the prop-drilling into context providers for easier consumption, and expansion as the project grows.

For image uploads, specifically, I think there are a few steps that need to be included.

1. Upload multiple images
   2 Reorder images into their hue/group combinations (the project currently orders them by number so the remainder math works for controlling randomization.)
2. Name image sets
3. Include info required in the ‘components/utils/specs.js’ file

Any suggestions or ideas are also welcome.

[izhuravlev]

@knitcodemonkey Will think about it and do a little research in firebase auth variations and how similar problems are solved in other projects.

[knitcodemonkey]

Because the project isn’t wildly popular, yet, it may be worth it to start simply with the actual functionality. We can always put it behind a login later.

[izhuravlev]

Sounds good, will get on it - or you can give me another issue if you want.

[knitcodemonkey]

This is a larger chunk of the project. If you choose to work on it, feel free to add incremental PRs as pieces are finished so that you're never left feeling solely responsible for the entire feature. I want you to enjoy working in this, not feel absolutely required.

If you would prefer a smaller issue, this is a bug that I'd like tackled relatively soon:
#24

[izhuravlev]

Hey @knitcodemonkey,
Sorry for being out for so long - had a hard time at college.
I am going to work on it today and during the weekend.

[knitcodemonkey]

The beauty of open source is that it is voluntary. Totally take care of you first! Thank you for anything you contribute.

[izhuravlev]

@knitcodemonkey I actually realized that this issue is a pretty big piece of work.
Should we probably break it into several pieces/issues?
I believe there are a couple of questions that should be solved and implemented to solve this task.

1. Where to host?
   As I understand it, we can not store uploaded image sets on the GitHub, which is basically our hosting platform. So, we need a database. I believe that MongoDB can be a good solution for this. GridFS can handle the storage of images: docs.

2. Do we need a server?
   With the implementation of accounts handling, image hosting and managing, authentification, we probably want to reduce the load on the front-end of our site. Should we create a Server and make it responsible for image sorting, authentication, keys, image storage? If we do create one, we can also store our images there - though, the storage could be not infinite. [Heroku](https://devcenter.heroku.com/) hosting could be helpful for Server hosting. (And Front-End can be moved to Heroku as well, they allow up to 5 projects to be hosted for free).

3. (Probably) Implement account creation.
   This will allow to secure image uploading and allow image-set editing in the future. (We don't want complete strangers to change and delete image sets that are already here or created by other people.

4. Implement Image uploading.
   This will include a specific component (it could pop-up and blur the rest of the screen on specific button pressed), which will take the image set (a number of images), receive them, organize in a way we need it (probably crop them to square form, and reduce their weight), and send to the server, where they would be added to the specific folder, sorted by hue, and other possible tasks.)
   I am looking up the possible image-set receiving library.