actualNoteContentPart: # Plugin API Reference Documentation: Plugin creation
  To create a plugin, you'll need a note that contains two things: a table of plugin information, and a code block containing the Javascript code of the plugin.
  
  
  
  
  
  ## Metadata table
  A plugin metadata table contains (at least) two columns: the name of the setting, and a value for the setting. 
  
  | setting name | setting value | 
  The setting name is not case sensitive. All columns are interpreted as strings.
  
  ### name
  The only required setting is the name of the plugin, which can be defined as:
  
  | name | Plugin name here | 
  This is the name that the user will see when invoking the plugin, and will be used as a prefix in cases where the plugin defines multiple options presented to the user.
  
  ### icon
  The name of a [Material Design Icon](https://fonts.google.com/icons?icon.set=Material+Icons)  that will be used to identify the plugin. If not provided, a generic "extension" icon will be used.
  
  | icon | search | 
  
  ### description
  A short description shown when installing or configuring a plugin.
  
  | description | Count the number of words in a note. | 
  
  ### instructions
  More detailed information about using the plugin that will be shown if the plugin is published to the [Plugin Directory](https://www.amplenote.com/notes/dda36f2a-ceae-11ed-898c-76979436bcb1) .
  
  | instructions | Here are some helpful words of advice on using this plugin:1. Instruction one2. Instruction two3. Instruction three | 
  
  ### setting
  Defines settings that the user can provide to configure the plugin. The user will be able to supply a string for each setting when configuring the note as a plugin. When plugin code is invoked, it has access to the settings values that the user has provided. All setting values are provided as strings.
  
  | setting | API Key | 
  
  This setting name can be repeated multiple times to define multiple settings.
  
  | setting | API Key | 
  | setting | Name |
processedNoteContent: ---
  title: Plugin Creation: Define settings, name and meta...
  tags: 
  headers: # Plugin API Reference Documentation: Plugin creation
  ---
  Plugin API Reference Documentation: Plugin creation
  To create a plugin, you'll need a note that contains two things: a table of plugin information, and a code block containing the Javascript code of the plugin. 
  Metadata table
  A plugin metadata table contains (at least) two columns: the name of the setting, and a value for the setting. | setting name | setting value |
  The setting name is not case sensitive. All columns are interpreted as strings. 
  name
  The only required setting is the name of the plugin, which can be defined as: | name | Plugin name here |
  This is the name that the user will see when invoking the plugin, and will be used as a prefix in cases where the plugin defines multiple options presented to the user. 
  icon
  The name of a [Material Design Icon](https://fonts.google.com)`
    that will be used to identify the plugin. If not provided, a generic "extension" icon will be used. | icon | search | 
  description
  A short description shown when installing or configuring a plugin. | description | Count the number of words in a note. | 
  instructions
  More detailed information about using the plugin that will be shown if the plugin is published to the [Plugin Directory](https://www.amplenote.com)`
   . | instructions | Here are some helpful words of advice on using this plugin:1. Instruction one2. Instruction two3. Instruction three | 
  setting
  Defines settings that the user can provide to configure the plugin. The user will be able to supply a string for each setting when configuring the note as a plugin. When plugin code is invoked, it has access to the settings values that the user has provided. All setting values are provided as strings. | setting | API Key | This setting name can be repeated multiple times to define multiple settings. | setting | API Key |
  | setting | Name |
noteTitle: Plugin Creation: Define settings, name and metadata for a plugin