A nicely done short film from MAYA Design that connects the history of intermodal containerization to the data interchange problems we now face in the “age of trillions”.
Actually, Storyteller isn’t a CMS
When trying to describe Storyteller, a term that many gravitate toward is the familiar “Content Management System”. This line of thinking makes sense. For almost as long as the internet has been around, this has been the tool with which you build a website.
But lacking any ability to create or store content of it’s own, Storyteller can’t accurately be called a CMS. Since all content used on a Storyteller website comes from other services, it’s role is focused on aggregating, curating, and presenting that content. The traditional CMS — so long as it offers an API — can even be a source.
For accuracy, we think a slight tweak to the term is in order. Storyteller is a “Content Presentation System”.
Changing the way we build websites
Thanks to mobile devices and cloud computing, there’s now more web APIs than ever before, and they’re getting better and better. JSON, RESTful design, OAuth 2, and good documentation are all qualities we commonly find in popular APIs today. This consistency is delivering awesome interoperability, leveraged by services like ifttt and Zapier. More importantly, it’s helping developers everywhere focus on doing what they do best. As a result, for almost any problem you can think of, the cloud has an app for that.
With reignited browser wars and resumed progress on the frontend, it’s an exciting time to build websites. Designers everywhere are learning to code and the web is becoming such a better place for it. Meanwhile, our tools haven’t changed much: a CMS, FTP, reload, rinse, repeat. We’re able to get by of course, and with motivation easy to find, many learn what they must. While there have been evolutionary advances, to really move forward we need to go beyond the confines of the desktop.
In the modern API ecosystem there is a tremendous opportunity to change the way we build websites. What if we separated our developer tools and servers from the systems we use to produce and manage content? What if you could build an entire website with content exclusively provided by APIs? The sheer number of providers out there and the rapid maturity of the services they offer make the traditional all-in-one CMS look quaint in comparison.
“It’s sort of like a jQuery for content APIs.”
Bryan Buchanan, our friend and frequent Sparkart collaborator over at Resen, had this to say about Storyteller today. We think he’s spot on.
Likewise, Storyteller tackles many of the hurdles developers currently face when working with APIs. Focus on exploring and presenting content that’s available across the web rather than how you’re accessing and serving it.