> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/contributing-content/contribution-demo-preparation.md).
# Contribution demo preparation
A demo is the last stage required before the contribution is merged into the content internal repo. To be as prepared as possible and to avoid post-demo change requests, review all of the steps below.
{% hint style="info" %}
### Note
A contribution demo is not required for community-supported content packs.
{% endhint %}
#### General notes
* The purpose of the demo is to verify the contribution meets Cortex XSIAM standards and to check that features work as expected, while providing a satisfactory user experience.
* The contributor, the PR reviewer, and in some cases a security reviewer, participate in the the demo.
* The demo can take up to one hour.
#### Before the demo
* Verify the change requests from your code review are fully addressed and fixed.
* Prepare a Cortex XSIAM tenant that has all recent changes and has the most updated version of your content pack. The demo is performed in this environment.
#### Demo agenda and workflow
The following may vary based on the size and scope of the contribution.
| Section | Description |
| ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Product Overview | Short general explanation about the product. |
| Use Cases Overview | The specific use cases for the customer. |
| Integration Commands Overview | Review which commands are implemented. |
| Demo Integration Instance Configuration | - Verify it's clear how to retrieve required credentials.
- Verify correct error handling - what happens when credentials are incorrect.
|
| Demo Integration Commands | Verify that commands, arguments, and outputs (including descriptions) are according to standard:
|
| Demo Fetch Incidents (if applicable) | Verify that incidents are fetched and displayed correctly. |
| Demo Playbooks (if applicable) | Verify that playbooks run as expected. |
| Review Layouts, Alert and Indicator Types, Alert and Indicator Fields, and Classifiers (if applicable). | - Verify layout is bound to incident/indicator type.
- Verify alert/indicator fields are bound to alert/indicator types.
- Verify classifier is bound to incident type.
- Verify playbook is bound to an incident type.
|
#### After the demo
* If changes were requested during the demo by the reviewers, make and commit these changes.
* After all requested changes are made, the PR is merged.
---
# 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://cortex-docs.paloaltonetworks.com/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/contributing-content/contribution-demo-preparation.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.