> For the complete documentation index, see [llms.txt](https://docs.codatum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codatum.com/getting-started/concept-further-reading/why-did-we-choose-block-editor-over-cell-based-editor.md).

# Why did we a choose Block Editor over Cell-based Editor?

At Codatum, we believe that data analysis should be flexible and easy to use without being limited by the tools we use. Our goal is to allow users to construct their thoughts and analyses as freely as they would in a notebook. By using a block editor, users can intuitively build their content and freely move blocks around, much like organizing thoughts in a memo pad. Furthermore, the block editor allows for continuous work with unified keyboard operations (including some special shortcuts for SQL execution, etc.). It is fundamentally constructed with the same text format, enabling users to stay focused on their work without interrupting their thought process.

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

Since the 2000s, block editors like Evernote and Notion have evolved rapidly. These modern interfaces offer an unparalleled combination of intuitive operation and flexibility, allowing users to manage their thoughts effortlessly.

While cell-based editors have their own advantages, such as clear segmentation of code and outputs, they present a slightly older approach. This method can sometimes disrupt the flow of thought by imposing a rigid structure. Additionally, cell-based editors are often weaker in real-time collaboration, making it difficult for teams to work together effectively.

Data analysis is not something that is done alone; it involves working together and sharing knowledge. At Codatum, we prioritize real-time collaboration. By adopting a modern block editor approach, multiple users can edit the document simultaneously, with changes reflecting instantly and without conflicts, making teamwork smooth and efficient.

At Codatum, we have chosen the modern block editor approach to ensure that the thought process is smooth and that real-time collaboration is seamless. This allows our users to focus on their data analysis without unnecessary distractions, making the process as smooth and efficient as possible.


---

# 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://docs.codatum.com/getting-started/concept-further-reading/why-did-we-choose-block-editor-over-cell-based-editor.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.