Originally Posted by donheff
Correct, but what I was reacting to is that a whole weekend down is not what the standard "regular maintenance" is about. No one regularly schedules websites to be down for the whole weekend. This is let's pray we can fixit maintenance or to be non-specific just maintenance..
Wildly offtopic now, but... The State of California is... noteworthy... for it's web sites. One of the "Best Web Sites Evar" was the Registrar's Office for the California State University system campuses back in the early 2000's. The silly thing kept office hours. Yes, the web site was only available from 8:30 AM until 5 PM Monday-Friday. I'm pretty sure the sophisticated back end processing consisted of a printer, from which an employee would regularly remove paper and then FAX to the appropriate office.
Just shutting down for the weekend as part of their rollout is pretty mild stuff. They also had shutdowns planned for the middle of the night last week for more urgent changes. This isn't exactly a 'sky is the limit' bigtime commercial project rollout. It's more of a 'built by the lowest bidder', 'compliant with state and federal privacy regulations for medical and tax data', proceeding with caution sort of project. If you want to think of it as a live beta test, well, yeah. The preferred terms are 'rapid prototyping' and 'spiral development'. Yaaay! Buzzwords!
Folks who are really curious about how the web site is being bolted together can check out the UX 2014 project, which provides a reference front-end implementation: