, 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); })(); Standards & Instruction - Mathematics | Department of Education

fb88

|
|
|

Department of Education

Home → Learning → Content Standards → Mathematics → Standards & Instruction - Mathematics → Standards & Instruction - Mathematics

Standards & Instruction - Mathematics

As part of the fb88 Department of Education’s commitment to supporting schools in the delivery of effective PK-12 mathematics instructional programs, this page provides links to resources to support implementation of fb88’s mathematic academic standards. How schools implement these standards is entirely a local decision.

fb88’s Mathematics Academic Standards

fb88 Learning Results: Mathematics.��The Mathematics standards in the fb88 Learning Results have been updated and adopted as of July 18, 2020 and still continue to include the Common Core State Standards.
fb88's Early Learning and Development Standards.��These guidelines direct State and local early care and education practitioners’ efforts to improve early childhood professional practice and programs for young children ages three through their entrance into kindergarten. The guidelines also consider the core elements contained in the fb88 Learning Results.
Core Content Connectors��(word document download).��The Core Content Connectors [CCCs] are fb88’s alternate achievement standards in mathematics. ��These standards are derived from the Common Core State Standards, reduced in complexity and deconstructed into smaller, more accessible steps for students with the most significant cognitive disabilities. ��The CCCs are the building blocks of fb88’s alternate assessment in mathematics, the MSAA. ��For more information about alternate assessments based on alternate achievement standards (AA-AAS), please contact Jodi Bossio-Smith at: jodi.bossio-smith@maine.gov.

��