> For the complete documentation index, see [llms.txt](https://docs.manyfast.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.manyfast.io/en/intro/undefined.md).

# Core Concepts

This chapter walks you through the core ideas behind the Manyfast editor.\
\
As the saying goes, "seeing is better than hearing a hundred times." The most reliable way to communicate is to "show it directly." Throughout the history of building IT products, teams have used all sorts of formats and methods to share their ideas with each other in the most direct way possible.

The problem is that those methods have multiplied so much that they've become complex and hard to use, often turning into an obstacle to communication instead of a help. The Manyfast editor takes a different approach so that everyone building a product can understand and share it more easily.

### IT products understood as graphs

The single most powerful tool in information visualization is the graph. Graphs are essential for showing relationships between pieces of data and making them easy to understand. When we want to give shape to vague, unclear ideas, we reach for a mind map — and a mind map is itself a kind of "graph," made up of "nodes" and "edges."

When designing an IT product, it's important to think about **how the components that make up the product relate to one another and how they should interact**. A graph is the best way to express this. That's why we made graphs the foundational format of the Manyfast editor.

### IT products assembled like blocks

Modern software development has embraced Component-Driven Development. The same applies to UI design through the Atomic Design System. Both share a common idea: assembling an entire product out of **reusable, minimal building blocks**.

This approach is excellent for maintenance. When you have ready-made pieces, you can tweak them slightly and reuse them, which is also great for moving fast. The one catch is that there's never a clear consensus on **how big each unit should be** — where one building block ends and another begins.

The Manyfast editor follows this development philosophy by letting you assemble and rearrange a product's components quickly, right from the planning stage. At the same time, to spare planners from agonizing over unit boundaries, we've defined the building blocks of an IT product around the patterns we see most often.

All you have to do is fill in the content for whatever your product needs. Manyfast will automatically classify that content into the right components and turn it into a polished plan.


---

# 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://docs.manyfast.io/en/intro/undefined.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.