> ## Documentation Index
> Fetch the complete documentation index at: https://attlas.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Structuring content for better performance

> Learn how to organize your content so Attlas can better understand your information and deliver more accurate responses.

The quality of your chat's responses doesn't depend only on how much information you provide.

The way that information is organized also matters.

While Attlas can process many different types of content, well-structured information tends to produce clearer, more accurate and more consistent responses.

For this reason, whenever possible, we recommend organizing your content using a structure similar to **Markdown**.

***

## What is Markdown?

Markdown is a simple way to structure content using headings, subheadings, lists and clearly organized sections.

It is widely used in documentation, knowledge bases and AI systems because it helps preserve the hierarchy of information.

Even when you upload PDFs, Word documents, or plain text, Attlas attempts to identify and understand this structure automatically.

The more organized the structure is, the better.

***

## Common Markdown Syntax

Here is a quick reference of the most common Markdown formatting elements that you can use to structure your documents:

| Element         | Markdown Syntax                                     | Description                                     |
| :-------------- | :-------------------------------------------------- | :---------------------------------------------- |
| **Headers**     | `# Header 1`<br />`## Header 2`<br />`### Header 3` | Defines document structure and hierarchy.       |
| **Bold**        | `**text**` or `__text__`                            | Emphasizes important terms or labels.           |
| **Italic**      | `*text*` or `_text_`                                | Emphasizes secondary notes or terms.            |
| **Lists**       | `- Item 1`<br />`1. First Item`                     | Separates items, benefits, or sequential steps. |
| **Links**       | `[Attlas](https://attlas.so)`                       | References external pages or sources.           |
| **Blockquotes** | `> Important note`                                  | Highlights quotes, disclaimers, or warnings.    |
| **Inline Code** | `` `code` ``                                        | Highlights system parameters, keys, or options. |
| **Code Block**  | ` ``` `<br />`code block`<br />` ``` `              | Groups multi-line scripts or structured data.   |

***

## Why is structure important?

AI doesn't just read words.

It also tries to understand:

* What is a heading;
* What is a subheading;
* Which information belongs to each section;
* How topics are related;
* What represents a list;
* What is a question and what is an answer.

When information is well organized, Attlas can better understand context and retrieve information more accurately.

***

## Use headings and subheadings

One of the best practices is dividing content into clear sections.

### Poor Example

<Tabs>
  <Tab title="Example">
    <CodeGroup>
      ```markdown Markdown wrap theme={null}
      Product X is a business management software. The product integrates with CRM systems. Support is available from 8 AM to 6 PM. The basic plan costs $99. The advanced plan costs $199.
      ```
    </CodeGroup>
  </Tab>

  <Tab title="Result">
    <Danger>
      Product X is a business management software. The product integrates with CRM systems. Support is available from 8 AM to 6 PM. The basic plan costs \$99. The advanced plan costs \$199.
    </Danger>
  </Tab>
</Tabs>

### Better Example

<Tabs>
  <Tab title="Example">
    <CodeGroup>
      ```markdown Markdown theme={null}
      # Product X

      ## What it is
      Business management software.

      ## Integrations
      CRM integration.

      ## Support
      Support available from 8 AM to 6 PM.

      ## Pricing
      - Basic Plan: $99
      - Advanced Plan: $199
      ```
    </CodeGroup>
  </Tab>

  <Tab title="Result">
    <Check>
      # Product X

      ## What it is

      Business management software.

      ## Integrations

      CRM integration.

      ## Support

      Support available from 8 AM to 6 PM.

      ## Pricing

      * Basic Plan: \$99
      * Advanced Plan: \$199
    </Check>
  </Tab>
</Tabs>

The second version creates a much clearer hierarchy for AI to interpret.

***

## Use lists whenever possible

Lists help separate concepts and reduce ambiguity.

### Example

<Check>
  **Product benefits:**

  * Easy implementation
  * CRM integration
  * Dedicated support
  * Advanced reporting
</Check>

This is often easier to interpret than a large block of text.

***

## Group related information together

Avoid mixing completely unrelated topics within the same document.

### Avoid

* Product information;
* Internal policies;
* Recipes;
* Company information;

All combined into a single file.

### Prefer

One document for each major topic.

This helps Attlas understand the context more effectively.

***

## Use question-and-answer format for FAQs

When creating help centers or FAQ content, use a clear question-and-answer structure.

### Example

<Check>
  ### How do I request a refund?

  You can request a refund through your customer portal.

  ### What is the delivery time?

  The average delivery time is five business days.
</Check>

This format makes it easier for Attlas to retrieve answers when users ask similar questions.

***

## Avoid redundant or conflicting information

One of the most common causes of inconsistent answers is conflicting content.

### Example

Document A:

> Our company has been in business for 20 years.

Document B:

> Our company has been operating for 22 years.

When this happens, Attlas may struggle to determine which information is the most up to date.

Whenever possible:

* Update older documents;
* Remove duplicate content;
* Maintain a single source of truth for important information.

<Card title="Attlas Best Practices Guide" icon="bot" href="/docs/practices/using-attlas">
  Learn more about content consistency and quality in our Attlas Best Practices Guide.
</Card>

***

## Better structure means better understanding

Attlas can process content from many different formats.

However, when information is organized using headings, subheadings, lists and clearly defined sections, understanding becomes much more effective.

Think of content structure as a map.

The easier it is for AI to navigate your information, the better the responses it can deliver.

Good structure does not replace good content.

But good content combined with good structure almost always produces better results.