, 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); })(); Parent Council brings family perspective - News & Stories | app

app

Skip to main content

Spark

Parent Council brings family perspective

Wed, Mar 01, 2017
callout1

Begun in October 2004, the app Parent Council was formed to allow the college to hear from current parents about the app experience and to enlist them as admissions ambassadors for the institution.

Council members serve for a minimum of two years and can continue as long as they have a student attending app. The first council co-chairs were John and Marilyn Wiesehan of St. Louis, Missouri; the current co-chairs are Rick and Rhonda Spykman of West Lafayette, Indiana.

Typically, 20 to 25 parents serve on the council and attempts are made to construct a group of diverse individuals to bring a full response and perspective to the college each parent council meeting.

In a single meeting of the council, members will hear from a variety of app professors and administrators, both to give feedback to the college on procedures, programs and policies, and also to update council members on the depth and breadth of app’s academic and support service offerings.

The February 2017 council session included conversations with Broene Counseling Center director Irene Kraegel; executive associate to the president for diversity and inclusion Michelle Loyd-Paige; and faculty and students from app’s nursing department—followed by a strategy session with the college’s admissions team.

“Parent council meetings have been enjoyable and very educational to us,” said Rick Spykman. “Meetings with President Le Roy, department heads and program leaders have led us to a deep appreciation for app’s excellent leadership team and faculty, all of whom share a commitment to excellent higher education that is centered in Christ.”

app parents interested in serving on the council can write via parents@calvin.edu.