> 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-2020-summer-workshop/preparation/workshop-tools.md). # Workshop Tools We strive to make learning accessible with free and browser-based tools whenever possible, and that goes for this workshop as well. Below are the primary tools we will be using along with pointers on particular features that will be useful for us. *\*\* Each project may use additional tools, but we will provide guidance for those when the need arises.* ## Slack [**Slack**](https://slack.com), an industry favorite, will support our daily communication during the workshop. If you are unfamiliar with Slack, take a look at their [**help pages on using slack**](https://slack.com/help/categories/200111606)**,** and review the "Send Messages" and "Share Files & Conversations" sections**.** Don't feel like you need to understand all the features. We will likely stick with the basics. The video below highlights some basic features that will be useful for the workshop. {% embed url="" %} ## Zoom [**Zoom**](https://zoom.com), a popular video conferencing platform, will be used for our live [**scheduled discussions**](/cxd/cxd-2020-summer-workshop/schedule.md) and ad hoc discussions as needed. If you haven't used Zoom much take a look at [**getting setup on your desktop**](https://support.zoom.us/hc/en-us/sections/200305583-Desktop)**,** [**testing audio**](https://support.zoom.us/hc/en-us/articles/201362283-Testing-computer-or-device-audio)**,** and [**testing video**](https://support.zoom.us/hc/en-us/articles/201362313-How-Do-I-Test-My-Video-)**.** The video tutorial below explains how to share your screen, which will come in handy to get feedback on something or to demonstrate something you have done. {% embed url="" %} ## Google Drive [**Google Drive**](https://drive.google.com) provides a suite of valuable tools that most are already familiar with. If you are new to Google Drive, consider [**this full tutorial**](https://www.youtube.com/watch?v=qg7d_FqiePo). The short video below specifically demonstrates how to share a folder on Google Drive. Whether using *link sharing* or adding individuals by email, this is a very useful way for student teams to share folders with you, or vice versa. {% embed url="" %} ## Repl.it [**Repl.it**](https://repl.it) will be the go-to platform for most programming tasks. It is free, browser-based, and has a lot of useful features. If you already have some programming experience, go ahead and poke around a bit on the platform. **As a teacher, you will likely want to get the free classroom plan that supports having private code, even if you don't use all the classroom features. Here is the link to apply,** [**https://repl.it/k12-form**](https://repl.it/k12-form)**.** If you have little or no experience programming, *no problem*, follow the quick start video below where you will 1) sign up, 2) make a copy (*fork*) of [**this program**](https://repl.it/@jimlyst/Hello-World), and 3) click `run` to see the result. That's it for now. We'll dive deeper later. {% embed url="" %} --- # 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-2020-summer-workshop/preparation/workshop-tools.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.