# Creating Extensions

Because extensions are basically separated app folders there really is no limit to what you can build with them. You could write a media manager extension or a notification handler extension which you can re-use on different Platform 2 applications.

## Using The Workshop Extension {#using-the-workshop-extension}

The easiest way to get started with an extension is to create one though the Workshop extension. To get started browse to `admin/operations/workshop` in your Platform 2 back-end.

You'll notice a series of input fields which will be needed to generate your extension files. We'll go over each one of them.

**Author name and email**

These will be used in your `composer.json` file under the `authors` key.

**Vendor and Name**

These define the namespace for your extension. The Vendor name is a unique identifier like your company or application name. The Name is of course your extension's main name (f.e. `Media` or `Notifications`).

**Description**

Your extension's description.

**Dependencies**

A list with other extensions on which your extension depends on. List them below eachother as `vendor/name`.

**Prepopulating Components**

You can choose to have the Workshop generate some standard files for you like a basic configuration file, some controllers or theme views to get you started with your extension. If you don't want this just leave the checkboxes blank.

**Installation**

After filling in the fields, you can choose to install your extension automatically or manually.

Automatic install will install the component in the workbench directory in your application root. Make sure the folder exists and is writeable before you attempt this.

You can also choose to download a zip file of your generated extension and install it manually in the extensions or workbench directory.


## Manually Creating Extensions {#manually-creating-extensions}

Manually creating an extensions takes a bit more work. There are two required files for creating extensions: the `composer.json` file and the `extension.php` file.

See [requirements]({url}/extensions#requirements) for more info.


## Enabling an Extension {#enabling-an-extension}

After that your extension is added to the extensions folder you can install and enable it through the admin back-end under the operations section. Your extension will be listed amongst the other extensions. Click the edit button to install and enable your extension.

Remember that you can always go back here to disable or uninstall your extension.


## Registering Widgets {#registering-widgets}

Widgets can be used to provide small pieces of views which can be easily re-used throughout your application or extension.

If you want to register a small widget but don't want to create a class for it you can do it directly in the `extension.php` file.

	'widgets' => array(
		'foo' => function ()
		{
			// return content.
		}
	),

If you'd like to create a separate class for the widget to have some extra functionality you can create a class in the `widgets` folder. By default, Platform 2 will register your widgets by using your class name as the widget key. You can override this by registering the widget in the `extension.php` file.

	'widgets' => array(
		'foo' => 'My\Widget\Namespace\Foo@someMethod',
	),

For more info on creating widgets see [the widgets documentation]({url}/usage/widgets).