Thinking Ahead for Emergency UI When Building a Website


In this episode of Syntax, Scott and Wes talk about emergency UI when building a website. During an emergency, you need to relay information to your website visitors as quickly and efficiently as possible. How do you do that? What do you need in place on your website?

Sanity - Sponsor is a real-time headless CMS with a fully customizable Content Studio built in React. Get a Sanity powered site up and running in minutes at Get an awesome supercharged free developer plan on

Sentry - Sponsor

If you want to know what’s happening with your errors, track them with Sentry. Sentry is open-source error tracking that helps developers monitor and fix crashes in real time. Cut your time on error resolution from five hours to five minutes. It works with any language and integrates with dozens of other services. Syntax listeners can get two months for free by visiting and using the coupon code “tastytreat”.

Show Notes

5:40 - Banners and popups

  • Interfere
  • Static
  • Dismissible
  • Cookie/localstorage
  • When that popup is updated, it should show again. Maybe use a hash of the content? Or length? Something that resets itself every time the content is updated.
  • Private client-side-only PWAs are hard

14:35 - Good styling

  • What happens if they add an image?
  • Do they have access to the branded fonts and colors in their WYSIWYG?
  • Can you revoke 100px red Times New Roman?

18:32 - Page alerts

  • Yellow, green, red
  • Alerts on existing pages

21:08 - New pages

  • Is there a good template for new pages?
  • Can they easily set the slug?
  • Can they add it to the nav?

23:52 - Google’s “Hours of Operation”

25:43 - Other

34:38 - Deployment

  • Detail how to deploy everything
  • It might have been years and the CSS will only compile on Node 6 and Gulp 3
  • Do any caches need clearing?
  • Does the CSS need to be cache busted?
Links ××× SIIIIICK ××× PIIIICKS ××× Shameless Plugs Tweet us your tasty treats!

Audio Player