> For the complete documentation index, see [llms.txt](https://tmniche-docs.keywordrush.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmniche-docs.keywordrush.com/core-concepts/blocks-and-formats.md).

# Blocks & formats

TMN doesn't pour an article out of a single template. It assembles each one from small building **blocks** — so no two articles share a fixed skeleton, and commercial blocks are placed by strategy rather than pasted on at the end. Think Lego, not templates.

## Three block families

Every article is composed from blocks in three families:

* **Editorial blocks** — the prose and structure: intros, sections, key takeaways, FAQs, step lists, conclusions. No product or profile data.
* **Product blocks** — bound to a product (real, from your catalog, or AI-synthesized): product cards, comparison tables, pros & cons, rating breakdowns, where-to-buy.
* **Conversion blocks** — bound to a [profile](/core-concepts/profiles.md): CTA, pricing, testimonials, trust signals. These carry the monetization in lead-gen and SaaS articles.

Blocks are rendered by **Content Egg**. For the full catalog and what each block looks like, see the Content Egg docs: [EggBlocks introduction](https://ce-docs.keywordrush.com/egg-blocks/introduction) and the [block reference](https://ce-docs.keywordrush.com/egg-blocks/block-reference).

## Formats

A **format** is the kind of article — review, how-to, comparison, and so on. It's a genre *guideline*, not a rigid template: the AI decides the exact outline and block mix within the format's boundaries. TMN has **16 formats**, in two groups:

* **Product-first formats** — the article is built around products, so products are resolved **before** the outline is written. Examples: product reviews, roundups ("best of"), comparisons, alternatives, gift guides.
* **Content-first formats** — the content comes first; where product slots fit, they're filled afterward with products **relevant to that section**. Examples: how-tos, buying guides, troubleshooting, explainers, FAQs.

See the [Article formats](/reference/formats.md) reference for the full list.

## How blocks and formats come together

You don't place blocks by hand. For each article, the AI composes the block mix from three inputs:

* **Format** — sets the natural shape (a review reads differently than a how-to).
* **Intent** — money/mixed articles include commercial blocks; info articles stay editorial.
* **Monetization model** — decides whether the commercial blocks are product blocks or profile-driven conversion blocks.

A few blocks are simply switched on or off by your **Generation Preset** — for example price-comparison blocks, YouTube embeds, or the table of contents. Everything else is composed automatically.

## What you control

* **Per article** — set the **Format** and **Intent** in the node drawer; see [Edit your Topic Map](/building-a-site/edit-topic-map.md).
* **Which formats a plan may use** — in the new-plan wizard, under **Basics → Advanced settings → Allowed formats**, you can limit TMN to specific formats. **Leave it empty (recommended)** so TMN picks the best format for each topic.
* **Across a plan** — toggle optional blocks and writing style in your Generation Preset; see [Use presets](/building-a-site/presets.md).

![One generated article showing a mix of editorial and product blocks](/files/T3nF4XfSImc6Uhnxmf8q)


---

# 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://tmniche-docs.keywordrush.com/core-concepts/blocks-and-formats.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.