Introducing Quill.js-Based Story Editor for Viking CMS

Our rich text editor:

It's simple. Super simple. It's based on a branch of Quill.js, and has all the features one would need. It generates an HTML snippet of the story content, which is saved in our database. I want to list the buttons to the right of the hyperlink button, that you might not recognize, from left to right:

1. Inline image (like the one above)
2. Embedded livestream (if you are in broadcast, have video encoders on site, and a video provider that supports livestreaming) - we don't because we know what business we aren't in, and that's video trans-coding!
3. the PDF button actually works for many types of files, but PDF is most common. There is a library just for that. They are stored on Amazon S3 just like the story images.
4. A "social embed" button, which is actually an integration with Iframely, because they do the hard work of maintaining 1900 social media connections, so that your "embeds" don't fall apart over time as those vendors grow and change. Not my job!
5. Recipes! We have a recipe library, with ingredients and how to steps, and we can embed those in stories in a beautiful view, that also clicks out to a printable version with just the recipe. This is beyond what even some of the best CMSs offer.

You'll see a few buttons above that, for adding items to the story's "media carousel" which can be a mixture of videos or images if you like. In this case, the video vendor is Viewnexa by Bitcentral, but we can support Field59 by BLOX as well. There are many video solution providers, and we welcome any of them. We don't have a horse in that race! You pick your favorite. Our job is to connect to them in the best way to make your product fast and simple to use. We don't store your video in our video library, we just store it's metadata and index it to stories. We'd rather somebody else manage that data pipe.