> For the complete documentation index, see [llms.txt](https://docs.wizeddev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wizeddev.com/wizeddev-docs.md).

# WizedDev Docs

The Official Open Source Resource

Welcome to our treasure trove of Wized PowerUps. This isn't just another "How To" Wized documentation - it's your go-to guide for making the most out of Wized's potential, without having to get stuck at writing complex code yourself.

{% hint style="info" %}
**This library works only with Wized Embed 2** (Latest Update: March 12th 2024)
{% endhint %}

* View all Set by Step Tutorials: <https://www.youtube.com/@WizedDev>
* View all Free Clonables: <https://webflow.com/@theip>

<details>

<summary>Support, Free Help &#x26; Paid Consultations</summary>

1. If you have any further questions about Wized, please feel free to reach out to the Official Wized Support Team via their Support Chat: <https://www.wized.com/support>
2. If you are encountering an obstacle but time is on your side, simply request a Free Custom Tutorial and I will get back to you. -> **Tutorial Request Form**
3. If you're encountering roadblocks in your Wized Project and need a helping hand urgently, 1-on-1 consultations are available ASAP. -> **View my Rates**

</details>

### Free Wized Community Resources 💛


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.wizeddev.com/wizeddev-docs.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 `build a script that syncs our docs to a CMS` 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.
