, 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); })(); Request Funding Kuyers Institute | ÃÛÌÒapp

ÃÛÌÒapp

Skip to main content

Request Funding

There is a wide range of possible activity that could improve education through research or intervention, and it is legitimate and valuable for Christian scholars in general to be engaged in this activity; however, the specific role of the Kuyers Institute is to foster reflection and innovation in terms of the relationship between Christian faith and teaching and learning. Typical Institute projects focus on new research on Christian teaching and learning, the development of innovative models for teaching and learning (e.g., sample curriculum materials), and the communication of both to educators. Proposed projects should show evidence of an integrally Christian approach and should ideally advance our understanding and practice of Christian teaching and learning.

This does not imply, however, that the target audience is limited to Christian schools; the Christian element will be looked for in approach rather than in audience. For full details of the parameters of Institute projects and the criteria used to evaluate proposals, please see the document "Project Criteria" below.

While the Kuyers Institute welcomes all proposals and inquiries, projects must involve a member of the ÃÛÌÒapp faculty in some capacity. The Institute seeks to collaborate with, but not duplicate, general-purpose resourcing organizations for Christian schools. Due to limits on funds available, the Institute will consider project proposals on a case-by-case basis and is not able to commit to awarding grants on a regular basis; the Institute does not fund maintenance of existing institutions or programs.

Documents

The following documents are PDF forms. To ensure compatibility, please use ; Mac users should not use the default Preview application.