When Boston.com buckled under the pressure of the traffic that news of the explosions sent its way, the site redirected its homepage to ScribbleLive, allowing Boston.com to still update their readers in real-time even after the site went down. 

By Belinda Alzner, for ScribbleLive

(Alzner is a former associate editor of J-Source. This post was originally published on ScribbleLive and reprinted here with the company's permission.) 


Yesterday was Patriots’ Day in the United States. It was a day that was, for so many, about doing nothing more than crossing a finish line.

Until it wasn’t.
All it took was a moment for people across North America and the world to stop what they were doing and turn their attention to Boston; for yesterday to become a day that sports reporters scrapped routine copy for capturing, filtering and reporting breaking news; for reporters and editors alike to think on their feet and make decisions in real-time. That moment was at 04:09:51 of the 117th Boston Marathon, to be exact, when the first explosion occurred at the finish line of the race.
As we all know, the new reality of breaking news is that journalists tell their readers what they know, as they discover it, in real-time. After all, “if journalism is the first draft of history, live blogging is the first draft of journalism,” as Andrew Sparrow wrote for The Guardian, after liveblogging the entirety of the United Kingdom general election in 2010. And that type of real-time reporting is what so many newsrooms did yesterday, in the aftermath of the explosions in Boston.
ScribbleLive and Boston.com

Boston.com had been gearing up for its coverage of the marathon for some time. They placed the event in ScribbleLive’s Syndication Marketplace, offering its content about the race for free to any ScribbleLive clients. A dozen or so picked it up.
At about 3 p.m. ET, the explosions happened. Boston.com continued to update their marathon liveblog with updates about the blasts, but they also shifted gears, creating a new liveblog dedicated to the explosions in Copley Square. The first post linked to a Facebook photo posted by Boston.com sports producer Steve Silva.
From there, Boston.com posted more photos of the immediate aftermath, maps of the area and where the bombs went off, and provided updates from their reporters on the ground as well as informational posts from official social media accounts to try to amplify their reach.
But Boston.com buckled under the pressure of the traffic that news of the explosions sent its way.
At ScribbleLive HQ, we worked with Boston.com to redirect its homepage to its ScribbleLive white label of the liveblog that they were running. (For those who don’t know, a ScribbleLive white label is where all your Scribble events live. It’s created by scraping a template of your website, and hosted on our servers.)
Meaning: Even though Boston.com went down, they were still able to update their readers in real-time.
The page looked and felt exactly like a Boston.com page, but it was hosted by ScribbleLive. Boston.com continued updating their readers in real-time, with video, photos and text. They tweeted out updates, linking to their developing coverage. They used maps to demonstrate the locked-down area, and they provided updates for people looking for loved ones. Reporters were filing longer stories from the scene of the explosion to the liveblog, and were able to share those individual stories across social platforms using the permalink associated with each post. More examples of reporters’ filing to Boston.com’s liveblog can be found here, here and here.
Yesterday, Scribble was used as we have always intended it to be: As news organizations’ choice for their live content management system.

Tamara Baluja is an award-winning journalist with CBC Vancouver and the 2018 Michener-Deacon fellow for journalism education. She was the associate editor for J-Source from 2013-2014.