more updates and sidebar items

Author: Andy McCormick

docs/_images/addon_sidebar_start.png

@@ -38,7 +38,7 @@ Getting started making an add-on is incredibly easy with the CLI. To begin makin
 $ php system/ee/eecli.php make:addon
 Let's build your add-on!
 What is the name of your add-on? Amazing Add-On
-Add-on description? This add-on does amazing things!
+Add-on description? [Amazing Add-on description] This add-on does amazing things!
 Add-on version? [1.0.0]1.0.0
 Add-on author? ExpressionEngine Developer
 Add-on author URL? www.expressionengine.com
@@ -47,15 +47,10 @@ Your add-on has been created successfully!
 
 ```
 
-This will create an add-on named Amazing Add-On in your `system/user/addons` folder with a file structure like below:
+This will create an add-on named Amazing Add-On in your `system/user/addons` folder with a skeleton file structure like below:
 
 ```
 amazing_add_on/
-┣ Module/
-┃ ┣ Actions/
-┃ ┃ ┗ ExampleAction.php
-┃ ┗ Tags/
-┃   ┗ ExampleTag.php
 ┣ language/
 ┃ ┣ english/
 ┃ ┃ ┣ amazing_add_on_lang.php
@@ -64,7 +59,7 @@ amazing_add_on/
 ┗ upd.amazing_add_on.php
 ```
 
-This is the starting point of an add-on and is enough to begin creating template tags, extension hooks, and much more! From here, you can add more functionality to your add-on depending on your needs. 
+At this point, your add-on can't really do anything other than be installed. However, from here, you can add more functionality to your add-on via the CLI depending on your needs. 
 
 Here's a list of functionality that can be added to your add-on and the corresponding CLI command if applicable:
 
@@ -96,6 +91,7 @@ amazing_add_on
  ┃ ┣ TemplatePostParse.php
  ┃ ┗ TypographyParseTypeEnd.php
  ┣ Mcp
+ ┃ ┣ Sidebar.php
  ┃ ┣ Index.php
  ┃ ┗ Page2.php
  ┣ Module
@@ -172,31 +168,51 @@ Reference [Adding Prolets](development/prolets.md) for more information on addin
 ### The Add-on Icon File `icon.svg`
 The add-on icon folder is used both in the Add-on Manager and in the Dock on the front-end to distinguish your add-on from others.
 
-### `/Extensions`
+### Extensions - `/Extensions`
 When we tell the CLI that we want to create an extension, classes are automatically created in the `Extensions` folder along with the above mentioned `ext.[addon_name].php` file. Interacting with hooks allows us to extend ExpressionEngine's functionality, thus we refer to these as "extensions". 
 
 TIP: Reference the [Extensions](development/extensions.md) section of the docs for more information on using extensions in your add-on.
 
-### `Module/Actions`
-The `Module/Actions` folder stores all the business logic for any actions that we are adding to ExpressionEngine with our add-on. Each action will have a separate file and corresponding class created based on information provided in the `$actions` array in the `upd` file.
+### Actions - `/Module/Actions`
+The `Module/Actions` folder stores all the business logic for any actions that we are adding to ExpressionEngine with our add-on. Each action will have a separate file and corresponding class created based on information provided in the `$actions` array in the `upd` file.   
+Reference [Adding Actions](development/actions.md) for more information on creating URL endpoints (actions) with your add-on.
+
+### Control Panel Pages - `/Mcp`
+The `Mcp` folder contains all the Control Panel pages and sidebar we create for our add-on.    
+Reference [Adding Control Panel Pages](development/modules.md) for more information on adding Control Panel pages with your add-on.
 
 ### `Module/Tags`
-The `Module/Tags` folder stores all the business logic for any template tags we create with our add-on. 
+The `Module/Tags` folder stores all the business logic for any template tags we create with our add-on.    
+Reference [Adding Template Tags](development/custom-template-tags.md) for more information on adding template tags with your add-on.
 
 ### `/views`
 The `views` folder contains all of our Control Panel views which will be used to render our add-on's control panel pages.
 
 ### `/language`
-The `language` folder contains all of our language files that will be used to display text on a page in whatever language is selected in the user’s account settings. 
+The `language` folder contains all of our language files that will be used to display text on a page in whatever language is selected in the user’s account settings.    
+Reference [Using Language Files](development/add-on-language-files.md) for more information on using language files with your add-on.
 
 ### `/database/migrations`
 The `/database/migrations` folder holds all migrations that will be ran on installation or updating of our add-on. Using the CLI, migrations can also be ran independently.
 
 ### `Model`
-The `Model` folder holds all models that we are creating with our add-on.
+The `Model` folder holds all models that we are creating with our add-on.     
+Reference [Building Your Own Models](/development/services/model/building-your-own.md) for more information on creating your own models with your add-on.
 
 ### `widgets`
 The `widgets` folder holds all dashboard widgets we create with our add-on.
+Reference [Developing Dashboard Widgets](development/widgets.md) for more information on creating widgets with your add-on.
+
+## Setting Default CLI Config Values 
+
+When creating an add-on via the CLI you will be asked for author and the author's URL. If you'd like to skip these questions when creating an add-on, you can set default values in your [config](/general/system-configuration-overrides.md#main-configuration-file) file like so:
+
+```
+...
+$config['cli_default_addon_author'] = 'ExpressionEngine Developer';
+$config['cli_default_addon_author_url'] = 'https://expressionengine.com';
+...
+```
 
 ## A Word About Legacy Add-On Development
 In the past, add-ons were often categorized based on their functionality. We identified our add-on to ExpressionEngine as a fieldtype, extension, module, or plug-in. Thus there was never a straightforward process on structuring one add-on that contained all these categories in one.   

docs/development/addon-development-overview.md

@@ -24,15 +24,25 @@ Adding a custom fieldtype to your add-on is easy with the `make:fieldtype` comma
 
 ```
 $ php system/ee/eecli.php make:fieldtype
