> 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/campus-community/members-aka-makers.md).

# Members aka Makers

At TinkerHub, we celebrate the spirit of hands-on learning and cognitive flexibility\*. *Bringing our coolest thoughts to life unlocks a better us, doesn't it?*

We have been using the term 'maker' for a long time at TinkerHub. By 'maker', we refer to TinkerHub volunteers and members who possess a unique blend of creativity, problem-solving abilities, commitment to continuous learning and wants to be part of TinkerHub movement to make a change.&#x20;

{% hint style="info" %}
🧑‍🔧 **Makers** are the innovators and creators who utilize their diverse skills and knowledge across various disciplines to build, create, and improve the world around them.
{% endhint %}

Makers take an interdisciplinary approach, combining skills to achieve their goals. We believe anyone can be a maker – it's about the mindset, passion for learning, and drive to create & innovate. By nurturing these qualities, we aim to empower the next generation of makers to build a better future for themselves and the world around them.

In TinkerHub context, we primarily focus on building with the help of technology and its adjacents. Given the same, we are not limited to coding.&#x20;

*\*Read more about cognitive flexibility, continuous learning and other foundational skills we have identified, in the page-* [*Foundational Skills*](https://wiki.tinkerhub.org/campus-community/foundational-skills.md)

{% content-ref url="/pages/C5NFPUupYvudJ1quo4bb" %}
[Makers - Roles & Responsibilities](https://wiki.tinkerhub.org/campus-community/members-aka-makers/makers-roles-and-responsibilities.md)
{% endcontent-ref %}


---

# 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/campus-community/members-aka-makers.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.
