No description, website, or topics provided.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
assets Adds forms fields reset to add instrument form May 10, 2017
grunt First commit May 3, 2017
lib First commit May 3, 2017
spec First commit May 3, 2017
.eslintrc.json First commit May 3, 2017
.gitignore First commit May 3, 2017
.jscsrc First commit May 3, 2017
.jshintignore First commit May 3, 2017
.jshintrc First commit May 3, 2017
.remarkrc First commit May 3, 2017
.scss-lint.yml First commit May 3, 2017 First commit May 3, 2017
Gruntfile.js First commit May 3, 2017
LICENSE First commit May 3, 2017 Corrects a spelling mistake Jun 3, 2017 First commit May 3, 2017
favicon.ico First commit May 3, 2017
index.html Adds change password function May 9, 2017
index.js First commit May 3, 2017
package.json First commit May 3, 2017
scrapcode.html bulk loads user authentication May 4, 2017

An explanation of this project:

This project is designed to be the initial build out for a website I want to have in the future. The original concept is to have an online store dedicated to selling violin family instruments to musicians in Boston. I want users to be able to sign up and add instruments or view and buy them all online with very little human intervention. This idea was too large a project for the three days of work we were given for this sprint so the project presented here designs and builds the back end server and the front end "business" side of the website. It allows for luthiers, people who build and repair instruments, to sign up and load their instruments onto the website. They can then view, edit and remove those instruments.


Since I had experienced working with user authentication before I built this part of the app first. It was fairly straightforward and went smoothly. My next step was to roughly design the web site. At first all of my user info forms and instrument info forms were right on the webpage. I used these forms to test my ajax requests. My biggest problem came at this point. When trying to get the ajax requests to add instruments to the forms I built I had two major problems. The first was understanding how getFormFields worked to turn form data into an object that got sent to the server. When I started looking at the object on my server logs as it was getting rejected and changing the forms around and experimenting with them I was able to understand how to properly lable the forms so the objects were built correctly. Following that I had to develop an understanding of the controllers in the API. This took me the longest amount of time to solve, though ended up being just two lines of code to change.

Future goals:

My immediate goals are to add an image link collumn and description collumn to the instruments table. Right now the website loads a hard coded image and hard coded text with each instrument add but it shouldn't be to difficult to use handlbars to replace that text with variables. I also want to standardize the type of photos that will be added to the site to present a stylized proffesional looking product to the end user.

After finalizing the "business" side I want to add a "customers" table. People who log in as customers can't add instruments. However they can log in and see every instrument available for purchase on the website. This is different from luthiers who only see the instruments they load. They of course won't be able to edit or remove these instruments, but they will be able to buy them online.

User stories: As a luthier, I want to be able to post an insturmnet that I have for sale/rent.

As a luthier, I want to be able to list the instruments type, price, details, and an image of the instrument.

As a luthier, I want to be able to see and manage/every every instrument that I've posted for sale.

As a luthier I want to know when I user has bought my instrument so I can send it to them.

Wireframe: Links to the repos:

Link to the live application: