> For the complete documentation index, see [llms.txt](https://research-amp.gitbook.io/research-amp-user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://research-amp.gitbook.io/research-amp-user-documentation/content-management-procedures.md). # Content Management Procedures Building out content for the site and maintaining it is the central work of Research AMP. This section of the documentation will walk you through some basic considerations for creating and maintaining the content types that are standard features of the Research AMP platform: research reviews, articles, profiles, the news feed, and events. Citations are covered under "Curating your Zotero Library." As noted in Content Management Tips, it is a good idea to develop a style guide, schedule, and workflow for posting all of these content types. We will go over some things you should consider as you develop your site's procedures for creating and posting content. Users are continually experimenting with more types of content, such as podcasts and audiovisual material, and this documentation will be updated with best practices for working with new types of content as this information becomes available. --- # 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://research-amp.gitbook.io/research-amp-user-documentation/content-management-procedures.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.