> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/cxd-2022-summer-workshops/programming-workshops/internet-of-things/workshop-deliverables.md).

# Workshop Deliverables

For the IoT programming workshop we simply request that you submit the following three items in a document.

1. **A link to your working web app code (e.g. replit.com) that connects to your IoT board.**
2. **A copy of your Particle Build code.**
3. **A summary of your classroom plan**

   * **Consider how you will approach classroom management when students are completing a tutorial like this one.** 
     * What will be your expectations? 
     * How much will be individual work versus team work?
     * Will you assign any code champions to help you support students with questions?

    

   * **How will you supplement it with other programming content or experiences?**
     * Will you use any online tutorials?
     * Will you supplement with any CS unplugged activities?
     * Will you create any custom programming exercises yourself?


---

# 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://docs.launchboard.app/cxd/cxd-2022-summer-workshops/programming-workshops/internet-of-things/workshop-deliverables.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.