> For the complete documentation index, see [llms.txt](https://docs.keyshade.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keyshade.io/contributing-to-keyshade/design-of-our-code/web.md).

# Web

The web application is responsible for serving the homepage, providing users with access to its content and functionality, the stacks, and things you should know before you get started with it!

## Stack

* **Next.js** as the framework
* **React** as the frontend library
* **MDX** for Markdown and JSX integration
* **Tailwind CSS** for utility-first styling
* **Framer Motion** for animations
* **Geist** for UI components
* **@tsparticles/engine, @tsparticles/react, @tsparticles/slim** for particle animations
* **Sonner** for notifications
* **TypeScript** for static typing

## Structure

```
├── web
    ├── public
    ├── src
    |      ├── app
    |      ├── components
    |      └── utils
    └── config_files
```

### web

The main directory that contains all parts of the web app.

#### public

Contains static files and assets.

#### src

Contains the source code of the app.

* **app**: Holds the main pages and settings for the app.
* **components**: Reusable pieces used in the app.
* **utils**: Helper tools and functions that support the app.

#### config\_files

Contains configuration files for the app.


---

# 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:

```
GET https://docs.keyshade.io/contributing-to-keyshade/design-of-our-code/web.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.