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

# How it works

1. Pick a template – You can choose from a series of different clean, responsive layouts that instantly give your site a polished and professional look. You don't need a high level of expertise or design degree.
2. Edit visually – It’s smooth and intuitive, all you just need to do is to click, type, drag. It’s just like making a slide, but what you’re building lives on forever.
3. Connect wallet – Your wallet is your key, the moment you connect, what you create becomes yours. No middlemen, no permission needed.
4. Publish – One click, and your site is live. Immutable, censorship-resistant and fully yours.
5. Link ENS – Turn your yourname.eth into a full-fledged website. Share it like you’d share your Twitter handle.

#### Templates & Use Cases

* Portfolios for artists, devs, nft curators; showcase your work in style.
* Token launch pages that make your project look legit from day one.
* Blog / coming soon / waitlist pages;  build anticipation the right way.
* Product showcases, NFT drops; make noise, stand out.

<figure><img src="/files/LkPbSDe3KdNe9J2Ub2ms" alt=""><figcaption></figcaption></figure>


---

# 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://websync.gitbook.io/websync/product-overview/editor.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.