Editoria Webinar

This week, Coko hosted a webinar focused on Editoria. Many attendees participated in the live broadcast, which included a Q&A session, in addition to the Editoria origin story, live demonstration, and a presentation on open source sustainability.

Watch the webinar in full here:

Engage with Editoria: How to get involved with the community

There has never been a tool quite like Editoria.

Several elements make Editoria unique, setting it far apart from open and proprietary tools that came before it. It was designed by subject matter experts and actual users! And the ability to author, edit, style, typeset and output books in browsers is revolutionary! The efficiencies that university presses and library publishers realize as a result of automated production and typesetting workflows add up to significant opportunities to scale output of monographs and other urgent academic works. All these benefits rest atop an open source infrastructure that places the academy in the driver’s seat. This is very different from working with third-party vendors who control the roadmap while locking presses in.

Still, one of the most important components of open source software is community. Communities support adopters, developers and users. Healthy communities operate in good faith, with transparency and trust, and the whole ecosystem benefits.

Here are some actions you can take today if you’d like to get involved in the Editoria community. Whether your interest is passive, or you are considering adding resources to the project, here are some ideas to get you started:

Sign up for the mailing list

The Editoria landscape is changing fast. You’ll want to know who’s adopting, what’s rolling out, where adopters are speaking, and when a new website is launching (hint: it includes a sandbox you can immediately use to experience Editoria first hand, with no setup required)! The simplest way to do this is to sign up for the Coko Foundation’s Editoria mailing list.

Register for a webinar

Editoria webinars are a fast and interactive way to come up to speed on how and why Editoria was created, as well as on the organizations involved. Hear about the problems Editoria solves directly from the founding adopters and users themselves. Interact directly with the team during Q & A. Sign up to attend!

Check the schedule

Community members are taking Editoria on the road this spring! Check out the Events schedule for a full listing of our meeting participation. Let us know if you’d like to meet up!

Do your due diligence

DSC05299-768x512Check on the health and vibrance of our community within our gitlab repository and mattermost chat channel. Fair warning: many smart people working on and discussing really interesting things in a fun and collaborative manner. 🙂

Read The Cabbage Tree Method

CoverNextJu-Front01

Coko Co-Founder Adam Hyde literally wrote the book on Open Source Collaborative Product Development. It is following this method that University of California Press’ Editorial and Production staff designed Editoria! The Cabbage Tree Method (CTM for short) emphasizes that the subject matter experts, those who will use the tool themselves, drive the decision-making during a facilitated collaborative design process:

“A fundamental rule of CTM is that no one speaks for the users, other than the users themselves.”

Also, this text was the first published Editoria output!

Drop the Community Manager a note

DSC05290-768x512If you like what you see, please let me know? I’m new to the Community Manager role and I am interested to talk with others who are new to Editoria, the community, Coko, and share perspectives. I’d love to learn about your organization, current workflows, and future directions. I can also help you strategize next steps for evaluating your interest or increasing your involvement.

Follow us on social media

There are several ways to keep up with Coko and Editoria on social media. Here they are:

Editoria on Twitter
Coko Foundation on the web
Coko Foundation on Twitter
Coko Foundation on Linked In

p.s. Maybe bookmark this page as an updated Editoria website (with sandbox) launches soon!

Share with your community!

Open source initiatives thrive when community members share code and in-kind resources. A major resource useful to growing the Editoria community will be shared contacts. If you like what you see, tell your friends and colleagues. If you have a newsletter or blog or other platform or channel, please consider featuring Editoria’s founding adopter perspectives, or early adopter use cases. Interesting content, and plenty of it!

There you go! Many resources to begin engaging with our community. Choose your level of involvement and go for it! I’d be delighted to hear from you!

Welcome, Alison McGonagle-O’Connell!

