> For the complete documentation index, see [llms.txt](https://docs-wieldy.g-axon.work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-wieldy.g-axon.work/get-started/package-content.md).

# Package Content

Once you download the zipped folder from your [**Themeforest** ](https://themeforest.net/user/g-axon/portfolio)account and extract that. You will get the folder like below:

#### Wieldy-4.x <a href="#jumbo-7.x" id="jumbo-7.x"></a>

Inside this folder, you will receive following sub-folders and files:

1. **design-files/** In this folder you will find the Figma Design files for all of the screens being shown in the demo of Wieldy.
2. **source-code/** In this folder you will find all source code related files. Following are the zip files you will find inside of that.
   * **vite-demo.zip**:

     The Jumbo Vite version for SPA with all the pages shown in the demo.
   * **vite-starter-template.zip**:

     A minimal version required to start a new project to build SPA.
   * **nextjs-demo.zip**:

     NextJS 14 with App Router template with the demo provided.
   * **nextjs-starter-template**

     A minimal version required to start a new project using NextJS.
3. **CREDITS.txt** Lists credits to all the the great work done by others which we have incorporated into Wieldy
4. **LICENSE.txt**
5. **README.txt**


---

# 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:

```
GET https://docs-wieldy.g-axon.work/get-started/package-content.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.