Seems like docs will have structure

docs/index.md

@@ -1,3 +1,11 @@
 # Dcron - Distributed cron
 
-Wlcome to the Dcron documentation! This is the reference guide on how to use Drcon. If you want a getting started guide refer to the [getting started guide](getting-started/) of the Dcron documentation.
+Welcome to the Dcron documentation! This is the reference guide on how to use Drcon. If you want a getting started guide refer to the [getting started guide](getting-started/) of the Dcron documentation.
+
+## What is Dcron
+
+Dcron is a system service that runs scheduled tasks at given intervales or times, just like the cron unix service. It differs from it in the sense that it's distributed in several machines in a cluster and if one of that machines (the leader) fails, any other one can take this responsability and keep executing the sheduled tasks without human intervention.
+
+## Dcron design
+
+Dcron is designed to do one task well, executing commands in given intervals, following the unix philosophy of doing one thing and doing it well, like the classic and battle tested cron unix service, with the given addition of being designed for the cloud era, removing single points of failure and clusters of any size are needed to execute scheduled tasks in a decentralized fashion.

docs/user-guide/getting-started.md

@@ -0,0 +1,57 @@
+#Getting started
+
+Welcome to the intro guide to Dcron! This will explain how to setup serf, how easy is to use it, what problems could it help you to solve, etc.
+
+## Introduction
+
+Dcron nodes can work in two modes, agents or servers.
+
+Servers are agents too. You can use servers to run jobs.
+
+The main distinction is that servers order job executions and can be used to schedule jobs.
+
+Dcron servers have a leader, the leader is responsible of executing jobs in the cluster.
+
+Any dcron agent or server acts as a cluster member and it's available to run scheduled tasks.
+
+You can choose whether a job is run on a node or nodes by specifying tags and a count of target nodes having this tag do you want a job to run. For example you can specify to run a job at 5:00am in all servers with role=web tag or you can specify to run a job in just one server of having the role=web tag:
+
+```
+role=web:1
+```
+
+Dcron will try to run the job in the amount of nodes indicated by that count having that tag.
+
+This gives an unprecedented level of flexibility in runnig jobs across a cluster of any size and with any combination of machines you need.
+
+All the execution responses will be gathered by the scheduler and stored in the database.
+
+## Installation
+
+Simply download the packaged archive for your platform from the downloads page, extract the package to a shared location in your drive, like `/opt/local` and run it from there.
+
+### Ubuntu
+
+Sample upstart scripts for Dcron are included in the `extras` folder
+
+### Debian
+
+Sample init scripts are included in the `extras` folder
+
+## Configuration
+
+See the [configuration section](configuration).
+
+## Usage
+
+Dcron relies on etcd for data storage, the etcd executable is included in the package and can be used to run an etcd node along with dcron servers.
+
+By default Dcron will start the etcd server when running in server mode and try to form a cluster.
+
+If you want to use an existing etcd cluster of your own, you can specify it by setting the `no-etcd` flag in the config file or as a command line flag.
+
+To start a Dcron server instance just run:
+
+```
+dcron agent --server
+```