Online Resource

Hayden Library - HQ1438.S63 S685 2019

Dewey Library - HT1523.L285 2019

Join the Regional Educational Laboratory Mid-Atlantic and stakeholders from the New Jersey and Delaware Departments of Education for a free four-part series on culturally responsive practices as a strategy for improving education outcomes.

Parents who participated in the Child Support Noncustodial Parent Employment Demonstration (CSPED) reported substantially higher levels of satisfaction with child support services compared with those who did not participate in the program.

Mathematica’s Jonathan Morse and Clint Eisenhower will team up to share their thoughts on state impacts and expectations for the Centers for Medicare & Medicaid Services Medicaid program integrity strategy at this year’s NAMPI Annual Conference in Atlanta.

Each October, National Principals Month recognizes the essential role principals play in making schools great.

A final report presents evidence on the long-term impacts of the Steps to Success home visiting program for adolescent mothers in San Angelo, Texas.

Principals can play an important role in improving instruction and student achievement in their schools. Many professional development programs focus on strengthening principals’ leadership skills.

Mathematica will showcase state Medicaid services and support for CMS projects to modernize data analytics for Medicaid and the Children’s Health Insurance Program at the National Association of Medicaid Directors fall conference.

Despite recent improvements in the overall job market, many individuals – including many individuals with disabilities – continue to face obstacles to gainful employment and economic independence.

Australia. Parliament. Senate. Legal and Constitutional Affairs Legislation Committee, author, issuing body

Australia, author

Australia. Parliament. Joint Standing Committee on the National Disability Insurance Scheme, author, issuing body

University of Sydney. Post-Graduate Committee in Veterinary Science

Online Resource

Gain a new respect for the good old pumpkin. Author Mary Miley Theobald traces the history of the venerable gourd.

Herring, William, author

Swarts, Heidi J

Australia. Parliament. Senate. Community Affairs Legislation Committee, author, issuing body

Online Resource

Location Multiple Locations

Call No. HV3177.H6 T83 2016

Have you been curious to know who was on the team of the 1985–1986 women’s Pronghorns basketball team? How about what was on the menu for the Pronghorns’ Athletic Awards Dinner in 1972?

Those curiosities and questions are answered if you browse the Pronghorn Athletics Programs and Ephemera that are now online at the University of Lethbridge Publications collection!

Take a stroll down memory lane and check out the other Digitized Collections provided by the University Library and partners for free!

Coles, Michael

Mayo, Joseph

Clifford, Brian R

Gordon, V. Scott, author

Kessenich, John M., author

Wong, Yue-Ling, author

Deitel, Paul J., author

Stokes, David, author

Sometimes it is fun to re-visit very basic HTML things and look what we can do with them nowadays. This is what I will do now with a radio button group. I will progressively enhance it to look great and still work with keyboard and screen readers. As part of my Logo-O-Matic upgrade, I added […]

Vee, Annette, author

Lister, Gary, author

Hayden Library - T174.7.D53 2018

As India debates environmental health versus economic growth, Rachel Kyte, vice-president and special envoy for climate change at the World Bank Group, feels it is vital to think beyond basic GDP.

Barker Library - TA443.P58 I57 2013

Online Resource

Hayden Library - QH315.C2885 2018

In his The Case for Progressive Web Apps presentation at An Event Apart in Chicago, Jason Grigsby walked through the process of building Progressive Web Apps for your Web experiences and how to go about it. Here's my notes from his talk:

• Progressive Web Apps (PWAs) are getting a lot of attention and positive stories about their impact are coming out. PWA Stats tracks many of these case studies. These sorts of examples are getting noticed by CEOs who demand teams build PWAs today.
• A PWA is a set of technologies designed to make faster, more capable Web sites. They load fast, are available online, are secure, can be accessed from your home screen, have push notifications, and more.
• But how can we define Progressive Web Apps? PWAs are Web sites enhanced by three things: https, service worker, and a manifest file.
• HTTPS is increasingly required for browsers and APIs. Eventually Chrome will highlight sites that are not on https as "insecure".
• Service Workers allow Web sites to declare how network requests and the cache are handled. This ability to cache things allows us to build sites that are much faster. With service workers we can deliver near instant and offline experiences.
• A Web manifest is a JSON file that delivers some attributes about a Web site. Browsers use these files to make decisions on what to do with your site (like add to home page).
• Are PWAs any different than well-built Web sites? Not really, but the term helps get people excited and build toward best practices on the Web.
• PWAs are often trojan horses for performance. They help enforce fast experiences.

