> 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-cross-disciplinary/master.md).

# Summary of Cross-Disciplinary Projects

A repository of Cross-disciplinary project guides for middle school and high school classrooms.

### Whether you teach math, language arts, history, or computer science – prepare for a short project that intersects computer science with other disciplines.

| Project Guide                                                     | Description                                                                                                                                                                                                                                                            |
| ----------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Proposing Solutions in Computing**                              | <p>Students investigate a problem, defining the key stakeholders and identifying the opportunities for improvement with computing technologies. Students will then generate proposals for presentation.</p><p><strong>Business, Design, and Language Arts</strong></p> |
| **Sketching and Prototyping in Computing**                        | <p>Students envision a new mobile application through sketches and generate a dynamic prototype (without coding) to evaluate their idea.</p><p><strong>Engineering Design, Drawing and Art</strong></p>                                                                |
| **Product Evaluation in Computing**                               | <p>Students conduct a careful study of an existing computer/phone product for usability and user experience. Students will synthesize a report or presentation to share their findings and recommendations.</p><p><strong>Business, Design, Language Arts</strong></p> |
| **CS for Math & Science: Charting Data**                          | <p>Students process and prepare data for visualization with a combination of spreadsheets and graphics software.</p><p><strong>Math, Science, and Engineering</strong></p>                                                                                             |
| **CS for Language Arts: Use Machine Learning to Analyze Writing** | <p>Students experiment with <em>natural language processing</em> techniques to analyze writing and evaluate the value and risk it brings.</p><p><strong>Language Arts and Social Sciences</strong></p>                                                                 |
| **Build a Flash Card App Study Guide for Any Course**             | <p>Students input course content for a flash card application and then style it for a fun and engaging experience. </p><p><strong>Any Subject</strong></p>                                                                                                             |


---

# 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-cross-disciplinary/master.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.