ppp project related files and prototypes
HTML Python
Clone or download
Permalink
Failed to load latest commit information.
architecture-diagrams updated old out of date arch diagram Mar 10, 2016
dashboard-documentation added definition of 'current' tab Oct 21, 2015
deploy_on_aws Clarification on builder-private-example and example.top Aug 15, 2017
eLife_bot_eLife2.0 Edit diagrams instructions Nov 4, 2016
elife-continuum-docs Cleaned up the start of README Jun 13, 2017
file-naming updates to asset type table via Melissa Nov 6, 2015
incidents Tombstone incidents/ folder Apr 4, 2018
metatags-and-urls docs regarding uris of articles and fragments Oct 14, 2015
ppp-bot-documentation added logs.md Apr 5, 2016
presentations
publishing-dashboard-wireframes gave wireframes folder more descriptive name Oct 14, 2015
publishing-workflows
.gitignore
LICENSE
Logbook.txt txt file for keeping some notes on progress of architecture diagrams Feb 8, 2016
README-obsolete.md Moved into README-obsolete.md most of the outdated information Jun 13, 2017
README.md
deployment-and-configuration.md

README.md

eLife Continuum

** DRAFT DOCUMENTATION **

Introduction

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.

Conceptual overview

High Level Overview

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.

Components

The actual software resides in the following repositories

Documentation and tools for building the components live in the following repositories

Licensing

eLife Continuum is licensed under the MIT License .

Installation and Deployment - DRAFT

We use builder for deployment of components of the system. Please refer to the deployment and configuration guide.

Feedback and mailing list

We have setup a mailing list for this project. For feature requests bugs please file an issue in this repository.