Workflow is greater than feature set

If you follow Coko’s work, you likely know a bit about Editoria. It’s open source, browser based, and pretty awesome! There are all the features, but how, specifically, does it support workflows? Which workflows?

Now that the system is not only operational and in use by several organizations, and we’ve announced that hosted deployments are coming soon, it’s time to think about how it can help you.

Workflow > features

Today, Editoria supports two workflows “out of the box.” They are: 1) Post-acquisition production workflow and 2) Flat collaborative workflow. Here’s a little more about how each of these came to be, and what they entail in terms of support from the technology.

Post-acquisition production workflow

University of California Press editors receive content “post-acquisition” as word files (.docx). From here, files are loaded into Editoria for styling, formatting, copyediting, proofreading, and review steps. All of these steps are tracked within Editoria by specific workflow participants, for each chapter.

Flat collaborative workflow

Book Sprints authors content within Editoria during facilitated content creation “sprints” or sessions with subject matter experts. They employ a “flat” approach to roles and permissions for this reason. They allow everyone the same permissions and manage who is responsible for what within the system socially. This works because they are all in a single location doing focused and highly collaborative work.

And you? What is your workflow? Let’s set up a time to catch up, map it out, and assess Editoria’s capability to support you.

 

Further reading