aboutsummaryrefslogtreecommitdiffstats
path: root/railties/doc/guides/source/creating_plugins/index.txt
diff options
context:
space:
mode:
Diffstat (limited to 'railties/doc/guides/source/creating_plugins/index.txt')
-rw-r--r--railties/doc/guides/source/creating_plugins/index.txt60
1 files changed, 0 insertions, 60 deletions
diff --git a/railties/doc/guides/source/creating_plugins/index.txt b/railties/doc/guides/source/creating_plugins/index.txt
deleted file mode 100644
index 0607bc7487..0000000000
--- a/railties/doc/guides/source/creating_plugins/index.txt
+++ /dev/null
@@ -1,60 +0,0 @@
-The Basics of Creating Rails Plugins
-====================================
-
-A Rails plugin is either an extension or a modification of the core framework. Plugins provide:
-
- * a way for developers to share bleeding-edge ideas without hurting the stable code base
- * a segmented architecture so that units of code can be fixed or updated on their own release schedule
- * an outlet for the core developers so that they don’t have to include every cool new feature under the sun
-
-After reading this guide you should be familiar with:
-
- * Creating a plugin from scratch
- * Writing and running tests for the plugin
- * Storing models, views, controllers, helpers and even other plugins in your plugins
- * Writing generators
- * Writing custom Rake tasks in your plugin
- * Generating RDoc documentation for your plugin
- * Avoiding common pitfalls with 'init.rb'
-
-This guide describes how to build a test-driven plugin that will:
-
- * Extend core ruby classes like Hash and String
- * Add methods to ActiveRecord::Base in the tradition of the 'acts_as' plugins
- * Add a view helper that can be used in erb templates
- * Add a new generator that will generate a migration
- * Add a custom generator command
- * A custom route method that can be used in routes.rb
-
-For the purpose of this guide pretend for a moment that you are an avid bird watcher. Your favorite bird is the Yaffle, and you want to create a plugin that allows other developers to share in the Yaffle goodness. First, you need to get setup for development.
-
-
-include::setup.txt[]
-
-include::tests.txt[]
-
-include::core_ext.txt[]
-
-include::acts_as_yaffle.txt[]
-
-include::models.txt[]
-
-include::controllers.txt[]
-
-include::helpers.txt[]
-
-include::routes.txt[]
-
-include::generators.txt[]
-
-include::generator_commands.txt[]
-
-include::migrations.txt[]
-
-include::tasks.txt[]
-
-include::gems.txt[]
-
-include::rdoc.txt[]
-
-include::appendix.txt[]