added note to create add-on first for each type of add-on functions

Author: Andy McCormick

docs/cli/creating-a-command.md

@@ -7,6 +7,8 @@ The ExpressionEngine [Command Line Inferface (CLI)](/cli/intro.md) makes it simp
 
 You can also build your own commands that will enable users to interact with your add-on or do other things inside of ExpressionEngine. Commands are created to live within add-ons, and are registered as part of the add-on process.
 
+NOTE:Before adding a custom CLI Command to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
+
 ## Generate Our Add-on
 We add custom commands to the CLI when our add-on is installed by using the CLI.
 

docs/development/actions.md

@@ -14,6 +14,8 @@
 ## Overview
 Actions in ExpressionEngine are URL endpoints that are reached with the `ACT` query parameter. An example of this might be `http://myamazingsite.com/?ACT=43` where 43 is the ID given to an action registered in the `exp_actions` database table. These actions are tied to methods in an add-on which can be used to accept input from forms or run some sort of other functionality defined in the add-on. 
 
+NOTE:Before adding an action to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
+
 ## How To Build An Amazing Action?
 To generate an action we use the CLI to add the action to our existing add-on named "Amazing Add-on".
 

docs/development/custom-template-tags.md

@@ -21,6 +21,8 @@ TIP:If you are unfamiliar with Template Tags be sure to read the docs on [Expres
 
 Creating your own custom template tags allows you to display dynamic data from your add-on anywhere you want, in any template.
 
+NOTE:Before adding a template tag to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
+
 ## Creating Template Tags
 Tags are created via the CLI by using the `make:template-tag` command. 
 

docs/development/extensions.md

@@ -19,6 +19,8 @@ lang: php
 
 Within ExpressionEngine are what is known as "hooks"; little snippets of code in over 100 strategic places that allow the calling of third-party scripts that can rewrite and modify the inner workings of the program. By hooking into the core, you can do things like modify an entire Control Panel page, add/remove functionality, and modify the appearance of certain page elements. Hooks enable third party developers to modify aspects of ExpressionEngine without hacking the core.
 
+NOTE:Before adding an extension hook to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
+
 ## Creating Our Extension Files
 
 We can give our add-on the ability to hook into the core of ExpressionEngine by using the CLI:

docs/development/fieldtypes/example.md

@@ -17,9 +17,34 @@ The snippets below were truncated for clarity. The full example fieldtype can be
 
 [TOC]
 
-## Installation
-
-The google maps fieldtype is going to have 3 global settings. Latitude, longitude, and zoom. These will determine what the default map looks like. By returning an array from within install we can provide a default set of global settings.
+## Generate Fieldtype File
+Start by generating a custom fieldtype for your add-on using the `make:fieldtype` command. 
+
+```
+$ php system/ee/eecli.php make:fieldtype
+Let's implement a fieldtype!
+What is the fieldtype name? Amazing Fieldtype
+What add-on is the fieldtype being added to? [amazing_add_on]:  amazing_add_on
+Building fieldype.
+Fieldtype created successfully!
+```
+
+This will create a `ft.amazing__fieldtype.php` in your add-on's folder.
+
+We'll now update the methods found within our fieldtype's class to provide our functionality:
+- `function install()`
+- `function display_global_settings()`
+- `function save_global_settings()`
+- `function display_settings()`
+- `function save_settings()`
+- `function display_field()`
+- `function replace_tag()`
+- `function replace_latitude()`
+- `function replace_tag_catchall()`
+
+## Installation - `install()`
+
+The google maps fieldtype is going to have 3 global settings. Latitude, longitude, and zoom. These will determine what the default map looks like. By returning an array from within our `install()` method we can provide a default set of global settings.
 
     function install()
     {
@@ -35,7 +60,7 @@ The google maps fieldtype is going to have 3 global settings. Latitude, longitud
 
 The installation method for this fieldtype does not create any additional tables, so no cleanup work needs to be done. The default `uninstall()` method provided by the EE_Fieldtype parent class will suffice. Most fieldtype methods have sensible defaults to help reduce duplicate code.
 
-## Global Settings
+## Global  - `display_global_settings()`
 
 The installer sets the default global settings, but currently there is no way to change these from the control panel. We can use the `display_global_settings()` method to return the contents of the settings form. Having this method also enables the global settings link on the overview page.
 
@@ -50,9 +75,9 @@ The installer sets the default global settings, but currently there is no way to
         return $form;
     }
 
-Manually entering longitudes and latitudes is inconvenient so the final method in the example download also adds some javascript to let the user choose from a map.
+Manually entering longitudes and latitudes is inconvenient so the final method in the example download also adds some JavaScript to let the user choose from a map.
 
-## Saving Global Settings
+## Saving Global Settings - `save_global_settings()`
 
 In most instances saving the global settings is as easy as storing the `$_POST` array. Remember to include existing global settings if not everything can be changed.
 
@@ -61,7 +86,7 @@ In most instances saving the global settings is as easy as storing the `$_POST`
         return array_merge($this->settings, $_POST);
     }
 
-## Individual Settings
+## Individual Settings - `display_settings()`
 
 The default map may not always be the desired choice for each map field, so on the regular settings page it will display a similar configuration screen. We will use the familiar [Shared Form View](development/shared-form-view.md) format to display our settings.
 
@@ -127,7 +152,7 @@ The default map may not always be the desired choice for each map field, so on t
         ));
     }
 
-## Saving Individual Settings
+## Saving Individual Settings - `save_settings()`
 
 Saving individual field settings works largely the same as saving global settings. Keep be aware that they are later merged with global settings, so they can override a global setting.
 
@@ -142,7 +167,7 @@ If your fieldtype needs a wide style on the publish form, like Grid or a Textare
         );
     }
 
