Open unobliged opened 12 years ago
Also, passages currently do not have ownership. Make sure to implement some basic ownership model (including shared read and public r/w ownership) even if roles are not clear. It may or may not be necessary to add a Passage Status field to indicate private/public, think harder about it.
Admin for public passages, user for private, can add public. Toggles for public, private(self, added). Public can be free or paid. Paid passages should have a preview w/o vocab_list or some other mechanism to protect. That or implement content_author user role that separates users that can create passages vs those that cannot. Think carefully about security here...
Think about what roles might be needed to ensure proper separation of privileges. Admin may or may not be necessary, but there should be some way to separate content authoring ability based on account status.
It might be good just to check into how roles can be implemented with Devise and implement a test role if the User roles turns out to be a more complex issue than anticipated.