> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/example-gallery/how-to-guides/qa-showcase-and-example-project.md).

# Q\&A Showcase and Example Project

This example Assessment Framework project provides a visual display of different question and answer types, including radiolists, checklists, dropdowns, text, numeric and date inputs.

It can also be used as a Designer reference for how to configure the part editor fields to achieve a specific question type and layout.

Download the project into your Designer, and run the project in TEST.

Different question types are organized in TABS in the runtime, and correspond to a logicnet the forms folder of the project.

## Attachments

{% file src="/files/akWvdr1WZmVQK84nQt9v" %}
ASF Q and A Showcase 745.zip
{% endfile %}

{% file src="/files/lzv9xgv4GDGa8BZ02QDy" %}
ASF Q and A Showcase v746 v8.zip
{% endfile %}

{% file src="/files/mN3sGgAbmthD6Y0BMerS" %}
ASF Q and A Showcase v8.3.zip
{% endfile %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/example-gallery/how-to-guides/qa-showcase-and-example-project.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.