-## Displaying the Field (Publish Page)
+## Displaying the Field On the Publish Page - `display_field()`
 
 With all the settings set up, it can now be displayed on the publish screen. A key factor when you get to this stage is to decide in what format the data should be stored. Since all three available values in this case are numbers, this field will store them separated by pipes (`lang|lat|zoom`).
 
@@ -173,9 +198,9 @@ With all the settings set up, it can now be displayed on the publish screen. A k
         return $hidden_input.'<div style="height: 500px;"><div id="map_canvas" style="width: 100%; height: 100%"></div></div>';
     }
 
-## Rendering the Tag
+## Rendering the Tag - `replace_tag()`
 
-Finally, the field needs a frontend display. For google maps this will almost exclusively be javascript.
+Finally, the field needs a frontend display. For google maps this will almost exclusively be JavaScript.
 
     function replace_tag($data, $params = array(), $tagdata = FALSE)
     {
@@ -193,6 +218,8 @@ Finally, the field needs a frontend display. For google maps this will almost ex
 
 Along with parameters a field can also provide tag modifiers to change its output. In the template these are called by adding a colon to the fieldname, followed by the modifier name. For example: `{myfield:latitude}`. The advantage that field modifiers have over parameters is that they can be used in conditionals.
 
+These methods are not created by the CLI and need to be added as needed to your fieldtype's class.
+
 Parsing the modifiers is identical to using the regular `replace_tag()` function. The method name must start with `replace_` followed by the modifier name.
 
     function replace_latitude($data, $params = array(), $tagdata = FALSE)

docs/development/fieldtypes/fieldtypes.md

@@ -15,10 +15,14 @@ lang: php
 
 [TOC]
 
+## Overview
+ExpressionEngine ships with a range of fieldtypes already in place. However, perhaps you want to had your fieldtype that executes functionality differently than the fields that ship with ExpressionEngine. If so, then read below for how to create your own custom fieldtype. 
+
 TIP: For an overview of what a Fieldtype is, read the [Fieldtype Overview docs](/fieldtypes/overview.md).
 
+NOTE:Before adding a fieldtype to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
 
-## Generating A Custom Fieldtype
+## Creating A Custom Fieldtype
 
 Adding a custom fieldtype to your add-on is easy with the `make:fieldtype` command. 
 
@@ -40,7 +44,7 @@ amazing_add_on
 ┗ ...
  ```
 
-## Basic File Structure
+## Basic Fieldtype File Structure
 
 All fieldtypes must inherit from the `EE_Fieldtype` base class and they must provide an `$info` array with a name and version number.
 

docs/development/modules.md

@@ -1,4 +1,4 @@
----
+0---
 lang: php
 ---
 
@@ -15,10 +15,13 @@ lang: php
 
 [TOC=2-3]
 
+## Overview
 If you have ever used some of the add-ons that ship with ExpressionEngine such as [Block and Allow](/add-ons/blocklist.md) or [Pro Search](/add-ons/pro-search/overview.md), you will notice those add-ons have settings and configuration pages associated with them in the Control Panel. You add this functionality to your add-on using Control Panel Routes, also known as `Mcp` files. Whenever you add a Control Panel Route to your add-on using the CLI, an `Mcp` and `views` folder is automatically created for you, opening the door to creating your own Control Panel settings and pages.
 
 NOTE:**NOTE:** Control Pages are what is rendered in the browser when visiting your add-on in the Add-on Manager. Control Panel Routes are what we had to our add-on that tells ExpressionEngine to render the pages. Think of it as we add a route to create a page.
 
+NOTE:Before adding a Control Panel route to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
+
 ## Generate Your Route
 
 If your add-on doesn't already have the required `Mcp` and `views` files, you can add a route to your add-on using the `make:mcp-route` command in the CLI.

docs/development/prolets.md

@@ -18,6 +18,8 @@ Prolets are add-on components that live in the [Dock](/advanced-usage/front-end/
 Here is an example of the add-on SEEO's prolet, which easily allows editors to edit SEO data for the entry they are currently viewing: 
 ![prolet example](_images/prolet_example.png)
 
+NOTE:Before adding a Prolet to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
+
 ## Creating A Prolet
 
 Creating a Prolet is straightforward using the `make:prolet` command in the CLI.

docs/development/tab-files.md

@@ -23,6 +23,8 @@ Add-ons can also add tabs which are visible on in [Publish Layouts](control-pane
 Here is an example of the publish layout's tab for the Structure add-on:
 ![structure tab](_images/structure_tab.png)
 
+NOTE:Before adding a tab to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
+
 ## Creating The Tab File
 Tab files are not currently able to be generated through the CLI, thus you will need to manually create the file `tab.[addon_name].php` in the root of your add-on's folder.
 

docs/development/widgets.md

@@ -11,6 +11,8 @@
 
 [TOC]
 
+## Overview
+
 Along with the basic widgets which will come native with ExpressionEngine, each third-party add-on can provide multiple widgets to show pertinent information to users.
 
 Widgets which are shipped with add-ons can have `.html` or `.php` extension and have to be placed into `widgets` sub-directory of the add-on. They are then installed automatically when the add-on is installed or updated. When using the CLI to generate a widget, a PHP widget will be created.
@@ -20,6 +22,8 @@ TIP:Users can also create widgets using ExpressionEngine template manager withou
 Here is an example of the Dashboard Widget shipped with the SEEO add-on:
 ![SEEO dashboard widget](_images/dashboard_widget_example.png)
 
+NOTE:Before adding a Dashboard Widget to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
+
 ## PHP Widgets
 
 In order for an add-on to provide dashboard widgets, it needs to contain `widgets` folder inside its main directory, which will contain the widget files.