Collectize

Heroku link

Minimum Viable Product

Collectize is a web application inspired by Pinterest that will use Ruby on Rails and React.js. By the end of Week 2, this app will, at a minimum, satisfy the following criteria:

• Hosting on Heroku
• New account creation, login
• A production README, replacing this README (NB: check out the sample production README -- you'll write this later)
• Homepage & Profile
  • Smooth, bug-free navigation
  • Adequate seed data to demonstrate the site's features
  • Adequate CSS styling
• Collections & Items
  • Smooth, bug-free navigation
  • Adequate seed data to demonstrate the site's features
  • Adequate CSS styling
• Custom Properties
  • Smooth, bug-free navigation
  • Adequate seed data to demonstrate the site's features
  • Adequate CSS styling
• Sort & Filter Collections
  • Smooth, bug-free navigation
  • Adequate seed data to demonstrate the site's features
  • Adequate CSS styling

Design Docs

• View Wireframes
• React Components
• Flux Cycles
• API endpoints
• DB schema

Implementation Timeline

Phase 1: Backend setup and Front End User Authentication (2 days, W1D2 6pm)

Objective: Functioning rails project with front-end Authentication

• create new rails project
• install gems
• install node packages
• front end skeleton
• configure webpack
• authentication back end (User model, SessionController, etc.)
• front end authentication flux cycle
• signup/login react components
• signup/login styling

Phase 2: Collections Model, API, and components (2 days, W1D4 6pm)

Objective: Collections can be created, read, edited and destroyed through the API.

• create Collection model
• seed database with test data
• CRUD API for Collections (CollectionsController)
• jBuilder views for Collections
• Collection react components
  • CollectionsIndex
  • CollectionThumb(dummy object)
  • CollectionForm
• search Collections by name in navbar
• basic styling

Phase 3: Items (2 day, W2D2 6pm)

Objective: Items belong to Collections, and can be viewed by collection.

• create Characteristic model
• create Item model
• Item CRUD
• Item Form
• Item seed data
• restyle CollectionThumb
• style ItemThumb
• style Item
• style Collection & CollectionForm

Phase 3 adds organization to the Items. Items belong to a Collection, which has its own Index view.

Phase 4: Sort & Filter (1 days, W2D3 6pm)

Objective: Items have characteristics with values, and can be sorted and filtered by value.

• create Value model
• create sort & filter flux API
• create Sort and Filter form react components
• style Collection with sort and filter form

Phase 5: Animate Collection (1 days, W2D4 6pm)

objective: Enable complex styling throughout.

• animate Item components when they're sorted & filtered

Phase 6: Styling Cleanup and Seeding (1 day, W25 6pm)

objective: Make the site feel more cohesive and awesome.

• Refactor HTML classes & CSS rules
• Add modals, transitions, and other styling flourishes

Bonus Features (TBD)

• collection description
• follow collections
• notifications when items are added to collections you follow
• Collections have tags; Profile has interests; Homepage displays collections by interest
• collaborative collections have more than one owner
• advanced sort options (e.g. "group by", "sort by then by")