# Structure Every Mburger project data model is composed of 3 main entities: * **Blocks**: a block is composed of *elements* and defines the feature data model within the project. Each block represents a specific feature defining its structure. * **Elements**: they are the basic elements with which to build the data model, forming a *block* structure. An element can be a text field, an image field, an address field and many others. * **Sections**: represents the data itself. A *section* belongs to a *block* inheriting its structure. A *block* can contain one or more *sections*. ### A Simple Sample A simple example can be building a News feature. First create a new *block* called News and define its structure using 3 *elements*: * a *text element*: the title of the news * an *image element*: an image associated with to the news * a *datetime element*: the date of the news Defined the News *block* structure, we can add one or more *sections*. Each section is a news with a title, image and a datetime. {% hint style="info" %} A block and its structure can only be created from the web dashboard (only **admin** and **developers** roles). Once a block is created, you can use APIs to create/update/delete sections. {% endhint %} --- # 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.mburger.cloud/api-docs-1/introduction/structure.md?ask= ``` 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.