You Spoke. We Listened.
We think it’s important to make sure we prioritize what comes next, and to a certain extent, we rely on you guys to keep us headed in the right direction.
Our feedback survey has been available for a few weeks now (fill it out for your chance to win an iPad Air!), and the most common type of feedback we have received is regarding our “documentation.” We would have never put that into “quotes” before but now we see our docs in a whole new light. You see, the docs were written by a developer, so they’re mainly in the mentality of, well, writing code.
When we initially launched Aesop Story Engine, we documented what each option did, which was fine… for developers. However it became painfully obvious that this route was not the best type of documentation for end users – so we did something about it.
Actually, we did a lot of things about it, and we’re really excited to give you a sneak peak into what’s happening next.
Aesop Help Center
[aesop_image img=”http://aesopstoryengine.com/wp-content/uploads/2014/06/BrAxBReCYAAoFVs.png” imgwidth=”content” caption=”New Aesop Help Center to be completed within two weeks” align=”center” captionposition=”center” lightbox=”off”]
The upcoming Aesop Help Center has been built with you in mind. 100+ component options have been rewritten to not be so developer focused. 13 new videos are being recorded to give you an in depth look into each component and how you can use them in your projects. We’re also actively writing a series of tutorials that go even deeper into how to use each component, complete with step-by-step screenshots.
Better Option Descriptions
[aesop_image img=”http://aesopstoryengine.com/wp-content/uploads/2014/06/Gus16ZpRxg.gif” imgwidth=”660px” caption=”Better option descriptions coming in Aesop Story Engine 1.0.8″ align=”center” captionposition=”center” lightbox=”off”]
Aesop Story Engine 1.0.8 is primarily focused on usability. Previously, each option had only a label, leaving most of you to wonder what the heck the option did. Unfortunately this led to confusion on how to use some of the Aesop components. We solved this problem by providing a tooltip-style description for each option, in every component, within the Aesop Story Engine generator.
[aesop_image img=”http://aesopstoryengine.com/wp-content/uploads/2014/06/editble-components.png” imgwidth=”content” caption=”Editable story components coming in Aesop Story Engine 1.1″ align=”center” captionposition=”center” lightbox=”off”]
Since we first released Aesop Story Engine, we’ve updated the plugin eight times, added 34 new options, and fixed 134 bugs. As we head into the development of Aesop 1.1, we’ll be focused on usability of the interface. Currently, in order to edit a component you either have to edit the text inside the shortcode or re-generate it completely. We know that’s not user-friendly and we’re going to fix it.
In 1.1, we’re solving this issue by introducing editable components. With editable components, you’ll be able to click the “edit” icon to bring up the component editor – easy! No more re-generating the component. No more editing the text. Our goal is to vastly improve the workflow for publishers by giving you quick access to manipulate and change components with as little friction as possible.
Original Story Series
[aesop_image img=”http://aesopstoryengine.com/wp-content/uploads/2014/06/Image-2014-05-28-at-4.30.48-PM.png” imgwidth=”800px” caption=”Original stories brought to life with Aesop Story Engine” align=”center” captionposition=”center” lightbox=”off”]
Looking for a good story to read this summer in a way that you never thought was possible? Sign up to be notified when our Original Story Series launches this summer. You won’t want to miss this amazing project!
In addition to the amazingness above, we’ve got a new theme planned for release in July and a few more surprises up our sleeves that we’ll hold on to for now. What are you looking forward to the most? Is there anything specific that you’d like to see in Aesop? Sound off in the comments below, through our feedback form, in our survey, or on Twitter @aesopinteractiv!