> For the complete documentation index, see [llms.txt](https://wiki.tinkerhub.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.tinkerhub.org/study-jams/faqs/frequently-asked-questions-faq.md).
# Frequently Asked Questions (FAQ)
> ## **Q: What exactly is a Study Jam?**
>
> A Study Jam is a learning initiative where you enroll in a course with a set schedule, attend lessons led by facilitators, and follow rules designed to maintain commitment and enhance learning.
> ## **Q: Who organizes Study Jams?**
>
> Study Jams are typically organized by TinkerHub Campus Communities, though external entities can also run them.
> ## **Q: How do I find a Study Jam that suits my interests?**
>
> Simply open *The Hub by TinkerHub* app, navigate to the Study Jams section, and search to find active courses that match your learning requirements.
> ## **Q: What are the consequences of missing a lesson?**
>
> Missing two mandatory lessons will automatically drop you from the course, reflecting the program’s emphasis on commitment and accountability.
> ## **Q: Can I choose to attend only some lessons?**
>
> While there are optional lessons, the course requires you to attend all mandatory lessons to successfully complete the program.
> ## **Q: What kind of support is available during a Study Jam?**
>
> Facilitators guide the sessions, and a community of learners is available to help you through any challenges you encounter.
> ## **Q: How do I know if I can handle the commitment?**
>
> Before registering, review the course details and guidelines thoroughly. Consider your schedule and commitment level, as the strict attendance policy is clearly outlined in the course rules.
---
# 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://wiki.tinkerhub.org/study-jams/faqs/frequently-asked-questions-faq.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.