Skip to content

Commit

Permalink
Fix for broken links in docs/index.md;
Browse files Browse the repository at this point in the history
Related to issue #CE-2.

Change-Id: I9e70929d12468398ba0f7438e9de4d552cebd493
Signed-off-by: saksham1115 <saksham115@gmail.com>
  • Loading branch information
saksham115 committed Mar 24, 2017
1 parent ba2941b commit a447c81
Showing 1 changed file with 17 additions and 17 deletions.
34 changes: 17 additions & 17 deletions docs/index.md
Original file line number Diff line number Diff line change
@@ -1,17 +1,18 @@
![Cello](docs/imgs/logo.png)

Blockchain as a Service!

**Note:** This is a **read-only mirror** of the formal [Gerrit](https://gerrit.hyperledger.org/r/#/admin/projects/cello) repository,
where active development is ongoing. Issue tracking is handled in [Jira](https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=111)
where active development is ongoing. Issue tracking is handled in [Jira](https://jira.hyperledger.org/projects/CE/issues/).

## Incubation Notice

This project is a Hyperledger project in _Incubation_. It was proposed to the community and documented [here](https://docs.google.com/document/d/1E2i5GRqWsIag7KTxjQ_jQdDiWcuikv3KqXeuw7NaceM/edit), and was approved by [Hyperledger TSC at 2017-01-07](https://lists.hyperledger.org/pipermail/hyperledger-tsc/2017-January/000535.html). Information on what _Incubation_ entails can be found in the [Hyperledger Project Lifecycle document](https://goo.gl/4edNRc).

Platform to provide Blockchain as a Service!

Using Cello, we can

* Provision customizable Blockchains instantly, e.g., a 6-node chain using PBFT consensus.
* Provision customizable Blockchains instantly, e.g., a 6-node fabric chain using PBFT consensus.
* Maintain a pool of running blockchains healthy with no manual operations.
* Check the system status, scale the chain numbers, change resources... through a dashboard.

Expand All @@ -28,23 +29,22 @@ You can also find more [scenarios](docs/scenario.md).
* Support heterogeneous architecture, e.g., Z, Power and X86, from bare-metal servers to virtual machines.
* Extend with monitor/log/health features by employing additional components.

## Docs

### User Docs
* [Dashboard](docs/dashboard.md)
## Documentation

### Operator Docs
* [Installation & Deployment](docs/deployment.md)
* [Scenarios](docs/scenario.md)
* [Production Configuration](docs/production_config.md)
### Operational Docs
* [Installation & Deployment](install.md)
* [Terminologies](terminology.md)
* [Tutorial](tutorial.md)
* [Scenarios](scenario.md)
* [Production Configuration](production_config.md)

### Development Docs
* [How to contribute](docs/CONTRIBUTING.md)
* We're following [pep8 style guide](https://www.python.org/dev/peps/pep-0008/), [Coding Style](docs/code_style.md)
* [Architecture Design](docs/arch.md)
* [Database Model](docs/db.md)
* [API](api/restserver_v2.md)
* [Develop react js](docs/reactjs.md)
* [How to contribute](CONTRIBUTING.md)
* We're following [pep8 style guide](https://www.python.org/dev/peps/pep-0008/), [Coding Style](code_style.md)
* [Architecture Design](arch.md)
* [Database Model](db.md)
* [API](../api/restserver_v2.md)
* [Develop react js](reactjs.md)

## Why named Cello?
Can u find anyone better at playing chains? :)
Expand Down

0 comments on commit a447c81

Please sign in to comment.