> 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/kutty-makers/learning-experiences.md).

# Learning Experiences

Learning experiences are the foundation of every KuttyMakers community.

Unlike traditional classroom sessions, they don't begin with a lesson plan or a chapter from a textbook. They begin with a question, an observation, a challenge, or an idea worth exploring.

A learning experience encourages children to think, ask questions, experiment, build, collaborate, and reflect. Some experiences may involve technology, while others may involve art, nature, storytelling, design, or simply observing the world around them.

The goal isn't to teach everything. It's to create opportunities for children to discover something for themselves.

There is no fixed format for a learning experience. Every school and every group of children is different. A good learning experience is one that adapts to the interests of the children and the context of the community.

Some examples include:

* Exploring how everyday objects work by taking them apart.
* Going on a walk around the school to observe problems worth solving.
* Building prototypes using cardboard and recycled materials.
* Inviting local makers, artists, or professionals to share their journeys.
* Exploring emerging technologies like Artificial Intelligence through hands-on activities.
* Creating something that improves the school or the local community.

Every learning experience should leave children with more questions than answers, because curiosity is where meaningful learning begins.

***

Then the next page becomes **Community Projects**, because projects are simply one type of learning experience.


---

# 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://wiki.tinkerhub.org/kutty-makers/learning-experiences.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.
