> For the complete documentation index, see [llms.txt](https://sitecoreuml.gitbook.io/sitecoredxg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitecoreuml.gitbook.io/sitecoredxg/architecture/plugins.md).

# Plugins

SitecoreDXG was specifically designed to make it easy for developers to extend and customize it to suit their needs, and the most straightforward way to make modifications and customizations is through *plugins*. 

Plugins are independent node modules with their own dependencies that follow a specific structure in order to satisfy a particular [*role*](/sitecoredxg/architecture/roles.md) of the SitecoreDXG ecosystem. There are two types of plugins supported by SitecoreDXG, natively: [*Trigger Plugins*](/sitecoredxg/architecture/plugins/trigger-sub-component.md), and [*Completion Handler Plugins*](/sitecoredxg/architecture/plugins/completion-handler-sub-component.md). 

Plugins are necessary because while SitecoreDXG was specifically built to be easily integrated into any CI/CD pipeline or automated process, there are always things that end-users might want to do differently or control based on their individual requirements. By enabling developers to write their own *trigger* and *completion handler* plugins, SitecoreDXG can be customized to suit nearly any need.

{% hint style="info" %}
By definition, plugins are technically [*components*](/sitecoredxg/architecture/components-overview.md), though they could be better described as *sub-components* of the SitecoreDXG Generation Service.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sitecoreuml.gitbook.io/sitecoredxg/architecture/plugins.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.