- Add Cucumber for the whole of Refinery. (top priority)
- Add RSpec for the whole of Refinery, particularly:
- User, User plugin and User mailer
- Inquiry mailer and Inquiry setting
We've started an effort to move to Rails 3.0 - in fact, you are currently viewing the Rails 3.0 branch.
Work items still to do:
- Rework to exploit Rails 3 initialization hooks correctly (medium).
- Cucumber tests (medium) to check for regressions.
- Explore making the application into multiple gems, managed by Bundler (as a reference, refer to Spree: http://github.com/railsdog/spree)
- Migrate to new generator API (low).
- Migrate to new Mailer API (low).
- Fix other deprecations (low).
- Figure out how to setup dragonfly for Heroku (medium).
Join the IRC channel on freenode.net #refinerycms on August 7th to contribute!
-
Check all the views for missing translations
- You can run a rake task with your locale e.g for Slovenian:
rake translate:lost_in_translation LOCALE=sl
- You can run a rake task with your locale e.g for Slovenian:
-
Translate models and model attributes used in forms (Rails 2.3.8 supports translation form labels!)
-
Javascript messages etc:
-
Add in i18n support for the front-end as well
- Install process, update process, copying assets to public
- All these things should be made standard so that it is easier for plugin authors
- The refinery_plugin generator should create those files necessary for the plugin to be installed elsewhere
- Most plugins should be packaged as gems for ease
- Standardize the naming (refinerycms-[plugin_name]), most do this already but there are a few exceptions
- WYMEditor and the dialogs are the weakest areas right now.