# Why Bloqs?

Bloqs is like a Fluid field, but on steroids. It gives you the freedom to build robust repeatable content modules using the [atomic design pattern](https://bradfrost.com/blog/post/atomic-web-design/). Functionally Bloqs shares more similarities with ExpressionEngine's native Grid field. Every row in the Grid field has the same custom field options because they all share the same columns. Think of Bloqs as a Grid field where each row has different columns, and you can place the rows in any order you want. 

If a Grid field has rows and columns, then a Bloqs field has bloqs and atoms. You create a bloq, then add one or more custom fields (aka atoms) to it, and then assign that bloq to one or more custom fields in a channel. Unlike the native Fluid field, since a single bloq contains multiple custom fields, those fields can work in conjunction with each other. One field can contain your text, the other one might be a select menu determining how that text is displayed. If you're using [nested bloqs](/bloqs/docs/features/nesting.md), the fields within a single bloq can be even more powerful as their values can cascade down to child bloqs.

![](/files/-MLwhGQkAUzRAvXUEoZP)


---

# Agent Instructions: 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.boldminded.com/bloqs/docs/why-bloqs.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.