Feels Like a Native App

• Does your organization have a Web site? Do you make money off your Web site? If so, you probably need a Progressive Web Site.
• Not every customer will have your native app installed. A better Web experience will help you reach people who don't. For many people this will be their first experience with your company, so you should make it as good as possible.
• Getting people to install and keep using native apps is difficult. App stores can also change their policies and interfaces which could negatively impact your native app.
• The Web can do much more than we think, the Web has APIs to access location, do fast payments using fingerprint identification, push notifications, and more.
• What should we use to design PWAs? Native app styles or Web styles? How much does your design match the platform? You can set up PWAs to use different system fonts for iOS and Android, should you? For now, we should define our own design and be consistent across different OSs.
• What impact does going "chrome-less" have on our PWAs? You loose back buttons, menu controls, system controls. Browsers provide us with a lot of useful features and adding them back is difficult. Especially navigation via the back button is complex. So in most cases, you should avoid going full screen.
• While not every person will add your PWA to their home screen, every person will "install" your PWA via the service worker.
• An app shell model allows you put your common UI (header, footer, nav, etc.) into the app cache. This makes the first loading experience feel a lot faster. Should you app shell or not? If you have architected as a single page app, this is possible but otherwise might not be worth the effort.
• Animating transitions can help with way-finding and polish on the Web. This gives Web sites even more personality.

Installation and Discovery

• Using a Web manifest file, allows you specify a number of declarations for your app. In addition to name, icon, and even theme colors.
• Once you have a PWA built and a manifest file, browsers will being prompting people to install your Web site. Some Browsers have subtle "add" actions. Other use more explicit banner prompts. "Add to home screen" banners are only displayed when they make sense (certain level of use).
• Developers can request these banners to come up when appropriate. You'll want to trigger these where people are mostly likely to install. (like checkout)
• Microsoft is putting (explicitly and implicitly) PWAs within their app store. Search results may also start highlighting PWAs.
• You can use Trusted Web Activity or PhoneGap to wrap native shells around your PWA to put them into Android and iOS app stores.

Offline Mode

• Your Web site would benefit from offline support. Service Workers enable you to cache assets on your device to load PWAs quickly and to decide what should be available offline.
• You can develop offline pages and/or cache pages people viewed before.
• If you do cache pages, make it clear what data hasn't been updated because it is not available offline.
• You can give people control over what gets cached and what doesn't. So they can decide what they want available for offline viewing.
• If you enable offline interactions, be explicit what interactivity is available and what isn't.

Push Notifications

• Push notifications can help you increase engagement. You can send notifications via a Web browser using PWAs.
• Personal push notifications work best but are difficult to do right. Generic notifications won't be as effective.
• Don't immediately ask people for push notification permissions. Find the right time and place to ask people to turn them on. Make sure you give people control, if you'd don't they can kill them using browser controls.
• In the next version of Chrome, Google will make push notification dialogs blocking (can't be dismissed) so people have to decide if they want notifications on or off. This also requires you to ask for permissions at the right time.

Beyond Progressive Web Apps

• Auto-login with credential management APIs allows you to sign into a site using stored credentials. This streamlines the login process.
• Apple Pay on the Web converged with the Web Payment API so there's one way to use stored payment info on the Web.
• These next gen capabilities are not part of PWAs but make sense within PWAs.

How to Implement PWAs

• Building PWAs is a progressive process, it can be a series of incremental updates that all make sense on their own. As a result, you can have an iterative roadmap.
• Benchmark and measure your improvements so you can use that data to get buy-in for further projects.
• Assess your current Web site's technology. If things aren't reasonably fast to begin with, you need to address that first. If your site is not usable on mobile, start there first.
• Begin by building a baseline PWA (manifest, https, etc.) and then add front-end additions and larger initiatives like payment request and credential api later.
• Every step on the path toward a PWAS make sense on their own. You should encrypt your Web sites. You should make your Web site fast. These are all just steps along the way.

Upper Saddle River, NJ : Addison-Wesley, [2011]