> For the complete documentation index, see [llms.txt](https://docs.appflowy.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appflowy.io/docs/documentation/software-contributions/architecture/frontend/frontend-tauri/codemap.md).

# CodeMap

This code map introduces the folder hierarchy of AppFlowy. **`appflowy_tauri`** the [tauri](https://tauri.app/) working directory.

## src

Contains all the React source code

### 1. appflowy\_app

1. components

   > Contains all the `React` components.

   1. grid
   2. board
   3. editor
2. home

   > Implements the application skeleton that including the sider, header, and footer.

### 2. services

1. backend:

   > Contains all the backend bridge files that including the auto-generated events,protobuf, and etc.

### 3. assets

## [src-tauri](https://tauri.app/v1/guides/getting-started/setup/html-css-js)

Contains all the Rust source code

1. Cargo.toml

   > Cargo's manifest file. You can declare Rust crates your app depends on, metadata about your app, and much more. For the full reference see Cargo's Manifest Format.
2. tauri.conf.json

   > This file lets you configure and customize aspects of your Tauri application from the name of your app to the list of allowed APIs. See [Tauri's API Configuration](https://tauri.app/v1/api/config/) for the full list of supported options and in-depth explanations for each.
3. src/main.rs

   > This is the entry point to your Rust program and the place where we bootstrap into Tauri.
4. src/request.rs

   > Defines `invoke_request` function to handle how to send the Event to AppFlowy core


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.appflowy.io/docs/documentation/software-contributions/architecture/frontend/frontend-tauri/codemap.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.