I’ve spent a lot of time over the past year wrapping my mind around what it means to build a content management platform for lawyers. For nearly a year and a half, LexBlog has completely turned our model of delivery on its head, and shifted our focus from a project-to-project business, to one that focuses on developing new products. As you may guess, the cost of this shift has not been small.

We’ve invested thousands of man hours toward a new options-based theme that all LexBlog customers use while not skipping a beat on design flexibility and style. Our ticketing and project management systems are now centralized (and using more modern software), providing more consistency and support to our customers and visibility for our Success Team. And various methods of delivery are under constant iteration as we take the process of starting and launching a blog with LexBlog from 30-50+ hours of work, to a handful of hours, and slowly empower our clients to take the wheel themselves to successfully start writing on our network.

All of this work has been crucial to our success as a company, and vital to make a successful shift, but it wasn’t until this past week that I’ve felt a significant difference; a wind in my sails, if you will. On Tuesday, after a long New Year’s weekend, our very own Angelo Carosio (@toastercookie for those of you into Twitter and Soundcloud) deployed a tool that he and our Art Director, Brian Biddle, had worked on earlier in the fall/winter of 2016. This tool adds a few new buttons to various areas of the post editor of all LexBlog blogs with the goal to provide each and every blogger on our network with the tools necessary to find and cite cases and link to them in a way that readers can easily access.

This tool, developed using a component of the Fastcase API and with assistance from the Fastcase team, represents a continuation of a philosophical (the notion of opening up the law to lawyers and consumers) and technical (building, delivering, and supporting products through technology and top-notch support) shift here at LexBlog.

Here, let me show you how it works in action. Let’s say that I want to link the text Roe v. Wade to the full text of the case itself. You can see in the gif below, how I’d do that inside our platform:

fastcase-search

As you can see, the link takes you to a publicly available page hosted by Fastcase that includes the case in its entirety. I used the “Look up citation” route to find this case, but the interface supports a general search of the Fastcase database, so if you’re interested in finding a specific citation/link to a case that discusses, say, Eastlake, Seattle (where I live), well, that’s possible too:

2017-01-04 17.15.42

This wouldn’t be possible without piggybacking off of Fastcase’s APIs, and as you may be able to tell, the “Search for a case” feature actually chains together a few different components of that API where we first run a search to get back all of the existing citations for a phrase/term, and then take that citation and get the link after a user interacts with the “Use Citation” or “Use Link” button(s).

All of this is part of an effort to take a rather onerous workflow for many of our customers right now, where they have to hunt down a document or resource online or in a separate researching platform and, if they’re lucky, link to it in their post. More likely, they have to do all of that searching and download the document as a PDF, and upload it to their blogs. Meanwhile, their readers have to open this document in a browser or mobile device which isn’t the friendliest of experience. Our hope is that by providing the tools to conduct some very basic legal research inside our platform, we can encourage authors to continue to write informative posts and make their take on the law accessible to current and potential clients in a way that is open and free to all.