Ok, your package is done and the only thing still preventing you from saving the world is getting it into the Rock Shop. Not to worry - submitting your plugin is a piece of cake! Just follow these simple steps.

1. Log in to the Rock website.
2. Select My Account from the user dropdown in the upper right of the page. This will take you to your user profile page on the Rock site.
3. Next select the organization that will be submitting the application. Most people will only belong to a single organization, but you could belong to several. This is helpful for those who operate as freelance ninjas at night.
4. Now you'll see your organization's profile page. To submit your package select the Edit Organization button then press the Packages link in the menu in the left sidebar.
5. You'll now see a listing of all the packages you have submitted to the Rock Shop. To add a new one press the [+] button in the grid footer.
6. This will allow you to submit a new package with the following fields.

1. Name:
This will be the name of your package that will be displayed in the Rock Shop.
2. HTML Description:
Don't skimp here. Take your time and explain what your package does and how it can help the organization. This is a good place to list any limitations also. Remember, even if this is a free package the customer is investing time looking at your package and installing it. Respect that by providing as many details as you can. Submissions that do not contain enough details will be rejected. Be sure to leverage HTML to present your description in a way that's easy to read.
3. Type:
There are a couple of different types of plugins you can submit. These include:

• Plugin: This is the most common. These include things like custom blocks, field types, workflow actions, etc.
• Themes: This option is for custom website themes you have developed.
• External Apps: Choose this option for applications that run outside of the Rock website. Most likely this will be used for client applications that run on the desktop or mobile devices.

4. Cost:
This field determines if your package is free or paid and, if applicable, what the cost is. Paid Rock Shop packages donating at a rate of 35% or more will be included in the "Sponsored Apps" section of the shop homepage.
5. Categories:
Next select up to two (one is fine too) categories that make sense for your package. We reserve the right to change these especially if/when we add new categories as the Rock Shop grows.
6. Package Icon:
This is an image that will be used in the Rock Shop. More details on the specifications of this image can be found below.
7. Support URL:
We require every package to have a support URL where customers can go to get help with your package.

------------------------------------------------------------------------------------------------------------------------------------

7. After creating the package, you must now create an initial version for it.

Adding A Package Version

1. Version:
This is the label you'll use to describe your version. We give you the flexibility to use any versioning scheme you prefer. Most people will use something like Version 1. See Package Versions for more details.
2. Description:
This field describes the specifics of the version. This is especially important for describing what's new in later versions. When filling this out for the initial version you may wish to include information about future features.
3. Required Rock Version:
Your package may not run on all versions of Rock. To limit who can install it, you will need to specify a minimum Rock version.
4. Package File:
This is where you'll upload the install package file that you created above.
5. Documentation URL:
This is where you'll link to the documentation about your package.
6. Post Install Instructions:
Once the customer has completed the install these instructions will be shown to point them toward what to do next.
7. Screenshots:
Nothing helps the customer understand your package as quickly as screenshots. You can upload as many as four different screenshots. Please upload at least one screenshot of your application. We suggest these screenshots be sized to 1280x960. Submissions without any screenshots will be rejected.

Package Icon Specifications

The package icon you submit must meet specific requirements to be included in the store. This single image will be used in several different places so it's important that you understand the requirements.

Package Icon Template

The image itself must be sized to 1365x210. The entire image will be displayed on the package details page of the store. The area shaded in red will be displayed when it's shown as an icon in a list of packages. Note, that this red section is not the exact size of the icon. Since the page is responsive the icon will grow and shrink in width depending on the browser width. The red area is more the target location for your icon.