# Documentation Style Guide

These are the guidelines for writing documentation.

## Titles

* Each page must have a single `#`-level title at the top.
* Chapters in the same page must have `##`-level titles.
* Sub-chapters need to increase the number of `#` in the title according to

  their nesting depth.
* All words in the page's title must be capitalized, except for conjunctions

  like "of" and "and" .
* Only the first word of a chapter title must be capitalized.

```
# Arrays

...

## How to declare an array

...

## Create an empty array

...
```

## Print Width

To be easy to read when editing the markdown code, if the sentence is too long, divide it down. The recommended column length limit is 80.

## Code Output

To create output from code, there are two rules:

* If the output is short then put it as a comment
* If the output is quite long (column) then write it in a separate section after the code section.

## Indentation

Indentation must use spaces and the tab size must be 4.


---

# 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://v-community.gitbook.io/v-by-example/docs_style_guide.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.