> For the complete documentation index, see [llms.txt](https://devise.gitbook.io/cms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devise.gitbook.io/cms/readme.md). # Devise Development Documentation ## What is Devise? Devise is a package designed to harness the power of Laravel and make it easier for developers to provide get content managable sites up *incredibly fast*. By implementing Devise you give them the ability to utilize your design and code in ways that you didn't even imagine. Devise also leverages the power of VueJS allowing you to create dynamic and intellegent interfaces. [Learn More](http://devisephp.com) ## Notes about documentation Throughout the documentation we will reference yarn commands. However, you can usually interchange these with npm commands. We just happen to prefer yarn. ## Contributing We welcome pull requests and issues with open arms. However, please take a quick look at our contribution guidelines so that you can quick get up and running building Devise in the appropriate environment and so that your issues get resolved as quickly as possible. ## Legacy Versions If you are looking for the 1.x version of Devise take a look here: Link to the 1.x branch ## License Devise is available under the [MIT license](http://opensource.org/licenses/MIT). --- # 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://devise.gitbook.io/cms/readme.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.