> 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/modules/cxd-framework.md).

# Foundations

### **What is the *****big picture***** of the Computing by Design (CxD) framework? How is it connected to fundamental concepts in science, design, and innovation? How can we introduce industry practices in a classroom environment?**

We will answer these questions and more through the following topics.

### [**The CxD Approach**](/cxd/cxd-2020-summer-workshop/modules/cxd-framework/cxd-approach.md)

We will explore **primary learning objectives** for a computer science course and an achievable **student profile** that exhibits the attributes of a life-long learner and doer.  We will consider the **three threads of an innovator's work** and how we can use the classroom as a bridge for students to participate in the modern world .  We will review basic **industry practices to manage project work** and how to replicate them in an appropriate way for classrooms.

### [**Mapping Innovative Practices**](/cxd/cxd-2020-summer-workshop/modules/cxd-framework/mapping-skills-and-practices.md)

We will map the **thinking, doing, and interactions of innovation** to provide perspective on the set of practices we want students to engage that provide a depth and breadth to their approach. We will investigate the **Indiana standards in computer science**, along with the **national framework and PBLWorks guidance,** to build confidence and comfort in covering a full spectrum of learning objectives.

### [**The CxD Project Framework**](/cxd/cxd-2020-summer-workshop/modules/cxd-framework/cxd-framework.md)

We will go through the **three phases of a standard project outline** and discuss the primary activities in completing projects. We will review the important milestones of the **public presentations and deliverables**. We will consider how teams of students may progress through the project, sometimes in a linear series and other times in parallel tracks. Finally, we will see how students may develop **a product feature map** for organizing work and communicating progress.

### [**Programming Warm Up**](https://app.gitbook.com/@cxd/s/cxd2020/~/drafts/-M8REDYTusR9uw7LSsVf/modules/cxd-framework/core-programming-concepts)

We will cover some **basic concepts in programming with HTML and CSS** that can provide a launching point into our projects.

### [**A Teacher's Insight**](/cxd/cxd-2020-summer-workshop/modules/cxd-framework/a-teachers-insight.md)

Justin Smith will provide insight from experience on how to facilitate innovation in the classroom.


---

# 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/modules/cxd-framework.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.