> For the complete documentation index, see [llms.txt](https://learn.adaptcms.com/adaptcms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.adaptcms.com/adaptcms/core-packages/plugins.md). # Plugins Like Fields, Plugins reside in the root `/packages` folder. Unlike fields, plugins are like mini-apps within your site. UI vue components, routes, controllers, models, commands - anything that Laravel supports is usable within a plugin. They could be used to add a feature, or to add a layer to the CMS fit for the specific website in mind. When creating, or editing a plugin, there is an option to "Publish". As long as a valid GitHub URL is entered, we will update that GitHub repo with the files that reside in the Plugin path. Another feature is the ability to search for a plugin from the AdaptCMS.com Marketplace. You may view the plugin on the marketplace, or even choose to install it directly to your website. --- # 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://learn.adaptcms.com/adaptcms/core-packages/plugins.md?ask=&goal= ``` `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.