# Control Deliverable Projects

You use a control deliverable project when you want to build Java controls that will be distributed to multiple users. A control deliverable project supports automatic integration of help and samples you provide with your Java control.

The difference is that a control deliverable project includes a "docs" folder with "help" and "samples" subfolders that include folder hierarchies to support automatic integration with the user's WebLogic Workshop installation. When you are ready to test or distribute your control deliverable, you can easily build a control deliverable by right-clicking the project name, then clicking Build Control Deliverable.

To create a control deliverable project

1. Right-click the application, point to New, then click Project.
2. In the New Project dialog, in the left pane, click All. In the right pane, click Control Deliverable Project.
3. In the Project name box, enter a name for your new project, then click Create.

WebLogic Workshop will create a new project with the name you gave it. If you expand the project folders to see it contents, you'll notice the docs folder and its subfolders. For example, if you created a project called "MyControls", you'll see something like this:

After creating the project, you should be sure to rename the VendorName folders to a name that clearly describes your company and product. Keep in mind that your control's users may have many controls installed from various sources.

Documentation and samples you add should go into the hierarchy provided. For more information on including documentation, see Help Authoring Guide.

When you build a control deliverable from this project, the resulting ZIP file won't contain the docs folder. Its top-level contents will include the help folder and its subfolders, the samples folder and its subfolders, along with your control implementation JAR.

For information about how a control deliverable is used in WebLogic Workshop, see Packaging Controls for Installation.

## Help in Languages Other than English

Note that the "en" folder is a <language> folder as described in Help Authoring Guide. If you translate your documentation into other languages, you must create a different <language> folder for each, along with child folders as shown here. For example, if you provide Japanese documentation, you would have a hierarchy such as docs/help/doc/ja/partners/<vendor_name>/*

Related Topics

None.