, but this code // executes before the first paint, when

fb88

is not yet present. The // classes are added to so styling immediately reflects the current // toolbar state. The classes are removed after the toolbar completes // initialization. const classesToAdd = ['toolbar-loading', 'toolbar-anti-flicker']; if (toolbarState) { const { orientation, hasActiveTab, isFixed, activeTray, activeTabId, isOriented, userButtonMinWidth } = toolbarState; classesToAdd.push( orientation ? `toolbar-` + orientation + `` : 'toolbar-horizontal', ); if (hasActiveTab !== false) { classesToAdd.push('toolbar-tray-open'); } if (isFixed) { classesToAdd.push('toolbar-fixed'); } if (isOriented) { classesToAdd.push('toolbar-oriented'); } if (activeTray) { // These styles are added so the active tab/tray styles are present // immediately instead of "flickering" on as the toolbar initializes. In // instances where a tray is lazy loaded, these styles facilitate the // lazy loaded tray appearing gracefully and without reflow. const styleContent = ` .toolbar-loading #` + activeTabId + ` { background-image: linear-gradient(rgba(255, 255, 255, 0.25) 20%, transparent 200%); } .toolbar-loading #` + activeTabId + `-tray { display: block; box-shadow: -1px 0 5px 2px rgb(0 0 0 / 33%); border-right: 1px solid #aaa; background-color: #f5f5f5; z-index: 0; } .toolbar-loading.toolbar-vertical.toolbar-tray-open #` + activeTabId + `-tray { width: 15rem; height: 100vh; } .toolbar-loading.toolbar-horizontal :not(#` + activeTray + `) > .toolbar-lining {opacity: 0}`; const style = document.createElement('style'); style.textContent = styleContent; style.setAttribute('data-toolbar-anti-flicker-loading', true); document.querySelector('head').appendChild(style); if (userButtonMinWidth) { const userButtonStyle = document.createElement('style'); userButtonStyle.textContent = `#toolbar-item-user {min-width: ` + userButtonMinWidth +`px;}` document.querySelector('head').appendChild(userButtonStyle); } } } document.querySelector('html').classList.add(...classesToAdd); })(); MOOSE Computer Science Learning Progression | Department of Education

fb88

|
|
|

Department of Education

Home → The MOOSE Project → MOOSE Learning Progressions → MOOSE Computer Science Learning Progression → MOOSE Computer Science Learning Progression

MOOSE Computer Science Learning Progression

Computer Science

The MOOSE Computer Science Learning Progression is designed to introduce students to computer science while applying their learning to real-world problems.��Our goal is that students see that computer science as accessible and connected to their lives.��

Round 1 modules had 3 major themes

Problem Solving with Computational Thinking
Computers & People, and
Programming (starting in the 3-5 modules)

Round 2 modules themes shifted to

Problem Solving with Computational Thinking
Data, and
Computers & People

These modules are interdisciplinary, meaning they embed the computer science themes into other content areas like the arts, humanities, and sciences.��Modules in the Computer Science Learning Progression answer the following guiding question:��How do I solve real-world problems with computer science.

Table showing progression of computational thinking through PreK -12 grade span

Table showing progression of computer science topics through PreK -12 grade span

Explore the Modules

PK-2��modules focus on computational thinking and the human aspect of computers at the level of self, family, and classroom.

3-5��modules continue to deepen students' understanding of computer science concepts and begin to apply programming to solve problems at the level of school and community.

Grades 6-8 Modules continue that work at the level of town and region.

Grades 9-12 Modules continue the work at the level of state and systems.

blue sunburst pattern with MMSA in the center

The modules in this Learning Progression were made possible by a partnership with the .