# Larissa Protocol Documentation Style Guide

Introduction

Welcome to the Larissa Protocol Documentation Style Guide. This guide outlines the conventions and standards we follow for creating consistent, clear, and user-friendly documentation. Adhering to this style guide ensures that our documentation remains cohesive and easy to navigate.

### Document Structure

#### 1. Documentation Hierarchy

* Use a logical hierarchy to organize content: sections, chapters, and subsections.
* Maintain consistency in the naming and ordering of sections.
* Provide a clear table of contents for easy navigation.

#### 2. Headers

* Use `##` for section headers and `###` for subsections.
* Ensure meaningful and descriptive headers.

#### 3. Lists

* Use ordered (numbered) and unordered (bulleted) lists when presenting steps, items, or options.
* Follow a consistent style for lists.

### Writing Style

#### 1. Tone

* Maintain a professional, informative, and user-centric tone.
* Address the reader as "you" to create an engaging experience.

#### 2. Clarity

* Use clear and concise language to explain concepts.
* Define technical terms or acronyms when first mentioned.
* Provide examples and illustrations to enhance understanding.

#### 3. Consistency

* Be consistent with terminology and style throughout the documentation.
* Use the present tense for instructions (e.g., "Click the button").
* Use the past tense for describing past actions (e.g., "The update was released").

#### 4. Use of Links

* Embed links within the text for easy access to additional resources or related content.
* Ensure all links are functional and up to date.

### Formatting

#### 1. Code and Syntax

* Use code blocks for displaying code snippets.
* Highlight code within text using backticks (`code`).
* Specify the programming language for code blocks (e.g., "\`\`\`python").

#### 2. Emphasis

* Use *italics* for emphasizing words or phrases.
* Use **bold** for highlighting important information.

#### 3. Images

* Include images or diagrams to support explanations.
* Use descriptive alt text for images.

#### 4. Notes and Warnings

* Use notes, tips, and warnings to draw attention to specific information.
* Format them consistently to distinguish between different types.

### Conclusion

Following this style guide helps us maintain consistency, clarity, and professionalism in our documentation. By adhering to these conventions, we ensure that our readers have a smooth and effective experience while exploring Larissa Protocol.

For any questions or clarifications regarding this style guide, please feel free to reach out to the documentation team.


---

# 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.larissa.network/project-info/getting-involved/larissa-protocol-documentation-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.