briefly cover reasons why plugins and engines are useful
models - active_record relationships models+controllers - authentications - devise views
probably seen this message,
You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released
++ need to better describe the structure of plugins
++ need to better describe how Rails 2.3 plugins are loaded within rails
console message and blog post
-- how to turn off the deprecation warning
types [mountable, full] core structural components integration with rails
++ note how plugins and engines differ
implemented an isolated namespace
lib/qe/engine.rb
gemspec
++ need to verify gemspec dependencies
we wanted to leverage Ruby Mixins rather than open classing - to more explicitly control engine classes and MainApp class interconnectivity. therefore, ActiveSupport::Concern
javascripts
stylesheets
images
++ can you precompile these in the gem?
spec/dummy
RSpec configurations
testing tools
put some code here