# Page Not Found

The URL `files/baSNT0ni14VMVLeD15Jn` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [사이트 편집 에디터](https://supportcenter.creatorlink.net/creatorlink/site-building/edit_site/site_editor.md)
- [도메인 연결하기](https://supportcenter.creatorlink.net/creatorlink/site-building/connect_domain.md)
- [모바일 최적화 디자인 설정하기](https://supportcenter.creatorlink.net/creatorlink/site-building/edit_block/menu_block/optimized_mobile_design.md)
- [페이지 추가하기](https://supportcenter.creatorlink.net/creatorlink/site-building/edit_site/menu_setting/undefined.md)
- [템플릿 없이 사이트 제작하기](https://supportcenter.creatorlink.net/creatorlink/site-building/edit_site/templage/blank_template.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter, and the optional `goal` parameter:

```
GET https://supportcenter.creatorlink.net/creatorlink/site-building/edit_site/site_editor.md?ask=<question>&goal=<end_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://supportcenter.creatorlink.net/creatorlink/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://supportcenter.creatorlink.net/creatorlink/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/creatorlink/site-building/edit_site/site_editor.md`).

You may also use `Accept: text/markdown` header for content negotiation.