-compatiblity
+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!
 ```
 
-Follow the prompts to complete the setup of your custom fieldtype.
+This will create a `ft.[fieldtype_name].php` in your add-on's folder. In the example above, this creates a file named `ft.amazing__fieldtype.php`.
 
+```
+amazing_add_on
+ ...
+┣ ft.[fieldtype_name].php
+┗ ...
+ ```
 
 ## Basic File Structure
 
-Once generated via the CLI a file named `ft.[addon_name].php` will created in your add-on's folder. All fieldtypes must inherit from the `EE_Fieldtype`.
+All fieldtypes must inherit from the `EE_Fieldtype` base class and they must provide an `$info` array with a name and version number.
 
     <?php if ( ! defined('BASEPATH')) exit('No direct script access allowed');
 
@@ -59,7 +69,7 @@ Once generated via the CLI a file named `ft.[addon_name].php` will created in yo
     /* End of file ft.google_maps.php */
     /* Location: ./system/user/addons/google_maps/ft.google_maps.php */
 
-NOTE: **Note:** All add-ons are required to have an [addon.setup.php file](development/addon-setup-php-file.md). This is where Fieldtypes can declare their compatibility with other Fieldtypes, allowing a site builder to switch an existing field to another compatible type, e.g. _text_ can be switched to _email_ and vice-versa. Please see [Fieldtype Compatibility Options](development/addon-setup-php-file.md#fieldtypes) for more details.
+NOTE: **Note:** Fieldtypes can declare their compatibility with other Fieldtypes in the `addon.setup.php` file, allowing a site admin to switch an existing field to another compatible type, e.g. _text_ can be switched to _email_ and vice-versa. Please see [Fieldtype Compatibility Options](development/addon-setup-php-file.md#fieldtypes) for more details.
 
 NOTE: We also have [Example fieldtype with annotations](development/fieldtypes/example.md) for your reference.
 
@@ -558,3 +568,7 @@ Here are the usage details for this function:
 A jQuery object of the field being affected by the current event is passed to the callback function.
 
 NOTE: **Note:** Please refer to [Enhanced Fieldtype Features](development/fieldtypes/enhanced.md) page for advanced topics, such ad working with Live Preview, Entry Manager, Entry Cloning, File Picker and Conditional Fields.
+
+## Do Something: Build A Fieldtype
+
+For a complete fieldtype example see the [Google Maps Fieldtype example](/development/fieldtypes/example.md).

docs/development/fieldtypes/fieldtypes.md

@@ -110,7 +110,82 @@ If you needed to add more levels to your breadcrumbs you can chain them together
 This would add a breadcrumb that would look like `Add-Ons -> [Add-On Name] -> Settings -> Configuration`
 
 ### Sidebar
-TBD
+If your add-on has multiple Control Panel pages, a sidebar can be incredibly helpful for your users to easily navigate between pages. Sidebars can either be generated automatically or manually. 
+
+#### Automatically Generate Your Sidebar
+We can use the `make:sidebar` CLI command to generate a sidebar file for us. 
+
+```
+$ php system/ee/eecli.php make:sidebar
+What add-on is the sidebar being added to? [amazing_add_on]:  amazing_add_on
+Building sidebar.
+Sidebar created successfully!
+```
+
+This will create the file `Mcp/Sidebar.php` in your add-on's folder.    
+
+```
+amazing_add_on
+┣ Mcp/
+┃ ┣ Sidebar.php
+┗ ...
+```
+
+**Note:** An add-on can only have one sidebar file.
+
+Inside of our `Sidebpar.php` file we'll have the following:
+
+```
+<?php
+
+namespace ExpressionEngineDeveloper\AmazingAddOn\Mcp;
+
+use ExpressionEngine\Service\Addon\Controllers\Mcp\AbstractSidebar;
+
+class Sidebar extends AbstractSidebar
+{
+    public $automatic = true;
+
+    /**
+     * @param false $id
+     * @return AbstractRoute
+     */
+    public function process()
+    {
+    }
+}
+```
+
+That's it! Our `Sidebar` class will scan our `Mcp` folder for all available Control Panel routes and automatically create respective entries in our sidebar. There's no need to add the sidebar to your Control Panel page as it will automatically be added when the page is rendered. 
+
+Example:
+
+With an add-on folder like this:
+
+```
+amazing_add_on
+┣ Mcp
+┃ ┣ Configurations.php
+┃ ┣ Settings.php
+┃ ┣ Licenses.php
+┃ ┣ Index.php
+┃ ┗ Sidebar.php
+┗ ...
+```
+
+Would produce a sidebar in the Control Panel like this:
+
+![control panel sidebar](_images/addon_sidebar_start.png)
+
+
+You can take this a step further by adjusting the following properties in your `Mcp` files to adjust how sidebar items are displayed:
+- **`protected $sidebar_title (string)`** - By default the sidebar link text is based on your route's name. This property will overwrite the text displayed for this route.
+- **`protected $sidebar_icon (string)`** - The Font Awesome icon you wish to display next to the sidebar link for this route.
+- **`protected $sidebar_is_folder (bool)`** - 
+- **`protected $sidebar_is_list (bool)`** - 
+- **`protected $exclude_from_sidebar (bool)`** - Exclude this route from the sidebar.
+- **`protected $sidebar_divider_before (bool)`** - Inserts a divider in the sidebar before 
+- **`protected $sidebar_divider_after (bool)`** - 
 
 ### Toolbar
 

docs/development/modules.md

@@ -140,7 +140,7 @@ If the data returned is of *Array* type, it is being passed to ExpressionEngine
 
     public function index()
     {
-        if (ee('Request)->isPost()) {
+        if (ee('Request')->isPost()) {
             //handle form submission
             return ee()->output->send_ajax_response(['success']);
         }