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

# Home 🏠

Welcome to Blup docs, your comprehensive resource for all things related to the inner workings of Blup!

<table data-view="cards"><thead><tr><th align="center"></th><th></th><th></th></tr></thead><tbody><tr><td align="center"><a data-mention href="/wiki/design-ui.md">Design (UI) ✏️</a></td><td></td><td></td></tr><tr><td align="center"><a data-mention href="/wiki/logics.md">Logics ⚡</a></td><td></td><td></td></tr><tr><td align="center"><a data-mention href="/wiki/backend.md">Backend 🔗</a></td><td></td><td></td></tr><tr><td align="center"><a data-mention href="/wiki/blup-code-editor.md">Blup Code Editor</a></td><td></td><td></td></tr><tr><td align="center"><a data-mention href="/wiki/publish-to-stores-ship.md">Publish to stores 🚀(Ship)</a></td><td></td><td></td></tr><tr><td align="center"><a href="https://www.youtube.com/watch?v=QHQiDpPJYcQ&#x26;list=PLMXGDzhAj1zuUJa2AN4zONbqOnAtLmhTL&#x26;ab_channel=Blup">Youtube Tutorials ▶️</a></td><td></td><td></td></tr><tr><td align="center"><a href="https://blup.in/downloads">Download Blup ⬇️</a></td><td></td><td></td></tr></tbody></table>

## Guide to Blup documentation

This section is an overview of Blup docs.

Blup consists of three major sections that are as follows:

1. **Design:** This is where the magic happens! In **Design**, you create stunning user interfaces (UIs) for your apps. With complete flexibility, you can design and customize every aspect of your app’s look and feel. It’s the heart of your Blup applications.
2. **Logics:** Once you’ve crafted your UI, it’s time to add logic. Logics is a powerful logic system where you create interactions and backend functionality. You’ll find a wide range of [nodes](/wiki/logics/ui-nodes.md), from simple variables to SDKs hosted on [pub.dev](https://pub.dev). Build dynamic and responsive apps by connecting your designs to logic seamlessly.
3. **Backend:** Need a backend? **Backend** has got you covered. Built on top of AWS, it provides a pre-built backend system with SQL-like queries. You can create real-time applications like chat apps or collaboration tools effortlessly. **Backend** is fast, reliable, and easy to use.
4. **Code Editor:** Wants more customization?  Let’s dive into the **Code Editor** – your gateway to more customization and fine-tuning in Blup. With the Code Editor, you can write code, edit native files, and seamlessly connect with your app’s UI.&#x20;

To make the most of Blup, follow this order:

1. [**Design**](/wiki/design-ui.md): Master the art of UI design.
2. [**Logics**](/wiki/logics.md): Dive into logic creation.
3. [**Backend**](/wiki/backend.md): Explore the backend capabilities.

### YouTube: Complete Beginners Series to Blup. \[Playlist]

If you prefer video tutorials, check out our **Complete Beginners Series to Blup** on YouTube.

{% embed url="<https://youtube.com/playlist?list=PLMXGDzhAj1zuUJa2AN4zONbqOnAtLmhTL>" %}
Beginners Series to Blup. \[Playlist]
{% endembed %}

We’re also planning to release videos featuring full production-ready apps, so stay tuned!

Happy Blupping! 🚀🎨🔌


---

# 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://docs.blup.in/readme.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.
