Make building and packaging different processes for clarity

README.md

@@ -28,6 +28,19 @@ Contact us [https://cloudinary.com/contact](https://cloudinary.com/contact)
 
 Stay tuned for updates, tips and tutorials: [Blog](https://cloudinary.com/blog), [Twitter](https://twitter.com/cloudinary), [Facebook](https://www.facebook.com/Cloudinary).
 
+## Development
+
+### Create a Plugin Release Package
+
+Run `npm run package` to create the plugin release in the `/build` directory and package it as `cloudinary-image-management-and-manipulation-in-the-cloud-cdn.zip` in the root directory.
+
+### Deployment to WordPress.org
+
+1. Tag a release from the `master` branch on GitHub.
+
+2. Run `npm run deploy` to deploy the version referenced in the `cloudinary.php` file of the current branch.
+
+3. Run `npm run deploy-assets` to deploy just the WP.org plugin assets such as screenshots, icons and banners.
 
 ## License #######################################################################
 

gruntfile.js

@@ -59,7 +59,7 @@ module.exports = function( grunt ) {
 	} );
 
 	grunt.registerTask(
-		'build', [
+		'package', [
 			'clean',
 			'copy',
 			'compress',
@@ -68,7 +68,7 @@ module.exports = function( grunt ) {
 
 	grunt.registerTask(
 		'deploy', [
-			'build',
+			'package',
 			'wp_deploy',
 		]
 	);

package.json

@@ -10,6 +10,7 @@
 	"scripts": {
 		"dev": "cross-env webpack --mode=development --watch",
 		"build": "cross-env webpack --mode=production",
+		"package": "npm run build && grunt package",
 		"deploy": "npm run build && grunt deploy",
 		"deploy-assets": "grunt deploy-assets"
 	},