tab files and widgets

Author: Andy McCormick

docs/_images/dashboard_widget_example.png

@@ -199,6 +199,8 @@ The `Model` folder holds all models that we are creating with our add-on.
 The `widgets` folder holds all dashboard widgets we create with our add-on.
 
 ## 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. With the release of 6.4.x and 7.2.x this has been updated. The CLI has been updated to make creating add-ons and adding functionality incredibly easy. At the same time, the docs have also been updated to reflect the ideal workflow of creating an add-on. 
+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.   
 
-While the latest changes shift our view of add-ons and how developers will create add-ons, you may still come across add-ons using the old methodology. We have left much of the old methods and structure in place so that older add-ons will continue to work. However, we are choosing to not actively update the documentation for the old methods because we feel it's no longer in the best interest of the community to develop add-ons in this way. If you need to access how the docs once were regarding add-ons, you can reference the [legacy docs in GitHub](https://github.com/ExpressionEngine/ExpressionEngine-User-Guide/releases/tag/legacy-add-on-structure) (note that v7 and v6 were the same in these regards). 
+With the release of 6.4.x and 7.2.x this paradigm has been updated to reflect the idea that we are just creating add-ons, and those add-ons can have multiple types of functionality. The CLI has also been updated to make creating add-ons and adding functionality incredibly easy. We have also updated the docs to reflect the ideal workflow of creating an add-on. 
+
+While the latest changes shift our view of add-ons and how developers will create add-ons, you may still come across add-ons using the old methodology. We have left much of the old methods and structure in place in the core so that older add-ons will continue to work. However, we are choosing to not actively update the documentation for the old methods because we feel it's no longer in the best interest of the community to develop add-ons in this way. If you need to access how the docs once were regarding add-ons, you can reference the [legacy docs in GitHub](https://github.com/ExpressionEngine/ExpressionEngine-User-Guide/releases/tag/legacy-add-on-structure) (note that v7 and v6 were the same in these regards). 

docs/_images/structure_tab.png

@@ -14,25 +14,73 @@ lang: php
 
 # Adding Publish Layout Tabs
 
+
+## Overview
 Add-ons can also add tabs which are visible on in [Publish Layouts](control-panel/channels.md#publish-layouts). Respectivley these tabs would also be visible on the Entry Publish/Edit page if selected in the publish layout. Two things are required for your add-on to have this functionality:
-- [`tabs()` method](/development/add-on-update-file.md#add-publish-tabs-with-your-add-on-tabs) addded to the Update File
+- [`tabs()` method](/development/add-on-update-file.md#add-publish-tabs-with-your-add-on-tabs) added to the Update File
 - The Tab File (`tab.[addon_name].php`)
 
-## The Tab File (`tab.module_name.php`)
+Here is an example of the publish layout's tab for the Structure add-on:
+![structure tab](_images/structure_tab.png)
 
-**class `Add_on_name_tab`**
+## 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.
 
-To add Publish Tabs
+```
+amazing_add_on
+...
+┣ tab.amazing_add_on.php
+┗...
+```
 
-There are no required class variables. Because multiple modules may be adding fields to the publish page, all third party tab fields are namespaced using the package name when displayed on the publish page. This namespacing will be stripped prior to any data being returned to the tab functions.
+## The Tab File Structure
 
-NOTE: **Note:** if your module includes a tab, do not forget to indicate this in the update file when installing the module. Further, be sure to include the `tabs()` function in the update file, and use it when updating custom layouts on installation and uninstallation.
+```
+<?php
+
+class Amazing_add_on_tab
+{
+
+    public function display($channel_id, $entry_id = ''){
+
+        $settings = [
+            //array of settings
+        ]
+        return $settings;
+    }
+
+    public function validate($entry, $values){
+        $validator = ee('Validation')->make(array(
+            'amazing_field_one' => 'required',
+            'amazing_field_two' => 'required|enum[y,n]',
+        ));
+
+        return $validator->validate($values);
+    }
+
+    public function cloneData($entry, $values){
+
+        return $values;
+    }
 
-## Tab File Function Reference
+    public function save($entry, $values){
+
+    }
+
+    public function delete($entry_ids){
+
+    }
+    
 
-**class `Module_name_tab`**
+}
+```
+
+**class `Add_on_name_tab`**
+
+There are no required class variables. Because multiple modules may be adding fields to the publish page, all third party tab fields are namespaced using the package name when displayed on the publish page. This namespacing will be stripped prior to any data being returned to the tab functions.
+
+NOTE: **Note:** if your module includes a tab, do not forget to indicate this in the update file when installing the module. Further, be sure to include the `tabs()` function in the update file, and use it when updating custom layouts on installation and uninstallation.
 
-[TOC=3]
 
 ### `display($channel_id, $entry_id = '')`
 

docs/development/addon-development-overview.md

@@ -11,11 +11,14 @@
 
 [TOC]
 
-Along with the basic widgets which will come native with ExpressionEngine Pro, each third-party add-on can provide multiple widgets to show pertinent information to users.
+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.
+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.
 
-Users can also create widgets using ExpressionEngine template manager.
+TIP:Users can also create widgets using ExpressionEngine template manager without needing to create an add-on.
+
+Here is an example of the Dashboard Widget shipped with the SEEO add-on:
+![SEEO dashboard widget](_images/dashboard_widget_example.png)
 
 ## PHP Widgets