** DRAFT DOCUMENTATION **
- Conceptual overview
- A comment about the the technology
- Architecture overview
- Component description
- Article processing flow
- A note about file formats and file naming
- A note about communication with Drupal
- Installation and Deployment - DRAFT
- Feedback and mailing list
eLife Continuum is the platform that we use to manage the publishing and hosting or our research content. It is composed of a set of software components that form a publishing and article hosting system. In this documentation we will describe those components and how they fit together. We will describe how they can be deployed and customised.
eLife continuum is best described as a production and hosting platform It takes article packages from a content processor and then transforms those packages so that they can be hosted on the web. It also provides production teams with a dashboard to manage the publishing and scheduling of articles. It provides a Drupal 7 site that can be used to host that journal content. It is built out of a number of software components, and these components mostly interact through a set of well described APIs, meaning that different parts of the system can be replaced or extended with relative ease.
A comment about the the technology
Most of the back-end components are written in python, with the hosting platform built on top of Drupal. We make liberal use of Amazon Web Services, and use a variety of storage engines exposed via RDS, including MySQL and Postgres. Redis is also used to store session information.
We manage workflows using AWS Simple WorkFlow.
The actual software resides in the following repositories
Documentation and tools for building the components live in the following repositories
eLife Continuum is licensed under the MIT License .