> 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/cross-disciplinary-workshops/cs-for-language-arts-natural-language-processing.md).

# CS for Language Arts: Natural Language Processing

### **Welcome and Getting Started Video**

{% embed url="<https://www.loom.com/share/8e422512e9344d1b9d318ddc9b299584>" %}

### **Project Guide**

While the project guide, linked below, can be used as-is in your classroom, you will likely want to adapt the instructions to meet the specific needs of your course context and objectives. Feel free to use any portion of the material in your own documentation.

{% embed url="<https://docs.idew.org/cxd-cross-disciplinary/projects/cs-for-language-arts-use-machine-learning-to-analyze-writing-1>" %}

### Workshop Agenda

{% hint style="warning" %}

#### All posted times are Eastern Daylight Time (EDT)

{% endhint %}

1. **Attend the live Zoom session on Monday June 13, 2:30 pm - 3:30 pm** **EDT ⏰**\
   The Zoom link will be provided in Slack.
2. **Follow the project guide and complete an example project to meet your student expectations, as you construct any adapted project instructions documents you will use for your course.**\
   Use our Slack channel `#short-project-cs-for-language-arts` to post questions/answers, to share things you have created or to share additional resources you have found.
3. **Attend the live Zoom session on Thursday June 16, 1:00 pm - 2:00 pm EDT ⏰**\
   The same Zoom link will be used for this meeting
4. **Continue posting questions and sharing success in Slack `#`**`short-project-cs-for-language-arts` as you complete your project example and adapted project instructions.
5. **Submit your project example and adapted project instructions for the workshop deliverable by July 11, 2022.  🎉**\
   ![](https://3503815932-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKaUwYmDa4QuxXnmkymd5%2Fuploads%2Fiet8twonV3DUyXjXMpXz%2Fimage.png?alt=media\&token=a75b05e0-c93a-4744-bf24-7395983af790)

## Workshop Prep

### Getting Started with Slack

{% embed url="<https://www.loom.com/share/351f4100d55045a0a04b3ec078ffaa39>" %}

Slack will be our primary communication platform for the workshop. The video above provides a brief introduction on the features of Slack, but more help and tutorials can be found at <https://slack.com/help>.


---

# 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/cross-disciplinary-workshops/cs-for-language-arts-natural-language-processing.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.