anchor.diff:              a.beta(href="#creating-an-app") Creating an app
             li
               a.gamma(href="#js-example") Connecting the JS client
  +          li
  +            a.delta(href="#status") Status
         #main-content.col-lg-9
           h1.section#installation Getting started with Telepat
           
  +        h3.section#installation-repositories Repositories guide
  +        ul
  +          li
  +            strong
  +              a(href='https://github.com/telepat-io/telepat-models' target='_blank') Telepat models
  +            p The Telepat models library holds core functionality, and exposes a method API that other components (like the endpoint, and the services) can use to interact with the system. Unless developing the core or working on additional services, you sholdn't need to work with this library directly.
  +            p
  +              em Available on npm as 'telepat-models'.
  +          li
  +            strong
  +              a(href='https://github.com/telepat-io/telepat-api' target='_blank') Telepat API
  +            p Built on top of 
  +              a(href='http://expressjs.com/' target='_blank') Express
  +              | , the API provides web endpoints that allow interacting with Telepat from web and mobile applications. This is a required part of the Telepat stack.
  +            p
  +              em Available on npm as 'telepat-api'.
  +          li
  +            strong
  +              a(href='https://github.com/telepat-io/telepat-worker' target='_blank') Telepat services
  +            p This repo is a container for all the services that come pre-packaged with Telepat:
  +            ul
  +              li The aggregation service, that actively monitors data changes and generates patches;
  +              li The persistence service, that stores updates in the datastore and sends them off to synchronization;
  +              li The synchronization services, handling transport for individual platforms.
  +            p The aggregation and persistence services are required parts of the Telepat stack. If no synchronization service is started, Telepat will act like a traditional, non-real-time API platform and simply deliver data snapshots on-demand.
  +            p
  +              em Available on npm as 'telepat-worker'.
  +          li
  +            strong
  +              a(href='https://github.com/telepat-io/telepat-cli' target='_blank') Telepat CLI
  +            p A command-line interface that helps with configuring a Telepat instance and managing applications.
  +            p
  +              em Available on npm as 'telepat-cli'.
  +          li
  +            strong
  +              a(href='https://github.com/telepat-io/telepat-docker-compose-files') Telepat Docker files
  +            p A set of Docker Compose files for accelerating the deployment of Telepat as well as its dependencies.
  +          li
  +            strong Telepat clients
  +            p Native clients are available for multiple platforms:
  +            ul
  +              li
  +                a(href='https://github.com/telepat-io/telepat-js') Javascript client
  +                | , available on npm and bower as 'telepat-js'
  +              li
  +                a(href='https://github.com/telepat-io/telepat-android-sdk') Android client
  +                | , available as a Maven dependency
  +              li
  +                a(href='https://github.com/telepat-io/telepat-ios-sdk') iOS client
  +                | , available on CocoaPods as 'Telepat'
  +
           h3.section#installation-dependencies Launching dependencies
  -        p As of 0.2.3, Telepat requires connections to instances of Elasticsearch, Redis and Apache Kafka. You can deploy them individually, or you can use a docker-compose recipe that Telepat provides.
  -        p
  -          |  The recipes are separated in two components, shared dependencies and the actual Telepat software. Once you have 
  +        p As of 0.2.8, Telepat requires 3 external dependencies:
  +        ul
  +          li A messaging broker. Adapters are provided out of the box for 
  +            a(href='https://www.rabbitmq.com/' target='_blank') RabbitMQ
  +            |  and 
  +            a(href='http://kafka.apache.org/' target='_blank') Kafka
  +            | .
  +          li A JSON datastore. An adapter for 
  +            a(href='https://www.elastic.co/' target='_blank') Elasticsearch
  +            |  is provided.
  +          li A 
  +            a(href='http://redis.io/' target='_blank') Redis
  +            |  instance to hold Telepat state and configuration data.
  +        p
  +          | You can find installation instructions for all components on their respective website.
  +        p
  +          | Alternatively, we provide Docker Compose files to accelerate deployment. The recipes are separated in two components, shared dependencies and the actual Telepat software. Once you have 
             a(href='https://docs.docker.com/installation/') docker
             |  and 
             a(href='https://docs.docker.com/compose/install/') docker-compose
  
positive.code:         p All you need to do next is run the example:
          pre gulp serve
          p That's it! You've successfully deployed your first Telepat instance.
  block scripts
    script(src="scripts/intro.js")
    script(src="scripts/menu-highlight.js")
negative.code: extends layouts/_default
  block content
    .container-fluid
      .row
        .col-lg-3
  