nuvention-web / closet Goto Github PK

Add beta login button to the homepage and update call to action

Sass & Susy, like #17 but for profile

Like #18 but for profile pages

Request and template-ify JSON for items. Requires routing, template modification.

Add videogames and purses to items database with tweaking for new fields as necessary

Redirect after login should definitely go back to root ('/') and just check if authenticated and render a different template. The current /user/dashboard scheme is convoluted and confusing. Logging into facebook doesn't take you to facebook.com/timeline or something. Easy fix, but needs done.

look up how this is done
needs research research research

Jade + node script
Styling and appearance

Sass and Susy styles for Item Page
Paste an image for lower right-hand corner reviews
Empty tab for reviews in the bottom
No image gallery
Basically focus on the data already in the schema - the big item image, the description, rating, owner, and marketplace data (also an indicator if it's in the currently logged-in-user's favorites)

Implement basic user dashboard

• list items in personal catalogue
• form for uploading new items (hidden if catalogue has more than 5 items to display)

Implement Ajaxing, form handling, and styling for /register and /login. The current styles are sufficient for now; focus being form serialization and ajax, then response handling and error reporting (eg, "username already taken")

In order to achieve profile page completeness as per our mockups, it's necessary to add new fields to the Account schema and denormalize some of our data (meaning eliminate references to item masters and change a user's favorites and collections to hold full item objects), also limiting the number of db queries we make, which is an important consideration.

Aside:
It may make sense to duplicate some user data into a quicksearch db (like redis or something), but that's a scaling problem and a [SUPER REACH] goal at best.

@hersey @ccowan2015

I also reserved two labels for biz dev usage. You can mark things by priorities or by 'customer development' and 'marketing/design' and have everything else be unlabeled, whatever.

Add fields as described in #35 for marketplace info

See #20

marketplace tab wiring/selecting from db items forsale or forrent

Design, implement simple user dashboard. Most of the boilerplate is already there, it just doesn't do anything once routed.

Ignoring item upload functionality for now, let's have "seeded" (read: junk) items populate the database and then produce a user profile from that.

Jade template for profile pages

Jade template for the working draft item page

Refactor to reflect more hobby-centric data basis. Currently items are more detached from hobbies than we like.

Remove masters and just reference all data within item object, primarily for simplicity.
Setup items to be associated with hobbies easily.

form-data-style uploading
see http://howtonode.org/really-simple-file-uploads
use express' req.files

also see the excellent "pipe" in this module:
https://github.com/mikeal/request

Item page template (jade)
Item routing
Stories and users having this item

Some necessary fields:

email, username, realName, (facebook, twitter, openID profile connections?), password (hash - bcryptv2)

And a few more hobbies. Use populate.js for this.

As it says.

Also verify passport authentication and bcrypt hashing, both of which are technically "implemented", but untested.

Essentially: write and debug all the code leading up to and completing calls to Account.save() and Account.findOne(user).

https://github.com/nuvention-web/closet/issues/new#

What was done?
Researched rental models, insurance and safety and security , create more robust language around rental part of our model

What was not done? Why?
As many as interviews were not completed, bc we were focused on presentation and having answers prepared questions. We now have a webpage we can do live demo interviews

What do we need help with?
N/A

What is the biggest insight for this week?
We needed to get rid of wordiness presentation, words like "warm marketplace" help give illusion to what we are trying to create

https://www.npmjs.org/package/venmo
https://github.com/jamescarr/paynode
http://go.developer.ebay.com/devzone/articles/accepting-direct-payments-nodejs-using-paynode
https://github.com/braintree/braintree_node
https://www.npmjs.org/package/paynode

Style and format backend-fed item dashboard templates

facebook/google/persona/etc login

http://passportjs.org/guide/facebook/
http://passportjs.org/guide/google/
http://passportjs.org/guide/providers/

further research(?):
http://matthewtyler.io/handling-oauth2-with-node-js-and-angular-js-passport-to-the-rescue/

[May end up reassigned]
Set up the upload form, using the same basic code as in routes/populate.js, to save new item to the database.

Database of items that can be "re-used" so multiple users can have instances of the same item

Data structure is outlined here:

https://drive.google.com/file/d/0BwzpLVHHSuvnMW9aWFctNk5HN0U/edit?usp=sharing

~/edit -style api for changing user data

item page currently showing duplicates of items.

Thanks

Go back over the signup and login forms to ensure that all fields are accounted for and everything is set up correctly.

Potentially update sign up form to fill out more fields of the Account schema.

Form for uploading an item with

• select field for set list of hobbies
• unlimited tags (separated by spaces)
• all the necessary fields
• inMarketplace boolean checkbox
• if inMarketplace, is it for sale or for rent