Hello, How are most people designing administrative capabilities into their Merb apps? I read some discussion of this in the archived IRC logs, but not a lot.
Admin functionality could be integrated directly, with (I suppose) lots of conditional code in controllers and views, or built as a subsection of a site, or a completely separate application. What's a good strategy for admin? I'm also interested in how to integrate this functionality with an application's workflow. For example, with a job listing site users might submit an ad which requires approval by an administrator, after which they might have edit capabilities. Or besides approval, a payment process may be integrated, further muddling the CRUD process. In other words, responsibility for an entity may shift back and forth between users (submitters) and administrators, or even third parties. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
