lchski/cca

A service to allow for awesome timetable tracking as well as related school sillies.

cca's Issues

Consolidate/Organize/Make Routes Better

They're all over the place. Just look at the output of rake routes to see what I mean:

          users GET    /users(.:format)           users#index
                POST   /users(.:format)           users#create
       new_user GET    /users/new(.:format)       users#new
      edit_user GET    /users/:id/edit(.:format)  users#edit
           user GET    /users/:id(.:format)       users#show
                PUT    /users/:id(.:format)       users#update
                DELETE /users/:id(.:format)       users#destroy
       sessions POST   /sessions(.:format)        sessions#create
    new_session GET    /sessions/new(.:format)    sessions#new
        session DELETE /sessions/:id(.:format)    sessions#destroy
           root        /                          static_pages#home
         signup GET    /signup(.:format)          users#new
         signin GET    /signin(.:format)          sessions#new
        signout DELETE /signout(.:format)         sessions#destroy
     create_new        /create_new(.:format)      classy_classes#new
create_schedule POST   /create_schedule(.:format) schedules#create
   create_class POST   /create_class(.:format)    classy_classes#create
    my_schedule GET    /my_schedule(.:format)     schedules#show

This should be a priority to fix before we proceed much further. Consistency will make our lives (and our users') easier!

Templating

We should have a "schedule template" system. When a user goes to create a schedule, it should offer them the choice of various schools for which we've prebuilt templates.

Thoughts?

Facebook/Twitter for User Creation

Having users go through a signup process is a bit of a pain (especially for our target audience, highschoolers), so it would be preferable to have alternate user creation mechanisms.

Facebook and Twitter seem like good candidates for this, given their popularity and (relative) ease of integration.

Perhaps once we figure out a good user workflow for this, they could replace the standard user creation process entirely.

Thoughts?

Change to an API Backend Model

What are thoughts on changing the backend so that it acts more as an API. This is to decouple our application from our presentation, which allows us to build other frontends which work in different contexts (ex. an iOS or Android app).

This would require a (potentially significant) refactor. It could be worth it. Maybe we push this to after we get our MVP out?