What should be in an app framework?
Sunday, January 11th, 2009Dan Ahern and I are working on our first Ruby on Rails framework for application development. While this is really intended to be used as an internal tool, we figured we would stick it up on Github and open source it for anyone else who may find it useful. Our framework is called Embark and basically it is a starting point for application development for the type of social apps we develop. Right now as it stands it will be a more complete/modern version of Bort. We like Bort but found that it was missing a lot of things we needed and used some different plugins then we would use, so decided to create our own.
As it stands Embark will include the following features:
- User Management
- User SignUp
- Standard SignUp
- OpenID SignUp
- Facebook Connect SignUp
- Retrieve Password
- Edit Profile
- Delete Account
- User Page
- User SignUp
- Administrative Tool
- Dashboard Report (How Many Users)
- Query Tables
- Delete Accounts
- oAuth Integration
- Capistrano Recipes for deployment and maintenance
We are looking to you the community to see what other sorts of standard things… things you would find in 90% of the web apps out there, to include in our framework. So leave a comment and let us know if there is anything you would like to see or feel free to follow the project and contribute!



