Meet PubSweet – Coko’s free, open source framework for building state-of-the-art publishing platforms


PubSweet logo

PubSweet is Coko’s free, open source framework for building state-of-the-art publishing platforms. PubSweet enables you to easily build a publishing platform tailored to your own needs. It is designed to be modular and flexible.

PubSweet can be used to rapidly create custom publishing systems. If the existing components do not completely meet your needs, you can focus development on building new components to provide just the new functionality required.

Join the PubSweet community and help us build a common resource of open components for publishing by contributing components back.

Documentation and further information about PubSweet can be found here. Below are Publishing platforms built with PubSweet.

Publishing platforms built with PubSweet

  • Hindawi's Phenom

    Journal submission and peer review platform

    Journals publishing and technology organization Hindawi Ltd. has developed a manuscript submission and peer review platform currently in live use. In addition to this, they’ve begun work on additional tools using PubSweet.

    Submission and Peer Review – this platform is live for a low volume journal, with 20 succesful live submissions so far, and one accepted article which has gone through the entire process and is now being prepared for publication.

    Hindawi Ltd. will make the platform multi-tenanted, to roll out across subsequent journals. They are leading the charge in the Coko community on the multi-tenancy approach.

    In addition to submission and peer review, and multi-tenancy, Hindawi Ltd. are also building a QA platform on top of PubSweet. All of the code is open and available to be reused.

    It took less than one year for Hindawi Ltd. to develop and begin live use of their platform. They were the first PubSweet Community member to launch with live submissions. After gaining this experience, they decided to add development resource, now with 18 people working on different PubSweet developments for the organization.

  • Libero Reviewer

    Manuscript Submission and Peer Review as imagined by eLife within the PubSweet Community.

    eLife chose to begin their development by working toward incremental replacement of a previous system. The first phase is represented by early release of a submission workflow. Today, 60% of all submissions go through their PubSweet submission component. From here, the submission flows into a legacy proprietary system for Peer Review. Interestingly, the content is transferred between the two systems using a MECA bundle, representing the first live use of MECA. Because eLife is building modularly within the community, their MECA component is, of course, is open source and available to anyone building a PubSweet platform.

    It took just over one year for eLife to deliver this first critical component to their much larger end-to-end workflow strategy underpinned by PubSweet.

    Looking forward, eLife’s workflow will be a series of inter-connected PubSweet apps. Any of these apps could be reused by anyone building with PubSweet. Within the community there are a variety of approaches to similar problems, and the multiple app proposition is one example of this. They will name each standalone app with the prefix Libero (eg Libero Publisher, Libero Reviewer etc).

  • Europe PMC Plus The EBI (European Bioinformatics Institute) platform, Europe PMC Plus, is a multiple source post-publish QA system for content aggregation (pushing to EuropePMC). It supports manual input through a submission wizard, as well as batch FTP upload/submission. Although built specifically for their workflow, it is conceivable the platform could be used for any workflow requiring post acceptance/production QA. It will go live in May.

    Interesting features include annotations using Nick Stennings Annotator, to QA XML. They are also using Coko’s XSweet for docx to HTML conversion. EBI have built this extremely fast, in a matter of months, with a development team of around four developers.

    EBI generously hosts most of the PubSweet Community meetings, and of course make all work available Open Source.

  • Editoria

    Community-led Open Source Books Production platform. Built by the Coko team

    Editoria the fully fledged post-acquisition book production workflow developed by the Coko team in collaboration with the University of California Press (UCP) and the California Digital Library. Editoria is now in live use by UCP, ATLA Press, punctum books, M Publishing, UNC Press/Longleaf Services and Book Sprints.

    There is a healthy community evolving around the product, as well as a forthcoming hosting vendor agreement (stay tuned). Editoria is completely open source. Our team of two developers works on the core Editoria platform, however much more horsepower is added when you consider development done on CSS stylesheets, paged.js, XSweet (docx to HTML conversion) and Wax (editor).

    External site


    Micropublications Platform as envisioned by CalTech's WormBase and built by the Coko team.

    WormBase commissioned the Coko team to develop a micropublications platform for their project. It follows a simple micropubs workflow which has been designed and built to allow for its re-purposing by any micropubs use case. The real key difference between a journals workflow and micropubs is the scope of material submitted and the intention to process it very quickly.

    This platform has been in active development for a year. It is likely that the platform will be in live use this year. Everything developed for Wormbase is fully open source, created currently by one (extremely productive) Coko developer.

  • Digital Science

    Digital Science‘s Innovations Team is building a very interesting awards system using PubSweet. In a broader sense, their strategy within the community is to build a system with configurable workflows. The functionality would allow a user to design a workflow, export, and access a PubSweet app that is automatically compiled to suit.

    All work is open source, and so far there is one developer working on these projects.