Updated README

Author: wpgodone

README.md

@@ -79,6 +79,33 @@ When you first run the dashboard, you should go to the "Settings" tab to configu
 - WCM Design Folder: The parent folder for WCM design libraries. Each child folder represents one WCM library, with children for Components and Presentation Templates. To get any WCM library from the server, click the “Libraries” button.
 - Servers - Name, User, Password, Host, Port, Content Handler, Secure: Set these for your Portal server. You can have multiple server configurations and select the configuration to use. If you are using a Virtual Portal, include the Virtual Portal name as part of the "Content Handler" path, like this: /wps/mycontenthandler/my_vp_name. Set the "Secure" option if the specified port is an HTTPS port.
 
+## Pushing Script Portlet Applications
+After setting a folder for Script Portlet applications in the settings tab, the
+toolkit provides a graphical interfaces for pushing script portlet applications.
+Pressing the "push" button will invoke the [`sp` command](http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/script/script-portlet/cmd_line_push_ovr.dita?lang=en) and push the 
+application to the active server specified in the settings. If a `sp-config.json`
+file exists, it will be used when pushing the application. Pressing Tthe gear button
+will open a dialog for editing the application's `sp_config.json` file.
+
+In the same dialog box (at the bottom), there is an option to set a pre-push command
+which can be used for minifying javascript, transpiling coffeescript, SASS, etc., 
+running a gulp or grunt build process, or launching other tools. This command will
+be run from the application's directory and will be run when pressing the push button
+or when the application's folder is being watched.
+
+## Testing and Linting Script Portlet Applications
+Pressing the "SP Lint" button will run a linting utility for Script Portlet that
+will analyze the script portlet application and detect possible issues in the 
+code where it is recommended to follow best practices.
+
+Pressing the run button will runt the script portlet on a test server and open it
+in your browser. Although not complete, the test server locally simulates a Portal environment:
+- Common WCM tags are replaced with mock data. A complete list of tags that replaced
+  with mock data can be found [here](https://github.com/OpenNTF/WebDevToolkitForDx/blob/master/digexp-sp-server/tag-replacements.json)
+- AJAX requests that use Portal's Ajax proxy will be sent through a local proxy.
+  The test server supports the ResourceURL tag and URLs that use "/wps/proxy/"
+- Other tags are removed and won't appear in the html.
+
 # Using the"dxwcmdesigns"  command line utility
 Note that all the functionality for push/pull of WCM design files is available from the Dashboard user interface. For the command line support, use:
 ```
@@ -172,4 +199,4 @@ There are some options that can be set to control some of the behavior when down
 - trial: if set any new features that have been added but not fully testes are added
 - include: This is an array of item types that allows you to limit the types of items that will be included in the pushed/pull actions for this library, this list will only support types that are handled by default. It allows you to limit the types to a subset of the supported types.  i.e. Some one that only works on icons could limit it to "LibraryImageComponent"
 
-To turn on the trial features for all libraries you can set an environment variable DIGEXP_TRIAL=true.
+To turn on the trial features for all libraries you can set an environment variable DIGEXP_TRIAL=true.

digexp-sp-server/README.md

@@ -1,8 +1,15 @@
 # Simple test server for Script Portlet with mock implementations of WCM tags
 
-This is a simple implementation of a web server that provides mock implementations of portal-specific features. It provides simple removal or replacement of WCM tags. The list of tag substitutions comes from the tag-replacements.json file.
+This is a simple implementation of a web server that provides mock implementations 
+of portal-specific features. It substitutes common WCM tags with mock data and
+removes others. The list of tag substitutions comes from the tag-replacements.json
+file. In addition, the server provides support for handling ResourceURL tags for
+generating urls for Portal's Ajax proxy.
 
-This test server is used by the Web Developer Dashboard part of this toolkit when you click the "Run" button for a script application. It's installed automatically when you install the dashboard, so typically you don't need to use the installation described below.
+This test server is used by the Web Developer Dashboard part of this toolkit when
+you click the "Run" button for a script application. It's installed automatically 
+when you install the dashboard, so typically you don't need to use the installation
+described below.
 
 ## Installation
 To install:
@@ -42,4 +49,4 @@ var serverInstance = spAppServer.start(spAppFolder, port);
 
 // ... later, close the port when finished
 serverInstance.close();
-```
+```