> For the complete documentation index, see [llms.txt](https://sign-language-center.gitbook.io/tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sign-language-center.gitbook.io/tech/faq.md).

# FAQ

## 1. What is Sign Language Center?

A project to bring free and convenient technology to the disabled community. Imagine a mute person giving an eloquent presentation on stage using sign language, or a deaf person understanding what you say immediately through sign language.

## 2. What is the technology behind Sign Language Center?

We use a machine learning model with the "Image Classification" problem to recognize hand gestures. The model was trained for over 1,000 hours on over 15,000 different hand-gesture photos, in every angle and lighting condition.

## 3. What is one-hand sign language?

Words that can be said with only one hand, for example the letters of the alphabet (A, B, C, D, etc.) or words like "I love you", "thank you" and "hello".

## 4. What is two-hand sign language?

Words that require both hands to express their meaning.


---

# 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://sign-language-center.gitbook.io/tech/faq.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.