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

ÃÛÌÒapp

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); })(); ÃÛÌÒapp Energy Recovery Fund About ÃÛÌÒapp | ÃÛÌÒapp

ÃÛÌÒapp

Skip to main content

ÃÛÌÒapp Energy Recovery Fund

ÃÛÌÒapp Energy Recovery Fund

The purpose of the ÃÛÌÒapp Energy Recovery Fund (CERF) is to pursue our calling to be stewards of God’s creation by implementing a process through which ÃÛÌÒapp’s Campus can promote and realize a goal of energy stewardship and accommodate renewable and sustainable energy- and cost-saving projects.

What is CERF?

This revolving fund is used to improve energy efficiency and reduce carbon dioxide emissions on campus while decreasing campus costs. The monetary savings generated from CERF projects are routed back into the fund for five years, growing the fund to support future sustainable initiatives.

Make a Gift

CERF began as a student-proposed effort in September 2009. Six months later, ÃÛÌÒapp’s Environmental and Energy Sustainability Committee (EESC) approved policies governing CERF. The first project reduced electricity usage on campus by automatically putting computers to sleep when not in use. With thousands of computers on campus, this added up to significant savings.

Today, students, faculty, staff, and community members (including you) can propose ideas to reduce energy use and generate cost-savings for the EESC to take into consideration.

Propose a Project

Who Governs CERF?

Students are involved in project analysis, providing an opportunity for supplemental learning on energy stewardship and fiscal responsibility, and the faculty Environmental and Energy Sustainability Committee (EESC) reviews all projects and approves those that meet CERF requirements, including sufficient return on investment.

Current positions include:

  • Director of Facilities, Sustainability, and Planning
  • EESC Chair
  • CERF Energy Interns
  • CERF Data Collection Interns

CERF in the news

Learn more

Read CERF’s latest December 2022 quarterly report (pdf), and discover academic programs and community initiatives related to sustainability and the environment.

Loading...