- Views 411
With this open-source, community-owned approach, you own your infrastructure and you can choose to use any service provider you like.
In a webinar on March 11, the team at eLife gave an update on Libero Publisher – one component of the open-source publishing technology suite eLife is building – and how publishers, libraries and developers can collaborate on the project.
To provide feedback on our plans, you can join the conversation on the Libero slack channel, explore the development roadmap, find the code on GitHub, and just let us know to get in touch with you by emailing email@example.com.
Libero encompasses the open-source, end-to-end publishing workflow that eLife is developing, both for its own purposes and to help other organisations looking to modernise and increase efficiency for their operations. Current projects that fall under the Libero umbrella include Libero Reviewer (being developed in concert with the Collaborative Knowledge Foundation (Coko) and others), the content production tool Texture (developed with Substance Software GmbH), and Libero Publisher (eLife’s content delivery platform).
Community-driven and also open-source, Libero Publisher presents content in a responsive online format that is easy to access and inviting to read on any device and is straightforward to integrate with other services that enhance the reader’s interaction with published literature. The software is built from the ground up, with a modular architecture and reusable, state-of-the-art, accessible front-end patterns that let anyone inspired by the eLife journal website to recreate its user-driven, user-research-backed experience.
While Libero Publisher was originally developed by eLife, the organisation has partnered with Coko, Hindawi Limited and Digirati to develop the latest version of the platform. Our collective aim is to facilitate its adoption by other organisations and expand a high-quality, cost-effective and open infrastructure as an alternative to more expensive proprietary systems.
Questions and comments are welcome. Please annotate publicly on the article or contact us at hello [at] elifesciences [dot] org.