> For the complete documentation index, see [llms.txt](https://redi-school-1.gitbook.io/applicant-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://redi-school-1.gitbook.io/applicant-hub/resources/redi-style.md).
# ReDI Style
At ReDI School, we value professional collaboration. That means we ask you to follow our communication standards, notify teachers when you can't join, use your camera during meetings, and participate via a laptop. These protocols are standard practice in companies. Thanks for following them during your course!
***
#### Community Conduct
At ReDI, we build a learning environment where everyone feels safe, respected, and able to participate fully. We expect all members of our community to carry themselves with professionalism and kindness, how you speak, listen, and show up matters.
* **Communicate and interact respectfully:** speak politely, listen actively, and use a kind tone. Introduce yourself to teachers and classmates, and use names and pronouns correctly. Help foster a positive, inclusive space for everyone.
* **Keep discussions constructive:** stay focused on learning, express ideas thoughtfully, and avoid divisive topics (such as political or religious debates) that could make others uncomfortable.
* **Appreciate your instructors:** our teachers volunteer their time and expertise. Show gratitude by being on time, coming prepared, and participating fully. Respect toward volunteers is a core ReDI value.
* **Misconduct is not tolerated:** harassment, bullying, discrimination, or offensive behaviour is unacceptable. If something concerns you, contact your **Course Manager**. You can find the full policy in the official [Code of Conduct](https://www.redi-school.org/redi-code-of-conduct).
***
#### 💬 Attendance & Absence
**Attendance Policy**
* **Regular attendance** is crucial for your learning journey
* We require **80% attendance** to receive your certificate at the end of the course
* Attendance is tracked for each session:
* Full attendance when you join on time
* Half attendance if you join late
* No attendance if you miss a session
**Absence Notification**
If you cannot attend a session:
1. Notify your teachers **at least 24 hours in advance** when possible
2. Use your **Course Slack channel** to communicate your absence (You will receive an invite to your **Course Slack channel** before the semester starts).
3. Provide a brief reason for your absence
This professional courtesy helps teachers plan accordingly and is standard practice in workplace environments.
***
#### 💻 Join via a Laptop
* **Join via a laptop or desktop computer**, not a mobile device.
* This ensures you can participate fully in coding exercises
* A proper setup allows you to:
* Follow along with live coding
* Split your screen between video call and code editor
* Use the necessary development tools effectively
***
#### 🙌 Professional Communication
* Use Slack to communicate
* Respond to messages within 24 hours
* Use clear, respectful language
* Share challenges openly - everyone is here to learn
***
#### 🤖 Use of AI Tools
The use of AI tools such as Fireflies.ai, Otter.ai, transcription services, or similar is **strictly prohibited** during live sessions.
These tools can compromise the privacy of your peers and instructors. They are not allowed under any circumstances. Please respect this rule to help us maintain a safe and trustworthy learning environment.
***
#### Summary
* **Join at least 80%** of the sessions to receive a certificate
* **Notify teachers** at least 24 hours in advance in your Slack Channel if you cannot attend
* Have your **Camera On** during the sessions
* **Join via a Laptop** instead of your phone
* Let's communicate **professionally**
By following these protocols, you'll get the most out of your ReDI School experience and develop professional habits that employers value highly.
---
# 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://redi-school-1.gitbook.io/applicant-hub/resources/redi-style.md?ask=&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.