> For the complete documentation index, see [llms.txt](https://readme.directual.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://readme.directual.com/plugins/developing-plugins.md).

# Developing Plugins

🪚 Unlimited extension possibilities

Go to the **Home page** → **My plugins** to develop a plugin.

### General settings

General plugin settings like name, description, list of categories, header image.

Instructions should comprise a step-by-step description of how to use a plugin. This includes details on tasks such as acquiring an API key or managing the API response. These instructions will be displayed within a plugin modal window (as shown in the screenshot below).

### Shared Parameters

Shared parameters are set by the user while installing the plugin.

![One shared parameter — api key](https://3071851461-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4Nnmtk9_gFGWOddsf6%2F-Mfb6JxuZoSLOwgv9PF6%2F-Mfb9qKfpie-IgpUSUz1%2Fshared.png?alt=media\&token=34fb2644-6f11-4cf3-bb17-4daed746af1f)

###

### Elements

You can see an example where a component is developed using [Chart.js](/plugins/developing-plugins/developing-web-plugins/example-using-chart.js-in-directual.md) or a [simple form](/plugins/developing-plugins/developing-web-plugins/example-building-simple-form.md).

### Status & Actions

Apps, where the plugin is available — apps' system names, comma separated. Use that setting for using unpublished plugins.