Halvorson, Kristina

Beaird, Jason, author

Powers, David, author

Grannell, Craig

Angel, Edward, author

Dewey Library - HM851.W357 2019

Dewey Library - HM851.S535 2020

Webster, Thomas H, author

The Magical World of Web Animation Milly Rowett, Senior Developer REA Group Back when we were kids, we used to have fun browsing the web, it was a magical playground full of colours, moving parts and games. Now we see browsing as a reluctant job to be done; finding a house, searching a recipe. Utilising […]

The post Web Directions Code ’20 session spotlight–The Magical World of Web Animation appeared first on Web Directions.

JavaScript debugging the hard way Marcin Szczepanski, Principal Developer Atlassian Error on line 1, column 6532112 of bundle.js? Out of memory error trying to load a CPU profile into the Chrome debugger? Two minutes to see wait and see if a change you made fixed a bug? While upgrading our complex web application from Webpack […]

The post Web Directions Code ’20 session spotlight–JavaScript debugging the hard way appeared first on Web Directions.

Making Single Page Apps Accessible Jess Budd, Front End Developer HBF Javascript frameworks get a bad rap when it comes to accessibility. But is it the frameworks creating the barriers, or us as the developers? Follow me on a journey through div soup, past the lost focus and under the unchanged titles. Find out: is […]

The post Web Directions Code ’20 session spotlight–Making Single Page Apps Accessible appeared first on Web Directions.

Know Your HTML Chris Lienert, Front End Technical Lead Iress HTML didn’t stop at version 5 and it continues to evolve. Chris Lienert will review a number of HTML elements and attributes that are new and (somewhat!) ready to be used. About Chris Lienert Chris started out as a web developer when Netscape ruled the […]

The post Web Directions Code ’20 session spotlight–Know Your HTML appeared first on Web Directions.

The State of the DOM Marcos Caceres, Standards Engineer Mozilla The DOM, while not quite as old as the Web itself, has been with us for the entire professional lifetime of almost every web developer. But its far from fixed in stone. Now the responsibility of the WHATWG it continues to evolve in response to […]

The post Web Directions Code ’20 session spotlight–The State of the DOM appeared first on Web Directions.

Evolving Web APIs for everyday developers Michael Mifsud, Senior platforms engineer Redbubble JavaScript is evolving quickly, and with it so the Web APIs. In just a few years it’s grown from humble callbacks to include generators, async iterations, and async functions. With this growth has come fragmentation not just in the availability of APIs but […]

The post Web Directions Code ’20 session spotlight–Evolving Web APIs for everyday developers appeared first on Web Directions.

Tuning web performance with just browser APIs Yaser Adel Mehraban, Lead Consultant Telstra Purple As web applications become more complex, with a corresponding increase in required bandwidth and bundle sizes, to meet users’ expectations the need to consider web performance has never been more important. Yes, there are third-party tools that can help with performance […]

The post Web Directions Code ’20 session spotlight–Tuning web performance with just browser APIs appeared first on Web Directions.

Web Assembly at the Edge Mark Nottingham, Principal Engineer Fastly Full session details coming soon About Mark Nottingham Mark Nottingham has helped develop the Web and the Internet since the late 90’s. He has written, edited or substantially contributed to more than twenty IETF RFCs and W3C Recommendations about topics like HTTP, caching, linking, Web […]

The post Web Directions Code ’20 session spotlight–Web Assembly at the Edge appeared first on Web Directions.

Cambridge, Mass. : National Bureau of Economic Research, 2020

Connolly, Randy, 1964-

Stiller, Evelyn, author

Howe, Shay, author

Sikora, Piotr, author

Nunn, Jeremy, author

Deitel, Paul J., author

Felke-Morris, Terry, author

Felke-Morris, Terry

Connolly, Randy, 1964- author

Felke-Morris, Terry

The ministry said the webinar series will provide information on the many destinations and the 'depth' and 'expanse' of the culture and heritage of India. The first webinar on Tuesday touched upon the history of Delhi and was titled " City of Cities- Delhi's Personal Diary'.

I've noticed that there are very few moms speaking at conferences in our industry. I'd like us to do our little part to make it easier for women to work in technology fields by making web design and development conferences more mom-friendly. This can help all of us, not just the moms.

I ran into a very frustrating bug while using icon fonts on our site at Contatta. A bug I filed last April, and nurtured through the process of getting fixed, didn’t make the Mozilla release notes (though it was included in Firefox 28). Because I feel it’s a very useful solution, I wanted to bring [...]

This talk about recreating the first ever web browser was a joint presentation with Remy Sharp, delivered at the Fronteers conference in Amsterdam in October 2019.

An interview conducted by Vitaly Friedman ahead of the 2019 View Source conference in Amsterdam.

The opening presentation from the Beyond Tellerrand conference held in Berlin in November 2019.

Fry, Christopher, 1907-2005

Middleman is a Ruby based static site generator which we use heavily at Kollegorna both for prototyping (checkout our Middleman boilerplate) and production sites. In my previous article on Service Worker, I overviewed the most common challenges you may face when implementing the technology. This time I’d like to dive into a single specific topic of enabling a worker on Middleman based website as there are a few things to deal with…

Read the article

Hayden Library - T174.7.B56 2016

Online Resource

Dewey Library - QH501.D38 2019

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.

This post explores the emerging popularity of 3D for creating highly interactive web sites.

Nicole finally gets a chance to hack into a personal email, only to find herself in the bowels of Agent Topple's locked messages from the 90s. As imagined, this is unfortunate.

At The Boss junket, Melissa McCarthy and Kristen Bell answer a Google Autocomplete interview together.

NASA astronauts Tim Kopra and Jeff Williams and European Space Agency astronaut Tim Peake are currently living on board the International Space station and answer the internet’s most searched questions in the latest installment of WIRED’s Autocomplete Interview.

Ice Cube takes WIRED's Autocomplete Interview, answering the world's most searched questions about himself.

Common takes WIRED's Autocomplete Interview, answering the most searched questions about him.

Eve takes WIRED's Autocomplete Interview, answering the most searched questions about herself.

Seth Rogen and Rose Byrne, stars of upcoming film 'Neighbors 2,' answer the internet’s most searched questions in WIRED's Autocomplete interview.

Travis Fimmel, Paula Patton, Toby Kebbell, and Robert Kazinsky answer the web's most searched questions about themselves and World of Warcraft.

MatPat, AsapSCIENCE, The Slow Mo Guys and Burnie Burns answer the internet's most searched questions about YouTube, influencers, fame, and of course themselves.