> For the complete documentation index, see [llms.txt](https://0xgosu.gitbook.io/monolith-framework/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://0xgosu.gitbook.io/monolith-framework/extra-resources/extra.md).

# Extra Resources

This section contains additional resources beyond the main documentation, including frequently asked questions and supplementary materials.

## What's in This Section

### Frequently Asked Questions (FAQ)

The [FAQ section](/monolith-framework/extra-resources/faq.md) addresses common questions developers ask when working with the Monolith Framework:

* **Module Development**: How to add and structure modules
* **Inter-Module Communication**: Different communication patterns and when to use them
* **Framework Features**: JetStream, health checks, and other features
* **Project Setup**: Recommended structures and best practices
* **Testing and Error Handling**: Common patterns and approaches

## Quick Links

### Get Answers to Common Questions

**Start here:** [Frequently Asked Questions](/monolith-framework/extra-resources/faq.md)

Common questions covered:

1. How do I add a new module?
2. How do modules communicate with each other?
3. What's the difference between Channel and Request-Reply services?
4. How do I handle errors in handlers?
5. How do I test modules in isolation?
6. Can I use this framework without JetStream?
7. How do I implement health checks?
8. What's the recommended project structure?

## When to Use This Section

* You have a question that isn't covered in the main guides
* You need clarification on common patterns or features
* You're troubleshooting an issue
* You want to understand best practices for a specific scenario

## Organization

* [**Frequently Asked Questions**](/monolith-framework/extra-resources/faq.md) - Answers to the most common developer questions
* [**Code Coverage**](/monolith-framework/extra-resources/code-coverage.md) - Test coverage statistics and quality metrics

## Related Documentation

* [How-To Guides](/monolith-framework/guides/guides.md) - Step-by-step instructions for common tasks
* [API Reference](/monolith-framework/api-reference/api.md) - Complete API documentation
* [Core Concepts](/monolith-framework/core-concepts/core-concepts.md) - Foundational concepts and architecture

***

If you have a question that's not covered here, check the [Core Concepts](/monolith-framework/core-concepts/core-concepts.md) or [How-To Guides](/monolith-framework/guides/guides.md) sections for more detailed information.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://0xgosu.gitbook.io/monolith-framework/extra-resources/extra.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.