actualNoteContentPart: ## How can plugins impact editor performance?
  Plugins can not be setup to run every keystroke, and their impact on responsiveness will generally be limited to when you interact with them (via context menu, note menu, etc). 
  
  That said, plugins can potentially set up timers that could allow them to be executed after their time of invocation. 
  
  A careless or malevolent plugin author could hypothetically do things like create huge volumes of notes, or generate notes with more content than can be fit into memory. The impact on performance of misused plugins could be significant, but figures to be rare.
  
  ## If I wanted to build my own plugin, where best to start?
  Amplenote's implementation of plugins is different from predecessors in that we have all the data structures within a note to define a plugin. With previous apps, "building a plugin" has generally required some programming prerequisites: stuff like cursory knowledge of git and IDEs. Amplenote plugins don't require you to download an IDE or speak git. You need only speak the lingua franca of programming languages (Javascript) and have some idea of what could make your Amplenote experience more wonderful.
  
  Armed with an idea to improve your experience, the next step is to either [read our docs](https://www.amplenote.com/help/developing_amplenote_plugins) , or feed them to your AI interpreter of choice for summarization or code generation. If somebody would like to provide some sample code or screenshots that illustrate sending Amplenote's Plugin API to ChatGPT (GPT-3.5), we will post that in this reserved space:
  
  [it could be you!]
  
  ## What improvements are planned for plugins?
  Depending on how much interest our community shows in building plugins, we would be interested in improvements like:
  Add a button to code editor to validate whether the plugin is currently valid
  Make it easier to diff earlier versions of the plugin to the current version
  Allow more types of markdown to be parsed or exported back into notes
  Whatever people email us persuasively at hello@amplenote.com
  Plugins are soft launching in Q2 of 2023, so expect these aspirations to update with some frequency.
  
  ## Why should I build a plugin?
  Besides the benefit of helping yourself get more done, there could be more benefits to creating a popular plugin, such as:
  Recognition and appreciation from Amplenote's GSD-oriented faithful
  Could ask community or Amplenote itself to sponsor your efforts if your plugin becomes popular
  What better way to learn to code than to experiment writing code in a syntax-highlighted editor within your note app? Building your own plugin is as simple as pasting into a new note.
  As of Q2 2023 it is the earliest days of plugins, so the good ones that are built before late 2023 will have an early advantage in gaining attention
  Nobody is an expert in creating AI prompts; if you can identify tasks you regularly undertake that aren't yet automated, why not make a plugin?
processedNoteContent: ---
  title: Installing & Using Amplenote Plugins
  headers: ## How can plugins impact editor performance?
  ---
  How can plugins impact editor performance?
  Plugins can not be setup to run every keystroke, and their impact on responsiveness will generally be limited to when you interact with them (via context menu, note menu, etc). That said, plugins can potentially set up timers that could allow them to be executed after their time of invocation. A careless or malevolent plugin author could hypothetically do things like create huge volumes of notes, or generate notes with more content than can be fit into memory. The impact on performance of misused plugins could be significant, but figures to be rare. 
  If I wanted to build my own plugin, where best to start?
  Amplenote's implementation of plugins is different from predecessors in that we have all the data structures within a note to define a plugin. With previous apps, "building a plugin" has generally required some programming prerequisites: stuff like cursory knowledge of git and IDEs. Amplenote plugins don't require you to download an IDE or speak git. You need only speak the lingua franca of programming languages (Javascript) and have some idea of what could make your Amplenote experience more wonderful. Armed with an idea to improve your experience, the next step is to either [read our docs](https://www.amplenote.com)`
   , or feed them to your AI interpreter of choice for summarization or code generation. If somebody would like to provide some sample code or screenshots that illustrate sending Amplenote's Plugin API to ChatGPT (GPT-3.5), we will post that in this reserved space: [it could be you!] 
  What improvements are planned for plugins?
  Depending on how much interest our community shows in building plugins, we would be interested in improvements like:
  Add a button to code editor to validate whether the plugin is currently valid
  Make it easier to diff earlier versions of the plugin to the current version
  Allow more types of markdown to be parsed or exported back into notes
  Whatever people email us persuasively at [hello@amplenote.com](null)`
  
  Plugins are soft launching in Q2 of 2023, so expect these aspirations to update with some frequency. 
  Why should I build a plugin?
  Besides the benefit of helping yourself get more done, there could be more benefits to creating a popular plugin, such as:
  Recognition and appreciation from Amplenote's GSD-oriented faithful
  Could ask community or Amplenote itself to sponsor your efforts if your plugin becomes popular
  What better way to learn to code than to experiment writing code in a syntax-highlighted editor within your note app? Building your own plugin is as simple as pasting into a new note.
  As of Q2 2023 it is the earliest days of plugins, so the good ones that are built before late 2023 will have an early advantage in gaining attention
  Nobody is an expert in creating AI prompts; if you can identify tasks you regularly undertake that aren't yet automated, why not make a plugin?
noteTitle: Installing & Using Amplenote Plugins