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

ƴɸ̳

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); })(); Newcomers missed - News & Stories | ƴɸ̳

ƴɸ̳

Skip to main content

Spark

Newcomers missed

Wed, Jun 15, 2016

I was very disappointed to hear that the format of Spark magazine will be changing and that you will no longer be printing newcomers’ information. Graduating in 2006, I looked forward to reading about who had recently had new babies. It was my favorite part of the magazine. My fellow graduates will not hear of the birth of my son in the magazine due to this change.

I encourage you to readdress and rethink this issue. Not celebrating new life in our magazine is just another example of how we are getting away from families and family support.

Beth Derocha Helmreich ’06, Port Huron, Michigan


I read in the most recent issue of the Spark that you would no longer be including wedding announcements and birth announcements because people get that through social media. I think that this is a loss because I am not friends with everyone that I might be interested in learning that information about. For example, there are younger people from my church growing up that I no longer have contact with but about whom it is fun to know that they have gotten married or had children.

Jennifer Hoogwerf Bryson ’91, Dexter, Michigan


I wanted to offer my opinion of the new Spark. The new format is fine—I like it neither worse nor better than the old one. However, I am very disappointed that the births and marriages are no longer published. This was my favorite part of the Spark. Because it is no longer in each issue, I no longer look forward to getting it. I thought Calvin’s big thing was being a community and being a “Knight for Life.” I feel like taking away the announcements of births and marriages takes away a huge part of the community feel. Please consider bringing back the marriages and newcomers.

Katie Shaarda VanDyken ’06, Grand Rapids, Michigan