In 2010, the Harvard Law Review needed to drag its publishing workflow into the present. The content was extraordinary. The process of getting it online was not. RubyStudio partnered with Winterhouse to redesign the site, rebuild it on modern technology, and give the editors a publishing system worthy of the institution.
The Client
The Harvard Law Review is one of the most important legal publications in the world. It is also, by its nature, a publication without pictures. Long-form legal scholarship, edited to exacting standards, published by some of the sharpest minds in American law. The content speaks for itself. The website needed to do the same.
The Challenge
The problem wasn't finding content. It was everything else. Years of back issues needed to be imported and restructured into a new database. The editorial workflow — manual, time-consuming, friction-filled — needed to be automated. And the reading experience needed genuine rethinking.
A legal journal is not a magazine. There are no photographs to break up the text, no pull quotes over dramatic imagery, no visual relief of the usual kind. The audience arrives prepared for a long read — they are lawyers, scholars, law students; they know what they came for — but prepared and comfortable are not the same thing. Making dense, lengthy legal writing genuinely easy to read online, without resorting to the visual conventions that weren't available, was the real design problem.
Our Approach
The design, created by Betsy Vardell in collaboration with Winterhouse, leaned into the challenge rather than around it. Typography and layout carried the weight that images couldn't. To introduce visual interest without compromising the publication's character, an illustrator was commissioned to create a suite of subtle, law-focused illustrations that appeared randomly in the header — varied enough to feel alive, restrained enough to never distract.
On the technical side, RubyStudio built a bespoke content management interface using its SmallBlock CMS — designed specifically for the way the Review's editors actually worked. Rather than requiring manual entry of each article, the system allowed editors to upload a PDF of an issue, which was then parsed directly into the database. The content could be reviewed, managed, and published from there. A process that had been laborious became, in a meaningful sense, invisible.
The Outcome
The result was a site that honored the Review's authority without feeling frozen in it — readable, structured, and built around the real needs of both its editors and its readers. The old content came with it, preserved and properly structured. The new workflow removed the friction that had stood between the editors and their audience.
The site has since been redesigned and moved to other technology. The version RubyStudio built served the Review well for its time — which, for a publication that has been in continuous operation since 1887, is the appropriate measure.