Skip to content

Commit

Permalink
Structure of technology approach and technology goals. Related to #4 #5
Browse files Browse the repository at this point in the history
  • Loading branch information
jmatsushita committed Feb 11, 2016
1 parent 62b3d9e commit 83bd07c
Show file tree
Hide file tree
Showing 3 changed files with 33 additions and 17 deletions.
34 changes: 31 additions & 3 deletions technology.md
Expand Up @@ -3,14 +3,42 @@ layout: page
title: Technology
---

The following pages describe the various technology related aspect of the content as code project
> Also see the [status page](status) and [roadmap](status#roadmap)
* [Components](components) : Overview of content as code components
The following sub-pages describe the various technology related aspect of the content as code project

* Workflow Components
* [Authoring](authoring)
* [Translation](translation)
* [Collaboration](collaboration)
* [Management](management)
* [Reuse](reuse)
* [Existing Approaches](existing) : Descriptions of existing approaches among project partners.
* [Inspiration](inspiration) from other projects

## Architecture
## Technical Goals

### CMS Parity

> Having usable solutions for commonly available features in CMSes is a design goal.
Have clear, integrated and open source solutions to deal with comments, visit statistics, search, forms and other features traditionally managed with a database backend.

### Flexible structure

> Allowing completely free form content structures or complex content structures is a design goal.
### Interoperable and extensible

> Allowing mixed workflows that allow importing/exporting/synchronising content across systems and adding software components is a design goal.
### Streamlined and extensible

> Simplicity and ease of use and understanding are design goals.
Composed of many different software parts, the workflow is nonetheless streamlined and integrated. When deployed with default settings, it can be used immediately. Authors, editors, translators as well as software and systems engineer can understand how the pieces fit together.

## Previous Architecture

In the below diagram the following approach is proposed:

Expand Down
13 changes: 0 additions & 13 deletions technology/components.md

This file was deleted.

3 changes: 2 additions & 1 deletion technology/inspiration.md
Expand Up @@ -9,7 +9,8 @@ title: Inspiration

### Web based Editors

- Aloha
- Quip
- Penflip
-

### Markdown
Expand Down

0 comments on commit 83bd07c

Please sign in to comment.