> For the complete documentation index, see [llms.txt](https://xoops.gitbook.io/xoops-modules-cookbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xoops.gitbook.io/xoops-modules-cookbook/introduction.md). # Introduction ## XOOPS Module Development **Before you start writing a module, ask few questions:** **1) Is there any similar module that will work for me?** If you can find a similar module maybe you can contribute in developing/ bug fixing that module instead of writing a module from scratch. for example there is a lot of content, gallery and download modules in XOOPS which you can use and develop more or customize for your needs. honestly i see no mean to write any more content module in XOOPS. **2) Is there any similar functionality in other modules which I could copy and use.** Maybe it seems odd but it will be good to announce in forums about your future plans for a module and your needs. Please explain what you want to do. Usually there are some modules with similar functionality which you can use in your module. If you didn't find any module that would address you need, and you decide to develop your own module, we hope that this document will make it easier for you. Please let us know if this **Module Developer Cookbook** was helpful, and if we could improve it. --- # 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://xoops.gitbook.io/xoops-modules-cookbook/introduction.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.