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

# PART II : 해결책 - 디자인 에디터

기존 방식의 문제를 이해했다면, 이제 해결책을 살펴볼 차례입니다. 이 파트에서는 디자인 에디터의 핵심 개념과 도입했을 때 실제로 달라지는 3가지 혜택을 안내합니다.

***

### 이 파트에서 다루는 내용

* [디자인 에디터란? - 1분 개념 이해](/design-editor/solution/concept.md) - 위젯 방식의 핵심 개념과 기존 방식 비교
* [혜택 1 - 운영 주도권 회복](/design-editor/solution/control.md) - 코딩 없이 직접 편집하고 즉시 반영
* [혜택 2 - 기능 단위 유연 활용](/design-editor/solution/flexibility.md) - 에이전시와의 역할 분담 구조
* [혜택 3 - 비용 구조의 근본적 변화](/design-editor/solution/cost.md) - 장기 운영 관점의 비용 효율


---

# 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, and the optional `goal` query parameter:

```
GET https://godomall-help.nhn-commerce.com/design-editor/solution.md?ask=<question>&goal=<endgoal>
```

`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.

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.