The first thing we did in this regard is to distinguish between two similar pages. We have a "crisis web page" and we have an "emergency web page".
The crisis web page is simply a dumbed down version of our home page, no images. It stands ready to be used when needed. The main goal for this page is to prevent our server from crashing in a situation where we expect a major spike in traffic. Such a situation could be a crime on campus (i.e. Virginia Tech), a major dignitary visiting campus, (U.S. president, Pope, etc). Any local situation that would cause a major spike web traffic qualifies. The page itself is designed to get visitors to the major information they need with one click. While other standard links still exist, the usual priorities of recruiting, soliciting donations, etc take a back seat during this situation.
The emergency web page is used when something happens to prevent access to our usual web server. Our web site is hosted here on campus. So, for example, if a tornado wipes out the IT building, we'd need to use the emergency site. Or if our internet access goes down for whatever reason, we'd need it (like when someone accidentally cut a fiber line not far from campus a couple years ago, which prevented the world from seeing our web site for a few hours). Our emergency site is hosted 130 miles from campus. It's new, so we haven't used it yet. If/when something happens, a couple of us need to leave campus and go to a place with internet access (i.e. home). Another guy takes care of flipping some DNS settings. I take care of the site content itself.
There are situations where both of the above could end up being the same site, like if a tornado hits campus. But it's important to know the differences. For us, the crisis page still provides access to the entire site, but with a dumbed down home page; it's assumed the IT infrastructure is still in place. On the other hand, the emergency site is only a couple of pages (with the ability to grow), meant to give info to the visitor as to why they cannot access our site.
There are campuses who use mirroring to make sure that their emergency site is still a complete web site. We just choose not to do that (everything has its costs).
We don't have anything as of yet, but it is on my list of things to do by the end of the year. We do have some crisis workflow policy in place, and I plan on talking to the PR people who would be responsible for getting the information out to see what we would need to facilitate getting all the key data from point A to point B in the lightest weight way possible.
Of note, our CMS has a good caching system, so once the page is loaded once, it doesn't hit the database for it again unless the information changes.
Also of note, isn't it sad that we have to account for such things these days?
We do have an alert system on the homepage. Not exactly the same things you guys are talking about here though. We use it for cases like University Closing due to Weather Conditions and the like. Basically a div with information shows up on page load. The div can then be closed.
Sounds like a good idea to have these other measures in place though.
"Switching to a new CMS? Join our next webcast with Briana Johnson from @OSUIT to learn how to convince decentralized web content authors to tolerate the switch, actively participate, and enjoy it! http://bit.ly/2zhdcIt"
"Your website is the front door to your college or university. Your website design has to accommodate for the way that students interact with and use the information your institution provides. http://bit.ly/2P8VldR"
"Join us for our next webcast with OmniUpdate CEO Lance Merker, who will delve into key insights about Generation Z’s online search behaviors to help you refine your school's web marketing strategy. http://bit.ly/2zhdcIt"
"Our newest guide will help you learn what it means to be accessible, how to implement accessibility best practices, quick fixes to try as well as a long-term plan, plus tools to help you in your website accessibility efforts. Download it now!"
"Are online forms more efficient? Learn how El Camino College used Formstack to create online forms that expedited processing, improved communications, increased transparency, and promoted accountability across campus. http://bit.ly/2zhdcIt"
"If you’re struggling with web challenges such as accessibility, SEO, design consistency, workflow, content governance, or how to start a website redesign, you’re not alone. Join our next webcast to learn how other higher ed institutions…"
"Here’s an outline of everything you need to know about OCR compliance, including what it is, what your college or university can do to stay compliant, and resources for OCR compliance. #accessibility http://bit.ly/2rcPDgG"
"Join us for our next webcast with April Buscher from Montana State University Billings to learn how blind readers and people with hearing impairment view and read your website and how you can make it accessible to them. http://bit.ly/2zhdcIt"
"High schoolers spend more time on their digital devices than they do sleeping, doing homework, or participating in extracurricular activities. So how do you make your message stand out to them? #eexpect http://bit.ly/2MOIIWC"
"Want to increase digital engagement with high school juniors and seniors? Join our next webcast with Stephanie Geyer from Ruffalo Noel Levitz as she shares new data from the 2019 E-Expectations Trend Report on email, paid media, and social media…"