We are delighted to welcome Alison McGonagle-O’Connell to the Editoria team as the new Editoria Community Manager. Alison has a long history in the publishing and technology industries, having held positions at Wiley, EBSCO, and Aries Systems. Most recently Alison was Global Product & Partner Marketing Manager at Aries, but Alison also spent a good amount of time as a production editor, so she is certainly no stranger to production workflows!


In this new role, Alison will be working closely with the Coko team—who have been helping us build Editoria—and will be managing the publisher, developer, and service provider communities for Editoria. Alison will play a key role in the evolution of Editoria, and will be driving and encouraging adoption and interfacing with members of the Editoria community. Catherine Mitchell (CDL), the Coko team, and I look forward to working closely with Alison. She will often be tweeting updates as @editoriapub. Follow us on Twitter to find out what’s happening with Editoria, and look for a email news (and a redesigned Editoria website) in the coming weeks. Please join us in welcoming Alison to the Editoria team!

Editoria meetings at UCP

These last 2 weeks Coko developers Yannis Barlas and Christos Kokosias have been working alongside Kate Warne and Cindy Fulton from UCP.

Yannis and Christos came to San Francisco (from Athens) for 3 weeks specifically to work with Kate and Cindy on some new features. Out of these meetings we now have some exciting new features that we will write more about on this blog soon!

While in San Francisco Christos and Yannis also met with the wider UCP staff to demonstrate Editoria and discuss the future of the application.

There was a lot of excitement about the application and a fantastic discussion about possible future features.

Editoria Update

Recent changes to Editoria.

Added

  • Clicking on a source note’s number in the notes editor snaps the main content editor to the source note’s callout #37

Changed

  • Updated track changes buttons for consistent capitalization (“Record Changes” is now “Record changes” and “Recording Changes” is now “Recording changes”) #62
  • Numbers in the note callout icon moved higher up to be more legible and look more natural #15
  • Application title changed from “Pubsweet app” to “Editoria” #24
  • Focus moves back to main editor with active cursor after clicking any of the track changes buttons (“Record/Recording changes” and “Show/Hide changes”) #60
  • Source Note style changed from inline style to a block-level style. Removed icon from top formatting tool bar, and added Source Note to the styling pane in two places #49
  • Switched the placement of the “Edit/View” and “Rename” buttons for components in the Book Builder interface to reflect the relative frequency of these actions #30
  • In the Book Builder interface, double clicking a component name now opens it in the editor, rather than opening a text field to rename the component #31
  • Changed capitalization of “Back To book” button to “Back to book” #32
  • When authors or copyeditors are about to change a workflow state in a way that will revoke their “edit” access, they see a warning message. The text of this warning message has been updated for clarity, to: “You won’t be able to edit this chapter after updating this workflow status. Are you sure you wish to continue?” #34
  • Some styles have been renamed (lists, subtitles, dialogue), and the order and groupings of styles have been updated #48
  • The currently applied style is more easily visible in the style panel across different displays (the applied style name changes more dramatically than before) #50
  • Upon exiting the editor with unsaved changes, the option on the warning screen to “Cancel” and go back to the editor has changed to “Take me back to the editor” for clarity #9
  • Users with author or copyeditor role no longer see non-functional buttons to “Rename” or “Delete” books from the book dashboard #26

Removed

  • Bold package removed from the note editor #17

Fixed

  • Resolving a comment no longer breaks the appearance of some of the styles in the editor (Subtitle, Extract: Poetry, Extract: Prose, Epigraph: Poetry, or Epigraph: Prose), #61
  • Font ligatures have been disabled in the editor, fixing the issue of certain character sequences combining into one character and causing the cursor to skip (e.g. “ff” and “fl”) #18
  • Book components can be dragged and dropped to rearrange after exiting the Wax editor (Substance drag-and-drop now properly disconnects) #19
  • Resolved font warning upon loading the editor #27
  • When exiting the editor, the bug where the user had to click “Save and quit” or “Quit without saving” multiple times has been resolved #20