# Introduction

HypaSites is an AI landing page and sales funnel builder. You answer an 8-step brief, the AI generates a fully custom HTML page, and you can publish it on a HypaSites subdomain or your own custom domain in a few clicks.

This documentation covers everything you need to use the platform: signing up, choosing a plan, building your first page, editing it, publishing, tracking performance, and managing your account.

## How to read these docs

The chapters are sequenced for a new user. If you're just starting out, read them in order. If you already have an account and just need to find one thing, jump straight to the relevant chapter from the sidebar.

* **Chapter 1 — Welcome** explains what HypaSites does and the core concepts (workspaces, projects, brand kits, pages).
* **Chapters 2–3** cover signup, billing, and plan selection.
* **Chapters 4–5** cover the dashboard, brand kits, and projects.
* **Chapters 6–8** cover the core build → edit → publish loop. These are the longest chapters because this is where you'll spend most of your time.
* **Chapters 9–10** cover analytics, account settings, and the bring-your-own API key option on Scale Without Limits.

## Conventions

When this guide says *"go to Dashboard → Pages"*, it means click **Dashboard** in the left sidebar, then **All Pages**.

Field names appear in **bold** (e.g. **Page Name**), button labels appear in **bold** as well, and form sections appear in headings.

If something on screen doesn't match what's described here, check that you're on the latest version of HypaSites and let support know.


---

# Agent Instructions: 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://hypasites.gitbook.io/hypasites-docs/readme.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.
