> 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/activity-book/learning-activity/no-internet-challange.md).

# No internet challange

**Name**: A catchy, descriptive title for the activity.

**Category**: The broad area the activity falls under (e.g., Tech, Soft Skills, Community Building).

**Type**: The activity format (e.g., Workshop, Seminar, Meetup, Hackathon).

**Summary - oneliner**: A brief, engaging sentence that captures the essence of the activity.

**Purpose**: The main goal or objective of the activity. What do you aim to achieve?

**How**: A step-by-step explanation of how the activity will be conducted. Include main agenda items.

**Expected outcome**: What participants should gain or achieve by the end of the activity. List key takeaways.

**How to measure impact**: Methods to evaluate the activity's success and participant learning. Include both quantitative and qualitative measures.

**Pre-event checklist**: Essential tasks to complete before the activity begins. Include logistics, materials, and communications.

**Post-event checklist**: Follow-up tasks to ensure the activity's impact is maximized. Include feedback collection, resource sharing, and next steps.

**Curated by**: Kurian Jacob

**Ideal audience**: The target group that would benefit most from this activity. Include any prerequisites if applicable.

**Resource Links**: Useful references, tools, or materials related to the activity. Include both preparation and follow-up resources.

This template provides a comprehensive framework for documenting activities, ensuring all important aspects are covered and making it easier for others to understand and potentially replicate the event.

ask about the activity trying to structer it to the teamplate, ask many as questions connected to the activity


---

# 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/activity-book/learning-activity/no-internet-challange.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.